User Tools

Site Tools


en:tutorials:community:sausage:preparing_a_windows_release

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
en:tutorials:community:sausage:preparing_a_windows_release [2018/02/14 04:46 (13 months ago)]
iarwain ↷ Page moved from tutorials:community:sausage:preparing_a_windows_release to en:tutorials:community:sausage:preparing_a_windows_release
en:tutorials:community:sausage:preparing_a_windows_release [2019/03/06 12:30 (2 weeks ago)] (current)
sausage
Line 67: Line 67:
  
 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/community/sausage/preparing_a_windows_release.txt · Last modified: 2019/03/06 12:30 (2 weeks ago) by sausage