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:community:sausage:preparing_a_windows_release [2019/03/06 04:30 (5 years ago)] sausageen:tutorials:publishing:preparing_a_windows_release [2022/01/07 01:57 (2 years ago)] (current) sausage
Line 3: Line 3:
 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>
 +
 +
 +
 +===== Checking Library Dependencies =====
 +
 +Orx on Windows depends on //libgcc// and //libstdc++// being compiled in statically, which it is. Your project needs to have these two libraries compiled in statically too, in order avoid the user being prompted when running your application.
 +
 +These libraries are supplied as part of the Microsoft Visual C++ Redistributable. 
 +
 +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.
  
  
Line 67: Line 83:
  
 That's all. That's all.
- 
- 
- 
-===== Checking Library Dependencies ===== 
- 
-Orx on Windows depends on //libgcc// and //libstdc++// being compiled in statically, which it is. Your project needs to have these two libraries compiled in statically too, in order avoid the user being prompted when running your application. 
- 
-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++''. 
- 
-This step should not be necessary for Visual Studio users. 
- 
- 
-===== 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.1551875427.txt.gz · Last modified: 2019/03/06 08:30 (5 years ago) (external edit)