User Tools

Site Tools


en:tutorials:publishing:preparing_a_windows_release

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:tutorials:publishing:preparing_a_windows_release [2020/08/31 12:27 (5 years ago)] – ↷ Page moved from en:tutorials:community:sausage:preparing_a_windows_release to en:tutorials:publishing:preparing_a_windows_release sausageen:tutorials:publishing:preparing_a_windows_release [2025/09/30 17:26 (12 days ago)] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 The following acts as a tutorial and a reference checklist for preparing your build for release and packaging for deployment. It covers preparing and inserting an icon for your executable, a checklist of things for your config files, and finally to create a setup.exe. The following acts as a tutorial and a reference checklist for preparing your build for release and packaging for deployment. It covers preparing and inserting an icon for your executable, a checklist of things for your config files, and finally to create a setup.exe.
 +
 +
 +<WRAP center round info 80%>
 +Also check [[en:tutorials:publishing:common_release_checklist|Common Release Checklist]] for a number of other things you might like to consider when packaging your release.
 +</WRAP>
 +
  
  
Line 10: Line 16:
 These libraries are supplied as part of the Microsoft Visual C++ Redistributable.  These libraries are supplied as part of the Microsoft Visual C++ Redistributable. 
  
-Any project you create using [[en:tutorials:community:sausage:using-premake-for-your-own-project|init]] should already be set up to compile in these libraries statically. If your project isn't, you can add the following to your linker options: ''-static;-static-libgcc -static-libstdc++''.+Any project you create using [[en:tutorials:projects:using-premake-for-your-own-project|init]] should already be set up to compile in these libraries statically. If your project isn't, you can add the following to your linker options: ''-static;-static-libgcc -static-libstdc++''.
  
 This step should not be necessary for Visual Studio users. This step should not be necessary for Visual Studio users.
Line 77: Line 83:
  
 That's all. That's all.
- 
- 
-===== Additional Tips ===== 
- 
-There are a [[en:tutorials:common_release_checklist|number of other things you might like to consider]] when packaging your release. 
  
en/tutorials/publishing/preparing_a_windows_release.1598876878.txt.gz · Last modified: 2025/09/30 17:26 (12 days ago) (external edit)