luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-04 18:26:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update Visual Studio README.txt's

Browse Source 
-The VS2010 README.txt should have Windows CRLF EOL.
-Tell people about the added dependency on LibFFI
This commit is contained in:
Chun-wei Fan 2011-06-29 14:07:38 +08:00
parent 1777614600
commit d1e26c51c8
2 changed files with 78 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
build/win32/vs10/README.txt
View File

@ -7,7 +7,7 @@ the .in files needed, mainly config.h.win32.in into config.h.win32 and
glibconfig.h.win32.in into glibconfig.h.win32. You will also need to glibconfig.h.win32.in into glibconfig.h.win32. You will also need to
expand the .vcprojin files here into .vcproj files. expand the .vcprojin files here into .vcproj files.
The required dependencies are zlib and proxy-libintl. Fetch the latest The required dependencies are zlib, proxy-libintl and LibFFI. Fetch the latest
proxy-libintl-dev and zlib-dev zipfiles from proxy-libintl-dev and zlib-dev zipfiles from
http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit
builds, and correspondingly builds, and correspondingly
@ -18,6 +18,12 @@ One may wish to build his/her own ZLib-It is recommended that ZLib is
built using the win32/Makefile.msc makefile with VS10 with the ASM routines built using the win32/Makefile.msc makefile with VS10 with the ASM routines
to avoid linking problems-see win32/Makefile.msc in ZLib for more details. to avoid linking problems-see win32/Makefile.msc in ZLib for more details.
For LibFFI, please get version 3.0.10rc8 or later, as Visual C++ build support
was added in the 3.0.10(rc) release series. Please see the README file that
comes with the LibFFI source package for more details on how to build LibFFI
on Visual C++-please note that the mozilla-build package from Mozilla is needed
in order to build LibFFI on Windows.
One may optionally use his/her own PCRE installation by selecting the One may optionally use his/her own PCRE installation by selecting the
(BuildType)_ExtPCRE configuration, but please note the PCRE must be built (BuildType)_ExtPCRE configuration, but please note the PCRE must be built
with VS10 with unicode support using the /MD (release) or /MDd (debug) with VS10 with unicode support using the /MD (release) or /MDd (debug)
@ -44,6 +50,11 @@ You should unpack the proxy-libintl-dev zip file into
<root>\vs10\<PlatformName>, so that for instance libintl.h end up at <root>\vs10\<PlatformName>, so that for instance libintl.h end up at
<root>\vs10\<PlatformName>\include\libintl.h. <root>\vs10\<PlatformName>\include\libintl.h.
For LibFFI, one should also put the generated ffi.h and ffitarget.h
into <root>\vs10\<PlatformName>\include\ and the compiled static libffi.lib
(or copy libffi-convenience.lib into libffi.lib) into
<root>\vs10\<PlatformName>\lib\.
The "install" project will copy build results and headers into their The "install" project will copy build results and headers into their
appropriate location under <root>\vs10\<PlatformName>. For instance, appropriate location under <root>\vs10\<PlatformName>. For instance,
built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into

11
build/win32/vs9/README.txt
View File

@ -18,6 +18,12 @@ One may wish to build his/her own ZLib-It is recommended that ZLib is
built using the win32/Makefile.msc makefile with VS9 with the ASM routines built using the win32/Makefile.msc makefile with VS9 with the ASM routines
to avoid linking problems-see win32/Makefile.msc in ZLib for more details. to avoid linking problems-see win32/Makefile.msc in ZLib for more details.
For LibFFI, please get version 3.0.10rc8 or later, as Visual C++ build support
was added in the 3.0.10(rc) release series. Please see the README file that
comes with the LibFFI source package for more details on how to build LibFFI
on Visual C++-please note that the mozilla-build package from Mozilla is needed
in order to build LibFFI on Windows.
One may optionally use his/her own PCRE installation by selecting the One may optionally use his/her own PCRE installation by selecting the
(BuildType)_ExtPCRE configuration, but please note the PCRE must be built (BuildType)_ExtPCRE configuration, but please note the PCRE must be built
with VS9 with unicode support using the /MD (release) or /MDd (debug) with VS9 with unicode support using the /MD (release) or /MDd (debug)
@ -44,6 +50,11 @@ You should unpack the proxy-libintl-dev zip file into
<root>\vs9\<PlatformName>, so that for instance libintl.h end up at <root>\vs9\<PlatformName>, so that for instance libintl.h end up at
<root>\vs9\<PlatformName>\include\libintl.h. <root>\vs9\<PlatformName>\include\libintl.h.
For LibFFI, one should also put the generated ffi.h and ffitarget.h
into <root>\vs9\<PlatformName>\include\ and the compiled static libffi.lib
(or copy libffi-convenience.lib into libffi.lib) into
<root>\vs9\<PlatformName>\lib\.
The "install" project will copy build results and headers into their The "install" project will copy build results and headers into their
appropriate location under <root>\vs9\<PlatformName>. For instance, appropriate location under <root>\vs9\<PlatformName>. For instance,
built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into