Building ICU 32/64 on Windows - Revision history

Steve: /* Specimen Build Platform/Environment */

2011-06-23T13:03:57Z

Specimen Build Platform/Environment

← Older revision		Revision as of 13:03, 23 June 2011
Line 9:		Line 9:
	*windows server 2008 R2 SP1 64		*windows server 2008 R2 SP1 64
	*install sdk7.1 minimally		*install sdk7.1 minimally
	*install visual studio c++ 2010 express		*install visual studio c++ 2010 express (optional if not building debug libs)

	VS is needed for building debug versions even while doing command line build. It might even be needed for building release versions if the projects arent setup quite right for msbuild+sdk only. Presence of VS doesnt mean that we are going to use GUI		VS is needed for building debug versions even while doing command line build. It might even be needed for building release versions if the projects arent setup quite right for msbuild+sdk only. Presence of VS doesnt mean that we are going to use GUI

Steve at 13:02, 23 June 2011

2011-06-23T13:02:08Z

@@ Line 23: / Line 23: @@
   f:\icu4c-4_6_1-src
-== Building x64 ==
+== Script to build x86 x64 Release+Debug ==
-=== x64/Release ===
+Can make VS2005 VS2008 VS2010 if you amend parameters in the heading
-<pre>
+ rem xp 2008 win7 for VS2005 VS2008 VS2010 respectively
-rem >>>Windows SDK 7.1 Command Prompt
+ set SETENV_TARGET=2008
-setenv /x64 /release
+http://code.google.com/p/exodusdb/source/browse/trunk/buildicu.cmd
-cd common
+[[older instructions]]

Steve at 01:15, 16 May 2011

2011-05-16T01:15:02Z

← Older revision		Revision as of 01:15, 16 May 2011
Line 32:		Line 32:
	cd \icu4c-4_6_1-src\icu\source		cd \icu4c-4_6_1-src\icu\source

	setenv /release		setenv /x64 /release

	cd common		cd common
Line 58:		Line 58:
	cd \icu4c-4_6_1-src\icu\source		cd \icu4c-4_6_1-src\icu\source

	setenv /debug		setenv /x64 /debug

	rem vsvars32 MUST be after setenv		rem vsvars32 MUST be after setenv
Line 84:		Line 84:
	cd \icu4c-4_6_1-src\icu\source		cd \icu4c-4_6_1-src\icu\source

	setenv /release ~~/x86~~		setenv /x86 /release

	cd common		cd common
Line 105:		Line 105:
	cd \icu4c-4_6_1-src\icu\source		cd \icu4c-4_6_1-src\icu\source

	setenv /debug ~~/x86~~		setenv /x86 /debug

	rem must be AFTER setenv		rem must be AFTER setenv

Steve at 01:12, 16 May 2011

2011-05-16T01:12:10Z

← Older revision		Revision as of 01:12, 16 May 2011
Line 22:		Line 22:

	f:\icu4c-4_6_1-src		f:\icu4c-4_6_1-src

	~~Open sdk7.1 command prompt and get into icu source folder~~

	~~>>>Windows SDK 7.1 Command Prompt~~
	f:
	~~cd \icu4c-4_6_1-src\icu\source~~

	== Building x64 ==		== Building x64 ==
Line 34:		Line 28:

	<pre>		<pre>
			rem >>>Windows SDK 7.1 Command Prompt
			f:
			cd \icu4c-4_6_1-src\icu\source

	setenv /release		setenv /release

Line 45:		Line 43:

	dir ..\lib64\*.lib		dir ..\lib64\*.lib
			rem should find lib64 folder has icudt.lib, icuuc.lib and icuin.lib
	</pre>		</pre>

	~~Check the lib64 folder for icudt.lib, icuuc.lib and icuin.lib~~

	=== x64/Debug ===		=== x64/Debug ===
Line 53:		Line 51:
	Producing the proper debug versions of icu may not be necessary if your objective is only to produce release versions of the boost libraries (and you use the work-around to avoid the need for icu debug libraries)		Producing the proper debug versions of icu may not be necessary if your objective is only to produce release versions of the boost libraries (and you use the work-around to avoid the need for icu debug libraries)

	NOTE: To produce the DEBUG version of the libraries, you need Visual Studio's bscmake on the path.		NOTE: To produce the DEBUG version of the libraries, you need Visual Studio's bscmake on the path - vsvars32 does that.

	~~vsvars32 must be done AFTER setenv~~.		<pre>
			rem >>>Windows SDK 7.1 Command Prompt
			f:
			cd \icu4c-4_6_1-src\icu\source

	~~<pre>~~
	setenv /debug		setenv /debug

			rem vsvars32 MUST be after setenv
	vsvars32 x64		vsvars32 x64

Line 71:		Line 72:

	dir ..\lib64\*d.lib		dir ..\lib64\*d.lib
			rem should find lib64 folder has icuucd.lib and icuind.lib
	</pre>		</pre>

	~~Check the lib64 folder for icuucd.lib and icuind.lib~~

	== Building Win32 (x86) Release and Debug==		== Building Win32 (x86) Release and Debug==
Line 79:		Line 80:
	=== x86/Release ===		=== x86/Release ===
	<pre>		<pre>
			rem >>>Windows SDK 7.1 Command Prompt
	f:		f:
	cd \icu4c-4_6_1-src\icu\source		cd \icu4c-4_6_1-src\icu\source
Line 93:		Line 95:

	dir ..\lib\*.lib		dir ..\lib\*.lib
			rem should find lib folder has icudt.lib, icuuc.lib and icuin.lib
	</pre>		</pre>

Line 98:		Line 101:

	<pre>		<pre>
			rem >>>Windows SDK 7.1 Command Prompt
			f:
			cd \icu4c-4_6_1-src\icu\source

	setenv /debug /x86		setenv /debug /x86

Line 112:		Line 119:

	dir ..\lib\*d.lib		dir ..\lib\*d.lib
			rem should find lib folder has icuucd.lib and icuind.lib
	</pre>		</pre>

Steve at 01:03, 16 May 2011

2011-05-16T01:03:17Z

← Older revision		Revision as of 01:03, 16 May 2011
Line 93:		Line 93:

	dir ..\lib\*.lib		dir ..\lib\*.lib
	~~@if not exist ..\lib\icudt.lib @echo ..\lib\icudt.lib not built!~~
	~~@if not exist ..\lib\icuin.lib @echo ..\lib\icuin.lib not built!~~
	~~@if not exist ..\lib\icuuc.lib @echo ..\lib\icuuc.lib not built!~~
	</pre>		</pre>

Line 115:		Line 112:

	dir ..\lib\*d.lib		dir ..\lib\*d.lib
	~~@if not exist ..\lib\icuind.lib @echo ..\lib\icuind.lib not built!~~
	~~@if not exist ..\lib\icuucd.lib @echo ..\lib\icuucd.lib not built!~~
	</pre>		</pre>

Steve at 01:01, 16 May 2011

2011-05-16T01:01:58Z

← Older revision		Revision as of 01:01, 16 May 2011
Line 1:		Line 1:
	== Building ICU common and i18n projects for Boost ==		= Building ICU common and i18n projects for Boost =

	You do not need to build the whole of ICU just to get icudt.lib, icuuc.lib and icuin.lib required by boost regex for unicode aware regex. The "common" project makes icudt.lib icuuc.lib and the "i18n" project makes icuin.lib		You do not need to build the whole of ICU just to get icudt.lib, icuuc.lib and icuin.lib required by boost regex for unicode aware regex. The "common" project makes icudt.lib icuuc.lib and the "i18n" project makes icuin.lib
Line 5:		Line 5:
	The release configuration of ICU can be built with SDK only. Visual Studio is only needed to create debug versions. Visual Studio Express is sufficient and it can be run in command mode.		The release configuration of ICU can be built with SDK only. Visual Studio is only needed to create debug versions. Visual Studio Express is sufficient and it can be run in command mode.

	=== Specimen Build Platform/Environment ===		== Specimen Build Platform/Environment ==

	*windows server 2008 R2 SP1 64		*windows server 2008 R2 SP1 64
Line 13:		Line 13:
	VS is needed for building debug versions even while doing command line build. It might even be needed for building release versions if the projects arent setup quite right for msbuild+sdk only. Presence of VS doesnt mean that we are going to use GUI		VS is needed for building debug versions even while doing command line build. It might even be needed for building release versions if the projects arent setup quite right for msbuild+sdk only. Presence of VS doesnt mean that we are going to use GUI

	=== Get ICU Source ===		== Get ICU Source ==

	Download		Download
Line 29:		Line 29:
	cd \icu4c-4_6_1-src\icu\source		cd \icu4c-4_6_1-src\icu\source

	=== Building x64 ===		== Building x64 ==

	==== x64/Release ====		=== x64/Release ===

	<pre>		<pre>
Line 49:		Line 49:
	Check the lib64 folder for icudt.lib, icuuc.lib and icuin.lib		Check the lib64 folder for icudt.lib, icuuc.lib and icuin.lib

	==== x64/Debug ====		=== x64/Debug ===

	Producing the proper debug versions of icu may not be necessary if your objective is only to produce release versions of the boost libraries (and you use the work-around to avoid the need for icu debug libraries)		Producing the proper debug versions of icu may not be necessary if your objective is only to produce release versions of the boost libraries (and you use the work-around to avoid the need for icu debug libraries)
Line 75:		Line 75:
	Check the lib64 folder for icuucd.lib and icuind.lib		Check the lib64 folder for icuucd.lib and icuind.lib

	=== Building Win32 (x86) Release and Debug~~===~~		== Building Win32 (x86) Release and Debug==

	~~==== x86/Release ==~~==

			=== x86/Release ===
	<pre>		<pre>
	f:		f:
Line 99:		Line 98:
	</pre>		</pre>

	==== x86/Debug ====		=== x86/Debug ===

	<pre>		<pre>

Steve: /* Building Win32 (x86) Release and Debug */

2011-05-16T00:56:47Z

Building Win32 (x86) Release and Debug

← Older revision		Revision as of 00:56, 16 May 2011
Line 76:		Line 76:

	=== Building Win32 (x86) Release and Debug===		=== Building Win32 (x86) Release and Debug===

			==== x86/Release ====

	<pre>		<pre>
Line 91:		Line 93:
	cd ..		cd ..

			dir ..\lib\*.lib
	@if not exist ..\lib\icudt.lib @echo ..\lib\icudt.lib not built!		@if not exist ..\lib\icudt.lib @echo ..\lib\icudt.lib not built!
	@if not exist ..\lib\icuin.lib @echo ..\lib\icuin.lib not built!		@if not exist ..\lib\icuin.lib @echo ..\lib\icuin.lib not built!
	@if not exist ..\lib\icuuc.lib @echo ..\lib\icuuc.lib not built!		@if not exist ..\lib\icuuc.lib @echo ..\lib\icuuc.lib not built!
			</pre>

			==== x86/Debug ====

			<pre>
	setenv /debug /x86		setenv /debug /x86

			rem must be AFTER setenv
	vsvars32 x86		vsvars32 x86

Line 108:		Line 115:
	cd ..		cd ..

			dir ..\lib\*d.lib
	@if not exist ..\lib\icuind.lib @echo ..\lib\icuind.lib not built!		@if not exist ..\lib\icuind.lib @echo ..\lib\icuind.lib not built!
	@if not exist ..\lib\icuucd.lib @echo ..\lib\icuucd.lib not built!		@if not exist ..\lib\icuucd.lib @echo ..\lib\icuucd.lib not built!
	</pre>		</pre>

Steve: /* x64/Release */

2011-05-16T00:51:20Z

x64/Release

← Older revision		Revision as of 00:51, 16 May 2011
Line 44:		Line 44:
	cd ..		cd ..

	dir ..\lib64		dir ..\lib64\*.lib
	</pre>		</pre>

Steve: /* x64/Debug */

2011-05-16T00:49:51Z

x64/Debug

← Older revision		Revision as of 00:49, 16 May 2011
Line 53:		Line 53:
	Producing the proper debug versions of icu may not be necessary if your objective is only to produce release versions of the boost libraries (and you use the work-around to avoid the need for icu debug libraries)		Producing the proper debug versions of icu may not be necessary if your objective is only to produce release versions of the boost libraries (and you use the work-around to avoid the need for icu debug libraries)

	~~setenv /debug~~		NOTE: To produce the DEBUG version of the libraries, you need Visual Studio's bscmake on the path.

	~~NOTE: To produce the DEBUG version of the libraries, you need Visual Studio's bscmake on the path. This~~ must be done ~~after~~ setenv.		vsvars32 must be done AFTER setenv.

	<pre>		<pre>
			setenv /debug

	vsvars32 x64		vsvars32 x64

Line 67:		Line 69:
	msbuild /p:Platform=x64 /p:Configuration=Debug		msbuild /p:Platform=x64 /p:Configuration=Debug
	cd ..		cd ..

			dir ..\lib64\*d.lib
	</pre>		</pre>

	Check the lib64 folder for icuucd.lib and icuind.lib		Check the lib64 folder for icuucd.lib and icuind.lib


	=== Building Win32 (x86) Release and Debug===		=== Building Win32 (x86) Release and Debug===

Steve: /* x64/Release */

2011-05-16T00:48:00Z

x64/Release

← Older revision		Revision as of 00:48, 16 May 2011
Line 43:		Line 43:
	msbuild /p:Platform=x64 /p:Configuration=Release		msbuild /p:Platform=x64 /p:Configuration=Release
	cd ..		cd ..

			dir ..\lib64
	</pre>		</pre>