Tutorial:Compiling & Installing SWORD on Windows - Revision history

David Haslam: /* Compilation of Sword */ Category:SWORD

2018-01-11T14:03:37Z

Compilation of Sword: Category:SWORD

← Older revision		Revision as of 14:03, 11 January 2018
Line 212:		Line 212:

	[[Category:Tutorials]]		[[Category:Tutorials]]
			[[Category:SWORD]]

Daniel Sheffield: /* Building SWORD */ edited note.

2015-01-07T02:29:35Z

Building SWORD: edited note.

← Older revision		Revision as of 02:29, 7 January 2015
Line 162:		Line 162:
	#		#
	`echo $(tail -n1 CMakeFiles/sword.dir/link.txt) -licudt -licuuc`		`echo $(tail -n1 CMakeFiles/sword.dir/link.txt) -licudt -licuuc`
	NOTE: the directory that your libcurl.dll ends up in might be different to mine - but it will be something like build/libcurl-blah-release-dll-blah-blah-blah/bin/libcurl.dll		NOTE: the directory that your libcurl.dll ends up in might be different to mine - but it will be something like build/libcurl-blah-release-dll-blah-blah-blah/bin/libcurl.dll. I also had to rename liblzma.dll to liblzma-5.dll for some reason...

	== Cross Compiling Sword for MS Windows on Suse Linux with MingW ==		== Cross Compiling Sword for MS Windows on Suse Linux with MingW ==

Daniel Sheffield: /* Aquire icu */ minor correction

2015-01-07T02:21:24Z

Aquire icu: minor correction

← Older revision		Revision as of 02:21, 7 January 2015
Line 88:		Line 88:
	Inflate the zip or tar archive to $BUILD_DIR/icu		Inflate the zip or tar archive to $BUILD_DIR/icu
	#		#
	# Make icu for linux first:		# Make icu for linux first...
	#
	cd $BUILD_DIR/icu/source/		cd $BUILD_DIR/icu/source/
	mkdir linux-build		mkdir linux-build
Line 95:		Line 94:
	../source/runConfigureICU Linux		../source/runConfigureICU Linux
	#		#
	# then cross-compile for windows:		# ...then cross-compile for windows...
	#
	cd $BUILD_DIR/icu/source		cd $BUILD_DIR/icu/source
	mkdir win-build		mkdir win-build
	cd win-build		cd win-build
	~~../source/runConfigureICU MinGW --host=i686-w64-mingw32 --with-cross-build=$BUILD_DIR/icu/linux-build~~
	#		#
	# ~~then set up the include dir for use~~ with ~~cmake~~		# ...making sure we are being consistant with which compiler we are using by setting CC and CXX...
			CC=/opt/mxe/usr/bin/i686-w64-mingw32-gcc CXX=/opt/mxe/usr/bin/i686-w64-mingw32-g++ ../source/runConfigureICU MinGW --host=i686-w64-mingw32 --with-cross-build=$BUILD_DIR/icu/linux-build
	#		#
			# Finally, set up the include dir for use with cmake
	cd $BUILD_DIR/icu		cd $BUILD_DIR/icu
	cp -r source/*/unicode/ include/		cp -r source/*/unicode/ include/

Daniel Sheffield: /* Building SWORD */ Note on libcurl

2015-01-06T11:13:56Z

Building SWORD: Note on libcurl

← Older revision		Revision as of 11:13, 6 January 2015
Line 119:		Line 119:
	cd $BUILD_DIR/sword/cmakebuild		cd $BUILD_DIR/sword/cmakebuild

	If you want to use dynamics libraries:		If you want to use the dynamics libraries (recommended):
	cmake -DREGEX_INCLUDE_DIR= \		cmake -DREGEX_INCLUDE_DIR= \
	-DCURL_LIBRARY=$BUILD_DIR/curl/builds/libcurl-vc-x86-release-dll-ipv6-sspi-winssl/bin/libcurl.dll \		-DCURL_LIBRARY=$BUILD_DIR/curl/builds/libcurl-vc-x86-release-dll-ipv6-sspi-winssl/bin/libcurl.dll \
Line 135:		Line 135:
	make sword		make sword
	: ...or if you want to use MXE's system libraries:		: ...or if you want to use MXE's system libraries:
			#
			# I couldn't link against MXE's static build of libcurl.
			# It might be to do with this: http://curl.haxx.se/docs/faq.html#Link_errors_when_building_libcur
			#
	cmake -DREGEX_INCLUDE_DIR= \		cmake -DREGEX_INCLUDE_DIR= \
			-DCURL_LIBRARY=$BUILD_DIR/curl/builds/libcurl-vc-x86-release-dll-ipv6-sspi-winssl/bin/libcurl.dll \
			-DCURL_INCLUDE_DIR=$BUILD_DIR/curl/include \
	-DICU_LIBRARY=$BUILD_DIR/icu/win-build/lib/icuuc54.dll \		-DICU_LIBRARY=$BUILD_DIR/icu/win-build/lib/icuuc54.dll \
	-DICU_I18N_LIBRARY=$BUILD_DIR/icu/win-build/lib/icuin54.dll \		-DICU_I18N_LIBRARY=$BUILD_DIR/icu/win-build/lib/icuin54.dll \
Line 142:		Line 148:
	make sword		make sword
	: ...or if you want to use MXE's system ICU too:		: ...or if you want to use MXE's system ICU too:
			#
			# I couldn't link against MXE's static build of libcurl.
			# It might be to do with this: http://curl.haxx.se/docs/faq.html#Link_errors_when_building_libcur
			#
	cmake -DREGEX_INCLUDE_DIR= \		cmake -DREGEX_INCLUDE_DIR= \
			-DCURL_LIBRARY=$BUILD_DIR/curl/builds/libcurl-vc-x86-release-dll-ipv6-sspi-winssl/bin/libcurl.dll \
			-DCURL_INCLUDE_DIR=$BUILD_DIR/curl/include \
	-DCMAKE_TOOLCHAIN_FILE=/opt/mxe/usr/i686-w64-mingw32/share/cmake/mxe-conf.cmake -G "Unix Makefiles" ..		-DCMAKE_TOOLCHAIN_FILE=/opt/mxe/usr/i686-w64-mingw32/share/cmake/mxe-conf.cmake -G "Unix Makefiles" ..
	make sword		make sword
Line 151:		Line 163:
	#		#
	`echo $(tail -n1 CMakeFiles/sword.dir/link.txt) -licudt -licuuc`		`echo $(tail -n1 CMakeFiles/sword.dir/link.txt) -licudt -licuuc`
			NOTE: the directory that your libcurl.dll ends up in might be different to mine - but it will be something like build/libcurl-blah-release-dll-blah-blah-blah/bin/libcurl.dll

	== Cross Compiling Sword for MS Windows on Suse Linux with MingW ==		== Cross Compiling Sword for MS Windows on Suse Linux with MingW ==

Daniel Sheffield: Cross-compiling with MinGW. Improved instructions. Plus minor formatting fixes.

2015-01-06T11:01:34Z

Cross-compiling with MinGW. Improved instructions. Plus minor formatting fixes.

Show changes

Daniel Sheffield: Cross Compiling Sword for MS Windows on Linux with MingW -- working

2015-01-06T10:05:12Z

Cross Compiling Sword for MS Windows on Linux with MingW -- working

← Older revision		Revision as of 10:05, 6 January 2015
Line 142:		Line 142:
	../source/runConfigureICU MinGW --host=i686-w64-mingw32 --with-cross-build=$BUILD_DIR/icu/linux-build		../source/runConfigureICU MinGW --host=i686-w64-mingw32 --with-cross-build=$BUILD_DIR/icu/linux-build

	~~:: Download the latest icu binaries. At time of writing, icu54 [http://site.icu-project.org/download/54]. I downloaded icu4c-54_1-Win32-msvc10.zip.~~
	:: Set up include dir for use with cmake		:: Set up include dir for use with cmake
	cd $BUILD_DIR		cd $BUILD_DIR/icu
	~~unzip~~ /~~path-to-downloaded-icu/icu4c-54_1-Win32-msvc10.zip -d~~ icu~~-bin~~		cp -r source/*/unicode/ include/
	cp -r ~~icu-bin~~/~~icu~~/include ~~icu~~

	:: Make an out of source-directory-for cmake.		:: Make an out of source-directory-for cmake.
Line 169:		Line 167:
	make sword		make sword

	:: You will get an error at the very end of make sword. These are just link errors in CMakFiles/sword.dir/link.txt (similarly in CMakeFiles/buildtest.dir/link.txt). These errors do not affect the static build of libsword which you can get by typing 'make' instead of 'make sword'.

	[[Category:Tutorials]]		[[Category:Tutorials]]

Daniel Sheffield: Cross-compile instructions with cmake -- not finished yet

2015-01-06T09:51:43Z

Cross-compile instructions with cmake -- not finished yet

← Older revision		Revision as of 09:51, 6 January 2015
Line 118:		Line 118:


			== Cross Compiling Sword for MS Windows on Linux with MingW ==
			NOTE: these instructions do not include CLucene.

			:: Create a build directory $BUILD_DIR.

			svn co https://www.crosswire.org/svn/sword/trunk/ $BUILD_DIR/sword

			:: Download and install MXE. Steps 1 and 2 of the tutorial here [http://mxe.cc/#tutorial].
			:: In MXE's install dir ('/opt/mxe' in the tutorial), set up the build environment as follows:

			make MXE_TARGETS='i686-w64-mingw32' gcc zlib bzip2 xz curl icu

			:: Make icu for linux
			cd $BUILD_DIR/icu/source/
			mkdir linux-build
			cd linux-build
			../source/runConfigureICU Linux

			:: Cross-compile for windows
			cd $BUILD_DIR/icu/source
			mkdir win-build
			cd win-build
			../source/runConfigureICU MinGW --host=i686-w64-mingw32 --with-cross-build=$BUILD_DIR/icu/linux-build

			:: Download the latest icu binaries. At time of writing, icu54 [http://site.icu-project.org/download/54]. I downloaded icu4c-54_1-Win32-msvc10.zip.
			:: Set up include dir for use with cmake
			cd $BUILD_DIR
			unzip /path-to-downloaded-icu/icu4c-54_1-Win32-msvc10.zip -d icu-bin
			cp -r icu-bin/icu/include icu

			:: Make an out of source-directory-for cmake.

			mkdir $BUILD_DIR/sword/cmakebuild
			cd $BUILD_DIR/sword/cmakebuild

			:: Make with the following command
			cmake -DREGEX_INCLUDE_DIR= \
			-DCURL_LIBRARY=$BUILD_DIR/curl/builds/libcurl-vc-x86-release-dll-ipv6-sspi-winssl/bin/libcurl.dll \
			-DCURL_INCLUDE_DIR=$BUILD_DIR/curl/include \
			-DXZ_LIBRARY=$BUILD_DIR/xz/bin_i486/liblzma.dll \
			-DXZ_INCLUDE_DIR=$BUILD_DIR/xz/include \
			-DZLIB_LIBRARY=$BUILD_DIR/zlib/zlib1.dll \
			-DZLIB_INCLUDE_DIR=$BUILD_DIR/zlib \
			-DICU_LIBRARY=$BUILD_DIR/icu/win-build/lib/icuuc54.dll \
			-DICU_I18N_LIBRARY=$BUILD_DIR/icu/win-build/lib/icuin54.dll \
			-DICU_INCLUDE_DIR=$BUILD_DIR/icu/include \
			-DBZIP2_LIBRARY=$BUILD_DIR/bzip2/libbz2.dll \
			-DBZIP2_LIBRARY=$BUILD_DIR/bzip2 \
			-DCMAKE_TOOLCHAIN_FILE=/opt/mxe/usr/i686-w64-mingw32/share/cmake/mxe-conf.cmake -G "Unix Makefiles" ..
			make sword

			:: You will get an error at the very end of make sword. These are just link errors in CMakFiles/sword.dir/link.txt (similarly in CMakeFiles/buildtest.dir/link.txt). These errors do not affect the static build of libsword which you can get by typing 'make' instead of 'make sword'.

	[[Category:Tutorials]]		[[Category:Tutorials]]

Osk: /* Compiling utilities */

2014-03-19T10:22:38Z

Compiling utilities

← Older revision		Revision as of 10:22, 19 March 2014
Line 68:		Line 68:
	=== Compiling utilities ===		=== Compiling utilities ===
	# Open $dir$\sword-$version$\utilities\vcppmake\utilities.sln		# Open $dir$\sword-$version$\utilities\vcppmake\utilities.sln
	# Build ~~all~~ (~~Click Build \| Batch Build... \| Select All \| Build~~)		# Build the solution (Release, Debug, or both)

	== Cross Compiling Sword for MS Windows on Suse Linux with MingW ==		== Cross Compiling Sword for MS Windows on Suse Linux with MingW ==

Osk: /* Compiling libsword */

2014-03-19T10:00:21Z

Compiling libsword

← Older revision		Revision as of 10:00, 19 March 2014
Line 60:		Line 60:

	=== Compiling libsword ===		=== Compiling libsword ===
	# Download the latest release of [http://www.crosswire.org/ftpmirror/pub/sword/source/sword.tar.gz The SWORD Project]		# Download the latest release of [http://www.crosswire.org/ftpmirror/pub/sword/source/sword.tar.gz The SWORD Project] or download a copy from SVN: https://www.crosswire.org/svn/sword/trunk/
	# Extract the tarball to $dir$		# Extract the tarball to $dir$
	::If you are building utilities or diatheke, the following steps are not necessary:		::If you are building utilities or diatheke, the following steps are not necessary:
	# Open $dir$\sword-$version$\lib\vcppmake~~\vc8~~\libsword.~~vcproj~~		# Open $dir$\sword-$version$\lib\vcppmake\libsword.sln
	# Build ~~all~~ (~~Click Build \| Batch Build... \| Select All \| Build~~)		# Build the solution (Release, Debug, or both)

	=== Compiling utilities ===		=== Compiling utilities ===

Osk: added zlib build instructions

2014-03-19T09:55:34Z

added zlib build instructions

← Older revision		Revision as of 09:55, 19 March 2014
Line 18:		Line 18:
	# Open $dir$\icu\source\allinone\allinone.sln		# Open $dir$\icu\source\allinone\allinone.sln
	# Ensure that the Win32 Release configuration is selected and build the solution		# Ensure that the Win32 Release configuration is selected and build the solution

			=== Compiling zlib ===
			# Download the latest release of [http://www.zlib.net/ zlib] source code. At writing, the latest version is 1.2.8: [http://prdownloads.sourceforge.net/libpng/zlib128.zip?download]
			# Extract the archive to $dir$ and rename the directory "zlib" (with no version number)
			# Start a Developer Command Prompt (find this on your Start Menu in the Visual Studio 2013 \| Visual Studio Tools menu)
			# cd to $dir$/zlib
			# Execute: nmake /f win32/Makefile.msc

	=== Compiling bzip2 ===		=== Compiling bzip2 ===
	# Download the latest release of [http://www.bzip.org/downloads.html bzip2]. At writing, the latest version is 1.0.6: [http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz]		# Download the latest release of [http://www.bzip.org/downloads.html bzip2]. At writing, the latest version is 1.0.6: [http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz]
	# Extract the archive to $dir$ and rename the directory bzip2		# Extract the archive to $dir$ and rename the directory "bzip2"
	# Open $dir$\bzip2\libbz2.dsp and allow Visual Studio to update the project		# Open $dir$\bzip2\libbz2.dsp and allow Visual Studio to update the project
	# Ensure that the Release configuration is selected and build the solution		# Ensure that the Release configuration is selected and build the solution