| Emeric Vigier | 2f62582 | 2012-08-06 11:09:52 -0400 | [diff] [blame] | 1 | Installation on Windows 32 Platform
|
| 2 | ===================================
|
| 3 |
|
| 4 | Starting with Common C++ "2" 1.0rc1, both posix and Win32 libraries
|
| 5 | are built from the same source directory (src). The only difference
|
| 6 | between them is that Win32 MSVC++ projects use a specific win32
|
| 7 | configuration header located in win32/cc++/config.h.
|
| 8 |
|
| 9 | If you use Cygwin or MingW you may use the autotools
|
| 10 | infrastructure. There is also a specific win32/Makefile.gcc for
|
| 11 | Mingw. It has been tested to build dll's with Mingw as cross compiler
|
| 12 | on Debian GNU/Linux.
|
| 13 |
|
| 14 | A win32/Makefile.bcc is provided for Borland C++ compiler
|
| 15 | users. Although a bit outdated it should work.
|
| 16 |
|
| 17 |
|
| 18 | Compiling and testing with MSVC6
|
| 19 | ================================
|
| 20 |
|
| 21 | Three workspaces are provided for MSVC++:
|
| 22 |
|
| 23 | * CCXX2: includes two projects that build ccgnu2.dll and ccext2.dll
|
| 24 | (base and extension libraries respectively).
|
| 25 |
|
| 26 | * CCXX2demo: projects for demo apps.
|
| 27 |
|
| 28 | * CCXX2tests: projects for tests apps.
|
| 29 |
|
| 30 | All these projects define the two usual configurations: Debug and
|
| 31 | Release. When building under "Debug" all executables, libraries and
|
| 32 | compilation temporary objects will go to win32/Debug. When building
|
| 33 | under "Release" all executables, libraries and compilation temporary
|
| 34 | objects will go to win32/Release.
|
| 35 |
|
| 36 | As mentioned above, a specific win32/cc++/config.h configuration
|
| 37 | header is provided for MSVC++. This header defines "configuration
|
| 38 | constants".
|
| 39 |
|
| 40 | In particular, the HAVE_LIBXML "configuration constant" is defined
|
| 41 | so that XML support is compiled and added to ccext2.dll. In order for
|
| 42 | this configuration to work, you should have installed libxml2 (the XML
|
| 43 | C library for GNOME) on your system. You can get sources (with MSVC++
|
| 44 | workspace files) and/or binaries of libxml2 from
|
| 45 | http://xmlsoft.org. If you just do not want XML support, simply remove
|
| 46 | or comment the line #define COMMON_XML_PARSING in win32/cc++/config.h,
|
| 47 | but beware the xml demo applications will not compile due to linking
|
| 48 | errors.
|
| 49 |
|
| 50 | Install with MSVC6
|
| 51 | ==================
|
| 52 |
|
| 53 | From win32 directory execute install.bat script. This copy headers and
|
| 54 | import libraries in MSVC directory and dll in SDK Path
|
| 55 |
|
| 56 | You must define some environments variables before launch install.bat
|
| 57 | (defined automatically by batch vcvars32.bat in VC bin directory):
|
| 58 | - MSVCDir the install directory of MSVC ( usually
|
| 59 | C:\Program Files\Microsoft Visual Studio\VC98)
|
| 60 | Also you can define:
|
| 61 | - DLL_PATH to point to a place to install things. If not defined it'll be
|
| 62 | defined to "%MSVCDir%\Bin"
|
| 63 |
|
| 64 |
|
| 65 | Install with Visual Studio 2008 from SVN
|
| 66 | ==================
|
| 67 |
|
| 68 | If you checked out the project from SVN and you mean building it by using
|
| 69 | Visual Studio 2008 you nead to create solution and projects.
|
| 70 | In order to do that you can do the following steps:
|
| 71 |
|
| 72 | - using cygwin
|
| 73 | run from the project root the following commands:
|
| 74 | ./autogen.sh
|
| 75 | ./configure
|
| 76 | then you can find the needed files into w32\vs2008 directory.
|
| 77 |
|
| 78 | - without using cygwin
|
| 79 | 1) open configure.ac file and take note of VERSION and LT_RELEASE values
|
| 80 | 2) copy w32\vs2008\common.sl.in to w32\vs2008\common.sl
|
| 81 | 3) copy w32\vs2008\ccext2.vcproj.in to w32\vs2008\ccext2.vcproj
|
| 82 | 4) copy w32\vs2008\ccgnu2.vcproj.in to w32\vs2008\ccgnu2.vcproj
|
| 83 | 5) edit w32\vs2008\ccext2.vcproj and w32\vs2008\ccgnu2.vcproj to change
|
| 84 | every entries of VCVERSION to the value of VERSION read before into
|
| 85 | configure.ac, and every entries of DLLVERSION to the value of LT_RELEASE.
|
| 86 |
|
| 87 | Install with Visual Studio 2005 from SVN
|
| 88 | ==================
|
| 89 |
|
| 90 | If you checked out the project from SVN and you mean building it by using
|
| 91 | Visual Studio 2005 you nead to create solution and projects.
|
| 92 | In order to do that you can do the following steps:
|
| 93 |
|
| 94 | - using cygwin
|
| 95 | run from the project root the following commands:
|
| 96 | ./autogen.sh
|
| 97 | ./configure
|
| 98 | then you can find the needed files into w32 directory.
|
| 99 |
|
| 100 | - without using cygwin
|
| 101 | 1) open configure.ac file and take note of VERSION and LT_RELEASE values
|
| 102 | 2) copy w32\ccext2.vcproj.in to w32\ccext2.vcproj
|
| 103 | 4) copy w32\ccgnu2.vcproj.in to w32\ccgnu2.vcproj
|
| 104 | 5) edit w32\ccext2.vcproj and w32\ccgnu2.vcproj to change
|
| 105 | every entries of VCVERSION to the value of VERSION read before into
|
| 106 | configure.ac, and every entries of DLLVERSION to the value of LT_RELEASE.
|
| 107 |
|
| 108 | Install with Visual Studio 6 from SVN
|
| 109 | ==================
|
| 110 |
|
| 111 | If you checked out the project from SVN and you mean building it by using
|
| 112 | Visual Studio 6 you nead to create solution and projects.
|
| 113 | In order to do that you can do the following steps:
|
| 114 |
|
| 115 | - using cygwin
|
| 116 | run from the project root the following commands:
|
| 117 | ./autogen.sh
|
| 118 | ./configure
|
| 119 | then you can find the needed files into w32 directory.
|
| 120 |
|
| 121 | - without using cygwin
|
| 122 | 1) open configure.ac file and take note of VERSION and LT_RELEASE values
|
| 123 | 2) copy w32\ccext2.dsp.in to w32\ccext2.dsp
|
| 124 | 3) copy w32\ccgnu2.dsp.in to w32\ccgnu2.dsp
|
| 125 | 4) edit w32\ccext2.dsp and w32\ccgnu2.dsp to change
|
| 126 | every entries of VCVERSION to the value of VERSION read before into
|
| 127 | configure.ac, and every entries of DLLVERSION to the value of LT_RELEASE.
|
| 128 |
|