Building on Windows - Revision history

Steve: /* Configure Exodus for Developing, Building, Packing, Uploading */

2012-02-18T14:24:09Z

Configure Exodus for Developing, Building, Packing, Uploading

← Older revision		Revision as of 14:24, 18 February 2012
Line 80:		Line 80:

	[[configlocalEXAMPLE.cmd]] as at 2010/5/20		[[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 ==		== Either Build/Develop Using Visual Studio ==

Steve: /* Either Build/Develop Using Visual Studio */

2011-05-20T22:06:03Z

Either Build/Develop Using Visual Studio

← Older revision		Revision as of 22:06, 20 May 2011
Line 92:		Line 92:
	#Select Platform: x64 or Win32		#Select Platform: x64 or Win32
	#Build the solution		#Build the solution
	#Debug/Run the solution - should get an exodus/cmd command console		#Check the startup project is exodus_cli
	#~~type~~ testsort, edic etc. configexodus may require adminstrator access to install pgexodus.dll into Postgresql's bin directory.		#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 ==		== Or Build Using Scripts or Command Line ==

Steve: /* Configure Exodus for Developing, Building, Packing, Uploading */

2011-05-20T17:14:37Z

Configure Exodus for Developing, Building, Packing, Uploading

← Older revision		Revision as of 17:14, 20 May 2011
Line 76:		Line 76:

	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.		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		[[configlocalEXAMPLE.cmd]] as at 2010/5/20

Steve: /* Build Using Scripts or Command Line */

2011-05-20T17:12:57Z

Build Using Scripts or Command Line

← Older revision		Revision as of 17:12, 20 May 2011
Line 93:		Line 93:
	#type testsort, edic etc. configexodus may require adminstrator access to install pgexodus.dll into Postgresql's bin directory.		#type testsort, edic etc. configexodus may require adminstrator access to install pgexodus.dll into Postgresql's bin directory.

	== Build Using Scripts or Command Line ==		== 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.		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.

Steve: /* Build/Develop Using Visual Studio */

2011-05-20T17:12:28Z

Build/Develop Using Visual Studio

← Older revision		Revision as of 17:12, 20 May 2011
Line 79:		Line 79:
	[[configlocalEXAMPLE.cmd]] as at 2010/5/20		[[configlocalEXAMPLE.cmd]] as at 2010/5/20

	== Build/Develop Using Visual Studio ==		== 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.		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.

Steve: /* Build Using Visual Studio */

2011-05-20T17:11:45Z

Build Using Visual Studio

← Older revision		Revision as of 17:11, 20 May 2011
Line 79:		Line 79:
	[[configlocalEXAMPLE.cmd]] as at 2010/5/20		[[configlocalEXAMPLE.cmd]] as at 2010/5/20

	== Build Using Visual Studio ==		== 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.		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.

Steve: /* Configure Exodus for Developing, Building, Packing, Uploading */

2011-05-20T17:10:49Z

Configure Exodus for Developing, Building, Packing, Uploading

← Older revision		Revision as of 17:10, 20 May 2011
Line 73:		Line 73:
	== Configure Exodus for Developing, Building, Packing, Uploading ==		== Configure Exodus for Developing, Building, Packing, Uploading ==

	copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration. ~~You do not have to~~ configure ~~everything if~~ you ~~are not performing all stages~~.		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.		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.

Steve: /* Configure Exodus for Building, Packing, Uploading */

2011-05-20T17:10:16Z

Configure Exodus for Building, Packing, Uploading

← Older revision		Revision as of 17:10, 20 May 2011
Line 71:		Line 71:
	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.		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 Building, Packing, Uploading ==		== Configure Exodus for Developing, Building, Packing, Uploading ==

	copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration		copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration. You do not have to configure everything if you are not performing all stages.

	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.		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.

Steve at 16:58, 20 May 2011

2011-05-20T16:58:44Z

← Older revision		Revision as of 16:58, 20 May 2011
Line 17:		Line 17:
	\|http://sourceforge.net/projects/nsis/files/		\|http://sourceforge.net/projects/nsis/files/
	\|		\|
			\|-
			\|Install Python
			\|http://python.org/download/
			\|Only needed to upload binaries to Google Code
	\|}		\|}

Line 77:		Line 81:
	== Build Using Visual Studio ==		== Build 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~~.		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.~~bat~~ which calls config.~~bat~~ and then opens your solution		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.~~bat~~		dev.cmd

	#Select Configuration: Release or Debug		#Select Configuration: Release or Debug
Line 87:		Line 91:
	#Build the solution		#Build the solution
	#Debug/Run the solution - should get an exodus/cmd command console		#Debug/Run the solution - should get an exodus/cmd command console
	#type ~~configexodus,~~ testsort, edic etc.		#type testsort, edic etc. configexodus may require adminstrator access to install pgexodus.dll into Postgresql's bin directory.

	== Build Using Scripts or Command Line ==		== Build 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.		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.~~bat~~		make.cmd
	clean.~~bat~~		clean.cmd

	== Packaging Exodus ==		== 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.		Once configlocal.cmd is setup then packing is a completely automatic process. Look for output files like exodus-x86-11.5.3.exe.

	pack.~~bat~~		pack.cmd

	== Uploading Exodus ==		== Uploading Exodus ==

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

	upload.~~bat~~		upload.cmd

	== Old Info ==		== Old Info ==

	[[Building on Windows - Old Version]]		[[Building on Windows - Old Version]]

Steve: /* Configure Exodus for Building, Packing, Uploading */

2011-05-20T16:51:36Z

Configure Exodus for Building, Packing, Uploading

← Older revision		Revision as of 16:51, 20 May 2011
Line 68:		Line 68:

	== Configure Exodus for Building, Packing, Uploading ==		== Configure Exodus for Building, Packing, Uploading ==

	~~[[configlocalEXAMPLE.cmd]] as at 2010/5/20~~

	copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration		copy the configlocalEXAMPLE.cmd to configlocal.cmd and edit it to reflect your configuration

	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.		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.

			[[configlocalEXAMPLE.cmd]] as at 2010/5/20

	== Build Using Visual Studio ==		== Build Using Visual Studio ==