User Tools

Site Tools


cre:compiling

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
cre:compiling [2021/10/24 14:14]
draugthewhopper [Windows]
cre:compiling [2021/10/26 11:51]
draugthewhopper [Finishing steps]
Line 33: Line 33:
 ===== Windows ===== ===== Windows =====
  
-CRE has a pre-compiled ​.exe available ​for [[http://​crossfire.weeger.org/​cre-latest.exe|download]] (make sure to check the [[http://​crossfire.weeger.org/​cre-latest.exe.sha512|sha512 sum]]). It is updated daily, ​and should not require any dependency (if it does, then please report that issue).+Windows users wishing to use CRE have two options if they don't wish to compile CRE themselves: use the installer, or use the standalone executableThey are available ​from [[http://​crossfire.weeger.org]]. ​Both are updated daily, ​with some ''​archives''​.
  
-After putting the .exe in the directory of your choiceyou need to assemble a few prerequisites before ​it will run: +In both cases, it is required to get ''​maps''​ and ''​arch''​ (read below).
  
-Firstcreate a directory alongside the .exenamed ''​share''​Get ''​arch''​ and ''​maps'',​ and put them into ''​share''​. You may find it easiest to directly clone the git repos so you can easily push your changes upstream. Get the ''​i18n''​ directory from the server source ​(it's in ''​lib\i18n''​and place it here too.+Both CRE versions are cross-compiledso there may be unknown issuesPlease report any issuesor problems with this documentation 
 +==== Using the installer ​(recommended====
  
-Next, create a directory alongside the .exe, named ''​etc''​. Find ''​exp_table'',​ ''​settings'',​ and ''​stat_bonus''​ from the server source (they'​re in ''​lib\config''​),​ and place them here in ''​etc''​. Note that if you are running a Crossfire server, maybe you want to pull these files from your server config instead.+The latest version of the installer is available from [[http://​crossfire.weeger.org/​CREInstaller-latest.exe|this direct link]] (make sure to check the [[http://​crossfire.weeger.org/​CREInstaller-latest.exe.sha512|sha512 sum]]). 
 + 
 +It will create required directories and add start menu and desktop shortcuts if wanted. 
 + 
 +Note that if you run the installer when a version is already installed, the old version is uninstalled silently. 
 + 
 +==== Using the standalone executable ==== 
 + 
 +CRE standalone is available from [[http://​crossfire.weeger.org/​cre-latest.exe|this direct link]] (make sure to check the [[http://​crossfire.weeger.org/​cre-latest.exe.sha512|sha512 sum]]). 
 + 
 +After putting the ''​.exe''​ in the directory of your choice, you need to assemble a few prerequisites before it will run:  
 + 
 +First, create a directory alongside the .exe, named ''​share''​. Get the ''​i18n''​ directory from the server source (it's in ''​[[https://​sourceforge.net/​p/​crossfire/​crossfire-server/​ci/​master/​tree/​lib/​i18n/​|lib\i18n]]''​) and place it here too. 
 + 
 +Next, create a directory alongside the .exe, named ''​etc''​. Find ''​exp_table'',​ ''​settings'',​ and ''​stat_bonus''​ from the server source (they'​re in ''​[[https://​sourceforge.net/​p/​crossfire/​crossfire-server/​ci/​master/​tree/​lib/​config/​|lib\config]]''​),​ and place them here in ''​etc''​. Note that if you are running a Crossfire server, maybe you want to pull these files from your server config instead.
  
 Finally, create a directory alongside the .exe, named ''​var''​. CRE may place temporary files here at runtime. Finally, create a directory alongside the .exe, named ''​var''​. CRE may place temporary files here at runtime.
  
 +==== Finishing steps ====
 +
 +Get ''​arch''​ and ''​maps'',​ and put them into ''​share''​.
 +
 +One way is to get a snapshot from Sourceforge,​ available [[https://​sourceforge.net/​p/​crossfire/​crossfire-maps/​ci/​master/​tarball?​path=|for maps]] and [[https://​sourceforge.net/​p/​crossfire/​crossfire-arch/​ci/​master/​tarball?​path=|for arch]].
 +
 +Another option is to clone the git repositories so you can easily push your changes upstream. ​
 +
 +==== Troubleshooting ====
 Note that it can take quite a few seconds for CRE to launch, even longer if your disk is slow, as it loads many files on launch. Note that it can take quite a few seconds for CRE to launch, even longer if your disk is slow, as it loads many files on launch.
  
-If CRE launches and then exits, it may be having trouble finding some paths. Procmon from the Sysinternals Suite may be helpful, or a debugger.+If CRE launches and then exits, it may be having trouble finding some paths. ​There should be a log file in ''​%temp%\cre.log''​ giving some details. 
 + 
 +Procmon from the Sysinternals Suite may be helpful, or a debugger.
 ====== Interface ====== ====== Interface ======
  
cre/compiling.txt · Last modified: 2024/03/20 01:07 by leaf