Building on Windows: Difference between revisions

From NEOSYS Dev Wiki
Jump to navigationJump to search
Line 76: Line 76:
== Building Using Scripts or Command Line ==
== Building Using Scripts or Command Line ==


Once config.bat is setup then making is a completely automatic process.
Once config.bat is setup then making is a completely automatic process. Currently config.bat only supports one configuration/platform (e.g. Release/x64) at a time.


  make.bat
  make.bat

Revision as of 17:22, 15 May 2011

Setting up Exodus Build Environment on Windows

Install and configure MS VC++ Step_by_step_instructions#INSTALL_COMPILER Ignore any configuration "for Exodus"
Install and configure Postgresql Step_by_step_instructions#INSTALL_DATABASE Ignore any configuration "for Exodus"
Install Subversion client http://tortoisesvn.net/downloads.html Ignore its suggestion to reboot after installation.
Install NSIS Installer Builder http://sourceforge.net/projects/nsis/files/

Get Boost Libraries

Install or build Boost 1_46_1 binary libraries and header/include source files.

You only need the release versions if you are simply packaging Exodus for release. You need Boost debug version libraries only to develop/debug Exodus

Built from source

Building Boost 32/64 on Windows

Ready-made from Exodus project

Binaries: http://exodusdb.googlecode.com/files/boost1461-vc100-x86x64-rd.zip

Header/Includes: Building_Boost_32/64_on_Windows#Get_Boost_Source

Ready-made from BoostPro x86 only

Includes source. GET VERSION 1_46_1 Visual Studio 2010 mt and mt-debug version Installing_Boost.

Get Exodus Source/Build Files

NB always use HTTPS not http for the subversion link below - just in case you need to commit any changes back up into the subversion repository.

GUI:

  1. Create a folder called "exodus" F:\exodus
  2. Right exodus click and choose "SVN checkout"
  3. url of respository: HTTPS://exodusdb.googlecode.com/svn/trunk/

TUI:

svn co HTTPS://exodusdb.googlecode.com/svn/trunk/ c:\exodus

Configuring Exodus for Building

copy the config0.bat to config.bat and edit it to reflect your configuration

If you are only building x64 then you dont need to set the x32 variables. Note that BOOST32 and BOOST64 may point to the same folder since the headers/includes are the same and the binaries are in different libs eg stage64 or lib64 etc.

Build/Develop Using Visual Studio

The exodus_all.sln relies on environment variables to identify location of boost, postgresql. All the necessary environment variables are set in config.bat.

To open visual studio with all the right environment variables set you must run dev.bat which calls config.bat and then opens your solution

dev.bat
  1. Select Configuration: Release or Debug
  2. Select Platform: x64 or Win32
  3. Build the solution
  4. Debug/Run the solution - should get an exodus/cmd command console
  5. type configexodus, testsort, edic etc.

Building Using Scripts or Command Line

Once config.bat is setup then making is a completely automatic process. Currently config.bat only supports one configuration/platform (e.g. Release/x64) at a time.

make.bat
clean.bat

Packaging Exodus

Once config.bat is setup then packing is a completely automatic process. Look for output files like exodus-x86-11.5.3.exe.

pack.bat

Uploading Exodus

Once config.bat is setup then uploading new versions is a completely automatic process.

upload.bat

Old Info

Building on Windows - Old Version