Building on Windows: Difference between revisions

From NEOSYS Dev Wiki
Jump to navigationJump to search
 
(94 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Software to install:==
== Setting up Exodus Build Environment on Windows ==


{|cellpadding="5" cellspacing="0" border="1" width="60%"
|Install and configure MS VC++
|[[Step_by_step_instructions#INSTALL_COMPILER]]<BR>You need SDK *and* Visual Studio
|*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/
|
|-
|Install Python
|http://python.org/download/
|Only needed to upload binaries to Google Code
|}


# WinRAR
== Get Boost Libraries ==
# PostgresSQL
# TortoiseSVN 9(32 bit)
# Boost c++ libraries 1.34.0
# Visual Studio C++ Express Edition
# Windows Platform SDK.


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


If installing off the C: drive, keep everything on the same drive and in the standard directory tree otherwise you will have to modify the project settings to point to the right include and lib folders.
If you are simply building Exodus for packaging and release then you need only the release versions of Boost. You only need Boost debug libraries o develop/debug Exodus itself.


D:\Program Files\boost\boost_1_34_0
=== Source 1 - build them from source ===
D:\Program Files\PostgreSQL\8.3
D:\Documents and settings\steve\Desktop\exodus <- anywhere on D: will do actually
[[Installing WinRAR]]


[[Installing Postgres]]
[[Building Boost 32/64 on Windows]]


[[Installing Tortoise Subversion]]
=== Source 2 - download from Exodus project ===


[[Installing Boost]]
Header/Includes: [[Building_Boost_32/64_on_Windows#Get_Boost_Source]]


[[Installing Visual Studio Express C++]]
Binaries: http://exodusdb.googlecode.com/files/boost1461-vc100-x86x64-rd.zip


==Getting Project Exodus onto your Computer:==
Unzip the binaries into the main boost source/header/includes like this:


# Go to your desktop, and create a new folder.
boost_1_46_1\stage32
# Right click on the folder, and got to TortoiseSVN, checkout.
boost_1_46_1\stage64
# In the URL field type in (or copy and paste) http://svn.neosys.com/svn/trunk and click Ok.<br>
[[Image:tortoiseSVN.JPG]]<br>
# Another window will pop up, and start listing the files you are importing onto your pc.
# Click Ok, once loading is finished.


For help on how to use: http://devwiki.neosys.com/index.php/Installing_and_Using_Tortoise_Subversion
=== Source 3 - download from BoostPro (but no x64! and no Unicode regex(?)) ===


===Part 2 Configuring & Compiling===
Installs includes and binaries.


# Run Microsoft Visual Studio C++ Express Edition.
See [[Installing_Boost]] but get:
# Now go to File, Open, File, Desktop, Exodus, agency, agency.sln and then open.
*Version 1_46_1
# You should see:<br>[[Image:newsolutionExplor.JPG]]<br>
*Visual Studio 2010
# Open agency pointed to you by the red arrow, by clicking on the + sign.
*mt and mt-debug version
# Remove Market and schedule.
# In the agency folder, open Main then double click on main.cpp
# You should now have C++ code to the right side of the Visual Studio program window.


== Possible Problems During Building ==
== Checkout Exodus ==


== Possible Problems During Execution ==
To commit any bug fixes or developments, send your gmail address [http://code.google.com/p/exodusdb/people/list here] to get a password.


=== libpq.dll ===
=== GUI  ===


[[Image:errormessage.JPG]]
#Create a folder called "exodus" F:\exodus
# Check whether libpq.dll is in C:\Program Files\PostgreSQL\8.1\lib\????, if not there then change project properties to reflect version on location in where you installed postgreSQL.
#Right exodus click and choose "SVN checkout"
# Right click on My computer, properties, advanced, environment variables, system variables, scroll down and find Path, double click it. variable value, go to the end of the path and type a semi-colon, then copy and paste the following path after the semi-colon:<br><b>C:\Program Files\PostgreSQL\8.1\lib\ms</b> and close Visual Studio C++ Express Edition, and then open again.
#url of respository: HTTPS://exodusdb.googlecode.com/svn/trunk/
[[Image:PCconfig.JPG]]


=== ssleay32.dll ===
=== TUI ===


There are dozens of versions of this open source secure sockets library which are widely used by many vendors some of whom very wrongly install them in the windows\system32 folder which has precedence after the local folder but before the path is searched. postgres requires them and will use the wrong version.
svn co HTTPS://exodusdb.googlecode.com/svn/trunk/ c:\exodus


The simplest solution is often to delete them.
You can use all the power of subversion to keep your build directory up to date, select previous versions of Exodus and generally be in control.


del c:\Windows\system32\ssleay32.dll
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.
del c:\Windows\system32\libeay32.dll


If you cannot delete them then try rebooting. If that doesnt work then find out which program has them open using some dll search facility like sysinternals procexplorer.
== Configure Exodus for Developing, Building, Packing, Uploading ==


Another solution is simply to upgrade them to the latest version of the files that you can find on your computer or on the web or from the postgres bin folder. See properties not the file date.
copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration. Only configure those stages that you plan to do.


INITIAL VERSION BY GREG BUSH 19/10/2007
If you are only building x64 then you don't 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.


==Helpful Websites==
You can run clean, dev, make, pack, upload etc by just clicking on them without opening a command prompt.


# For help on Microsoft Visual Studio C++ Express Edition go to http://msdn2.microsoft.com/en-gb/express/aa700755.aspx
[[configlocalEXAMPLE.cmd]] as at 2010/5/20
# For help on Boost go to http://www.boost.org
 
# For help on PostgeSQL go to http://www.postgresql.org/
for packing, you need to edit version.cmd, for example
# For help on WinRAR go to http://www.win-rar.com/winrarsupport.html
 
# For help on TortoiseSVN go to http://tortoisesvn.tigris.org/
set EXO_MAJOR_VER=11
# For how to use tortoiseSVN go to [[Installing_and_Using_Tortoise_Subversion]]
set EXO_MINOR_VER=5
set EXO_MICRO_VER=28
set EXO_BUILD_VER=0
 
== Either 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 the fixed config.cmd and your local configlocal.cmd.
 
To open visual studio with all the right environment variables set you must run dev.cmd which calls config.cmd and then opens your solution
 
dev.cmd
 
#Select Configuration: Release or Debug
#Select Platform: x64 or Win32
#Build the solution
#Check the startup project is exodus_cli
#Debug/Run the solution. You should get an exodus/cmd command console.
#Type testsort, edic etc. configexodus may require adminstrator access to install pgexodus.dll into Postgresql's bin directory.
 
== Or Build Using Scripts or Command Line ==
 
Once configlocal.cmd is setup then making is a completely automatic process. Currently configlocal.cmd only supports one configuration/platform (e.g. Release/x64) at a time.
 
make.cmd
clean.cmd
 
== Packaging Exodus ==
 
Once configlocal.cmd is setup then packing is a completely automatic process. Look for output files like exodus-x86-11.5.3.exe.
 
pack.cmd
 
== Uploading Exodus ==
 
Once configlocal.cmd is setup then uploading new versions is a completely automatic process.
 
upload.cmd
 
== Old Info ==
 
[[Building on Windows - Old Version]]

Latest revision as of 14:24, 18 February 2012

Setting up Exodus Build Environment on Windows

Install and configure MS VC++ Step_by_step_instructions#INSTALL_COMPILER
You need SDK *and* Visual Studio 		*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/
Install Python http://python.org/download/ Only needed to upload binaries to Google Code

Get Boost Libraries

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

If you are simply building Exodus for packaging and release then you need only the release versions of Boost. You only need Boost debug libraries o develop/debug Exodus itself.

Source 1 - build them from source

Building Boost 32/64 on Windows

Source 2 - download 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

Source 3 - download from BoostPro (but no x64! and no Unicode regex(?))

Installs includes and binaries.

See Installing_Boost but get:

  • Version 1_46_1
  • Visual Studio 2010
  • mt and mt-debug version

Checkout Exodus

To commit any bug fixes or developments, send your gmail address here to get a password.

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

You can use all the power of subversion to keep your build directory up to date, select previous versions of Exodus and generally be in control.

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.

Configure Exodus for Developing, Building, Packing, Uploading

copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration. Only configure those stages that you plan to do.

If you are only building x64 then you don't 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.

You can run clean, dev, make, pack, upload etc by just clicking on them without opening a command prompt.

configlocalEXAMPLE.cmd as at 2010/5/20

for packing, you need to edit version.cmd, for example 

set EXO_MAJOR_VER=11
set EXO_MINOR_VER=5
set EXO_MICRO_VER=28
set EXO_BUILD_VER=0

Either 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 the fixed config.cmd and your local configlocal.cmd.

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

dev.cmd
  1. Select Configuration: Release or Debug
  2. Select Platform: x64 or Win32
  3. Build the solution
  4. Check the startup project is exodus_cli
  5. Debug/Run the solution. You should get an exodus/cmd command console.
  6. Type testsort, edic etc. configexodus may require adminstrator access to install pgexodus.dll into Postgresql's bin directory.

Or Build Using Scripts or Command Line

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

make.cmd
clean.cmd

Packaging Exodus

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

pack.cmd

Uploading Exodus

Once configlocal.cmd is setup then uploading new versions is a completely automatic process. 

upload.cmd

Old Info

Building on Windows - Old Version

Retrieved from "https://devwiki.neosys.com/index.php?title=Building_on_Windows&oldid=1479"