Building on Windows: Difference between revisions
| Line 69: | Line 69: | ||
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. | 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 == | == Build/Develop Using Visual Studio (Optional) == | ||
The exodus_all.sln relies on environment variables to identify location of boost, postgresql. All the necessary environment variables are set in config.bat. | The exodus_all.sln relies on environment variables to identify location of boost, postgresql. All the necessary environment variables are set in config.bat. | ||
Revision as of 19:57, 15 May 2011
Setting up Exodus Build Environment on Windows
| Install and configure MS VC++ | Step_by_step_instructions#INSTALL_COMPILER | *Ignore the section to "test Exodus compilation - you haven't built it yet!" |
| 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
Header/Includes: Building_Boost_32/64_on_Windows#Get_Boost_Source
Binaries: http://exodusdb.googlecode.com/files/boost1461-vc100-x86x64-rd.zip
Unzip the binaries into the main boost source/header/includes like this:
boost_1_46_1\stage32 boost_1_46_1\stage64
Ready-made from BoostPro (but no x64!)
Installs includes and binaries.
See Installing_Boost but get:
- Version 1_46_1
- Visual Studio 2010
- mt and mt-debug version
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:
- Create a folder called "exodus" F:\exodus
- Right exodus click and choose "SVN checkout"
- 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 (Optional)
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
- Select Configuration: Release or Debug
- Select Platform: x64 or Win32
- Build the solution
- Debug/Run the solution - should get an exodus/cmd command console
- 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
