Building ASCEND for 64-bit Windows - Revision history

Jpye: /* Building ASCEND */

2013-12-05T07:42:55Z

Building ASCEND

← Older revision		Revision as of 07:42, 5 December 2013
Line 68:		Line 68:
	== Building ASCEND ==		== Building ASCEND ==

	If your [[Setting up a MinGW-w64 build environment\|Windows build environment]] is set up correctly, and you have a current copy of the source code (either from [[VersionManagement our subversion repository]] or a source-code tarball), you should be able to simply run:		If your [[Setting up a MinGW-w64 build environment\|Windows build environment]] is set up correctly, and you have a current copy of the source code (either from [[VersionManagement\|our subversion repository]] or a source-code tarball), you should be able to simply run:

	scons -j4		scons -j4

Jpye: /* Building ASCEND */

2013-12-05T07:42:46Z

Building ASCEND

← Older revision		Revision as of 07:42, 5 December 2013
Line 68:		Line 68:
	== Building ASCEND ==		== Building ASCEND ==

	If your [[Setting up a MinGW-w64 build environment Windows build environment]] is set up correctly, and you have a current copy of the source code (either from [[VersionManagement our subversion repository]] or a source-code tarball), you should be able to simply run:		If your [[Setting up a MinGW-w64 build environment\|Windows build environment]] is set up correctly, and you have a current copy of the source code (either from [[VersionManagement our subversion repository]] or a source-code tarball), you should be able to simply run:

	scons -j4		scons -j4

Jpye at 07:42, 5 December 2013

2013-12-05T07:42:29Z

@@ Line 65: / Line 65: @@
 Currently the resulting IPOPT depends on libgfortran and libstdc++. If you build the resulting static libraries into a DLL or an EXE, that DLL/EXE will have shared library dependencies on the ligfortran and libstdc++ DLLs that come with MinGW/MinGW-w64. We would rather like to have the code from of those external DLLs statically linked, but don't yet know how that's possible.
 == Runtime prerequisites ==
@@ Line 97: / Line 117: @@
 Some helpful diagnostics for finding out why 'import gtk' gives errors in some cases: (in my case, I needed to add c:/GTK/bin to the START of my PATH because of a conflicting ZLIB1.DLL earlier in my PATH.
 * http://gramps-project.org/wiki/index.php?title=ImportError:_DLL_load_failed
 == Building the ASCEND installer ==

Jpye at 05:49, 5 December 2013

2013-12-05T05:49:03Z

← Older revision		Revision as of 05:49, 5 December 2013
Line 65:		Line 65:

	Currently the resulting IPOPT depends on libgfortran and libstdc++. If you build the resulting static libraries into a DLL or an EXE, that DLL/EXE will have shared library dependencies on the ligfortran and libstdc++ DLLs that come with MinGW/MinGW-w64. We would rather like to have the code from of those external DLLs statically linked, but don't yet know how that's possible.		Currently the resulting IPOPT depends on libgfortran and libstdc++. If you build the resulting static libraries into a DLL or an EXE, that DLL/EXE will have shared library dependencies on the ligfortran and libstdc++ DLLs that come with MinGW/MinGW-w64. We would rather like to have the code from of those external DLLs statically linked, but don't yet know how that's possible.

	~~=== GDB ===~~

	~~{{outdated-section}}~~
	~~''gdb seems to be included the current MinGW-w64 package (see [[setting up a MinGW-w64 build environment]]), so the following is probably not required any more''~~

	~~GDB is helpful for debugging the location of crashes, errors, etc. It requires a specially-compiled version of an executable, which with GCC is specified by adding <tt>-g</tt> at compile-time.~~

	* Download the GDB package from the MinGW-64 site [https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/gdb/ here] (we chose [http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/gdb/x86_64-w64-mingw32-gdb-7.1.90.20100730.zip/download x86_64-w64-mingw32-gdb-7.1.90.20100730.zip])
	* Building GDB from source tarball version 7.3.1 worked OK but the resulting GDB didn't recognise/load symbols from the running executable. So download the MinGW-64 pre-compiled version instead.

	== Runtime prerequisites ==		== Runtime prerequisites ==
Line 85:		Line 75:
	** [http://sourceforge.net/projects/ascend-sim/files/thirdparty/pygobject-2.28.6.win-amd64-py2.7.exe/download pygobject-2.28.6.win-amd64-py2.7.exe]		** [http://sourceforge.net/projects/ascend-sim/files/thirdparty/pygobject-2.28.6.win-amd64-py2.7.exe/download pygobject-2.28.6.win-amd64-py2.7.exe]
	** [http://sourceforge.net/projects/ascend-sim/files/thirdparty/py2cairo-1.10.0.win-amd64-py2.7.exe/download py2cairo-1.10.0.win-amd64-py2.7.exe]		** [http://sourceforge.net/projects/ascend-sim/files/thirdparty/py2cairo-1.10.0.win-amd64-py2.7.exe/download py2cairo-1.10.0.win-amd64-py2.7.exe]
	* ~~From~~ http://www.lfd.uci.edu/~gohlke/pythonlibs, ~~download and install~~ the '''win-amd64-py2.7''' versions ~~of each of~~ the ~~following (sorry, this website doesn~~'~~t allow direct URL links)~~:		* In order to have plotting and console support in the PyGTK GUI, Download and install the following Python packages from http://www.lfd.uci.edu/~gohlke/pythonlibs (sorry, this website doesn't allow direct URL links). Be sure to use the'''win-amd64-py2.7''' versions for 64-bit Python, or the '''win32-py2.7''' files for 32-bit Python:
	** six (required for dateutil)		** six (required for dateutil)
	** pyparsing (required for matplotlib)		** pyparsing (required for matplotlib)

Jpye: /* CUnit testing library */

2013-12-04T04:57:16Z

CUnit testing library

← Older revision		Revision as of 04:57, 4 December 2013
Line 11:		Line 11:
	cd cunit		cd cunit
	./configure --prefix=/mingw --enable-examples --enable-debug		./configure --prefix=/mingw --enable-examples --enable-debug
	make ~~-j4~~		make
	make install		make install

Jpye: /* SUNDIALS */

2013-12-04T04:57:06Z

SUNDIALS

← Older revision		Revision as of 04:57, 4 December 2013
Line 30:		Line 30:
	cd sundials-2.4.0		cd sundials-2.4.0
	./configure --build=x86_64-w64-mingw32 --prefix=/mingw F77=gfortran		./configure --build=x86_64-w64-mingw32 --prefix=/mingw F77=gfortran
	make ~~-j4~~		make
	make install		make install

Jpye: /* IPOPT */

2013-12-04T04:56:58Z

IPOPT

← Older revision		Revision as of 04:56, 4 December 2013
Line 54:		Line 54:
	cd ~/Ipopt-3.11.3		cd ~/Ipopt-3.11.3
	./configure --enable-static=yes --enable-shared=no --prefix=/mingw ADD_FFLAGS="-fopenmp -static-libgcc" --disable-pthread-mumps		./configure --enable-static=yes --enable-shared=no --prefix=/mingw ADD_FFLAGS="-fopenmp -static-libgcc" --disable-pthread-mumps
	make ~~-j4~~		make
	make install		make install
	make test		make test

Jpye: /* IPOPT */

2013-12-04T04:29:07Z

IPOPT

← Older revision		Revision as of 04:29, 4 December 2013
Line 42:		Line 42:

	* Download and unpack [http://www.coin-or.org/download/source/Ipopt/Ipopt-3.11.3.tgz Ipopt-3.11.3.tgz]:		* Download and unpack [http://www.coin-or.org/download/source/Ipopt/Ipopt-3.11.3.tgz Ipopt-3.11.3.tgz]:
			cd ~
	wget http://www.coin-or.org/download/source/Ipopt/Ipopt-3.11.3.tgz		wget http://www.coin-or.org/download/source/Ipopt/Ipopt-3.11.3.tgz
	tar zxf Ipopt-3.11.3.tgz		tar zxf Ipopt-3.11.3.tgz
Line 51:		Line 52:
	cd ../Lapack && ./get.Lapack		cd ../Lapack && ./get.Lapack
	* Configure and build IPOPT (configuration takes a several minutes, building takes ~15 min or so):		* Configure and build IPOPT (configuration takes a several minutes, building takes ~15 min or so):
			cd ~/Ipopt-3.11.3
	./configure --enable-static=yes --enable-shared=no --prefix=/mingw ADD_FFLAGS="-fopenmp -static-libgcc" --disable-pthread-mumps		./configure --enable-static=yes --enable-shared=no --prefix=/mingw ADD_FFLAGS="-fopenmp -static-libgcc" --disable-pthread-mumps
	make -j4		make -j4
Line 56:		Line 58:
	make test		make test

	Thanks for Stefan Vigerske and Tony Kelman for their help with these instructions (and for [http://www.mpclab.net/Trac/wiki/CompilingIpopt#MinGW this page]), and for the suggested changes to our [[Setting up a MinGW-w64 build environment\|MinGW-w64 set-up guidelines]]. See also [https://projects.coin-or.org/Ipopt/ticket/215 IPOPT bug 215].		Note: above <tt>./configure</tt> command is a special workaround for 64-bit Windows. Thanks for Stefan Vigerske and Tony Kelman for their help with these instructions (and for [http://www.mpclab.net/Trac/wiki/CompilingIpopt#MinGW this page]), and for the suggested changes to our [[Setting up a MinGW-w64 build environment\|MinGW-w64 set-up guidelines]]. See also [https://projects.coin-or.org/Ipopt/ticket/215 IPOPT bug 215]. It is probable that on 32-bit, a simpler command without the 'ADD_FFLAGS' will work OK, but it may change the resulting DLL dependencies of the final DLL/executables.

	If the install works OK you should have some /mingw/libcoin* and /mingw/libipopt.a files.		If the install works OK you should have some /mingw/libcoin* and /mingw/libipopt.a files.

Jpye: /* SUNDIALS */

2013-12-04T04:11:21Z

SUNDIALS

← Older revision		Revision as of 04:11, 4 December 2013
Line 34:		Line 34:

	SUNDIALS at v2.4.0 doesn't support <tt>DESTDIR=~/temp-install</tt> in the <tt>make install</tt> step, which is annoying becuase it's not quite as easy to 'catch' the installed files and distribute a binary.		SUNDIALS at v2.4.0 doesn't support <tt>DESTDIR=~/temp-install</tt> in the <tt>make install</tt> step, which is annoying becuase it's not quite as easy to 'catch' the installed files and distribute a binary.

			Note, for 32-bit, use <tt>./configure --prefix=/mingw F77=gfortran</tt> above. We need to test again whether the <tt>--build=x86_64-w64-mingw32</tt> part is needed for 64-bit builds, or not.

	=== IPOPT ===		=== IPOPT ===

Jpye: /* Runtime prerequisites */

2013-11-27T07:07:15Z

Runtime prerequisites

← Older revision		Revision as of 07:07, 27 November 2013
Line 82:		Line 82:
	** [http://sourceforge.net/projects/ascend-sim/files/thirdparty/py2cairo-1.10.0.win-amd64-py2.7.exe/download py2cairo-1.10.0.win-amd64-py2.7.exe]		** [http://sourceforge.net/projects/ascend-sim/files/thirdparty/py2cairo-1.10.0.win-amd64-py2.7.exe/download py2cairo-1.10.0.win-amd64-py2.7.exe]
	* From http://www.lfd.uci.edu/~gohlke/pythonlibs, download and install the '''win-amd64-py2.7''' versions of each of the following (sorry, this website doesn't allow direct URL links):		* From http://www.lfd.uci.edu/~gohlke/pythonlibs, download and install the '''win-amd64-py2.7''' versions of each of the following (sorry, this website doesn't allow direct URL links):
	** pyparsing (required for matplotlib)		** six (required for dateutil)
			** pyparsing (required for matplotlib)
	** dateutil (required for matplotlib)		** dateutil (required for matplotlib)
	** numpy-MKL (required for matplotlib)		** numpy-MKL (required for matplotlib)