Older instructions

From NEOSYS Dev Wiki
Jump to navigationJump to search

Building x64

x64/Release

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

setenv /x64 /release

cd common
msbuild /p:Platform=x64 /p:Configuration=Release
cd ..

cd i18n
msbuild /p:Platform=x64 /p:Configuration=Release
cd ..

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


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)

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

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

setenv /x64 /debug

rem vsvars32 MUST be after setenv
vsvars32 x64

cd common
msbuild /p:Platform=x64 /p:Configuration=Debug
cd ..

cd i18n
msbuild /p:Platform=x64 /p:Configuration=Debug
cd ..

dir ..\lib64\*d.lib
rem should find lib64 folder has icuucd.lib and icuind.lib


Building Win32 (x86) Release and Debug

x86/Release

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

setenv /x86 /release

cd common
msbuild /p:Platform=win32 /p:Configuration=Release
cd ..

cd i18n
msbuild /p:Platform=win32 /p:Configuration=Release
cd ..

dir ..\lib\*.lib
rem should find lib folder has icudt.lib, icuuc.lib and icuin.lib

x86/Debug

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

setenv /x86 /debug

rem must be AFTER setenv
vsvars32 x86

cd common
msbuild /p:Platform=win32 /p:Configuration=Debug
cd ..

cd i18n
msbuild /p:Platform=win32 /p:Configuration=Debug
cd ..

dir ..\lib\*d.lib
rem should find lib folder has icuucd.lib and icuind.lib