Changes between Version 3 and Version 4 of CompilingMapGuideVCExpress
- Timestamp:
- 03/05/14 03:16:38 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CompilingMapGuideVCExpress
v3 v4 1 = Building MapGuide trunk with Visual C++Express Edition =1 = Building MapGuide trunk with Visual Studio Express Edition = 2 2 3 3 == Environment Setup == 4 4 5 * [http://www.microsoft.com/express/Downloads/Download-2008.aspx Microsoft Visual C++ 2008 Express Edition] 6 * [http://www.microsoft.com/downloads/details.aspx?FamilyID=e6e1c3df-a74f-4207-8586-711ebe331cdc&displaylang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5] 5 * [http://www.microsoft.com/en-us/download/details.aspx?id=34673 Microsoft Visual Studio 2012 Express Edition for Windows Desktop] 7 6 8 The Windows SDK provides us with the x64 native/cross compilers if you want to build MapGuide in 64-bit. This is not required if you are only building in 32-bit. 7 With the [http://trac.osgeo.org/mapguide/wiki/MapGuideRfc135 move to VS2012 as the defacto C++ compiler for windows], building MapGuide on Windows with free tools has never been easier. 9 8 10 == Setting up x64 compilers == 9 Visual Studio 2012 Express for Windows Desktop now includes *both* x86 and x64 C++ compilers. Installation of additional Windows SDKs and other tools to get the x64 compiler is no longer required. However it is worth noting that the x64 compiler that comes with Visual Studio 2012 Express is a cross-compiler (ie. x86_amd64), and not a native one. This is not really important for building MapGuide, but something to note for when building FDO. 11 10 12 If you don't intend to build 64-bit MapGuide you can skip this section. 11 Before building MapGuide manually via Visual Studio or via msbuild from the command-line, you must set up some environment variables. 12 13 To set up the environment for 32-bit compilation, launch the Developer Command Prompt for VS2012 and run: 14 {{{ 15 setenvironment.bat 16 }}} 17 18 To set up the environment for 64-bit compilation, launch the Developer Command Prompt for VS2012 and run: 19 {{{ 20 setenvironment64.bat 21 }}} 22 23 Launching Visual Studio (wdexpress.exe) from that same command-line afterwards will carry the initialized environment variables into Visual Studio. 24 25 All future references to Visual Studio in this page, assume it has been launched with these environment variables set. 13 26 14 27 == Build Oem == … … 16 29 === Manual === 17 30 18 Open Oem.sln in Visual C++ Express and build the solution using your configuration of choice. You will get an error about a particular project not loading (SQLiteGUI). This is because VS express doesn't support solutions with mixed project types. Fortunately, this project is not required and the error can be safely ignored.31 Open Oem.sln in Visual Studio 2012 Express and build the solution using your configuration of choice. 19 32 20 33 Then open the CS-Map OpenSource.sln and build that solution using the same configuration. … … 22 35 === Automated === 23 36 24 From the Visual Studio 2008 command prompttype the following from the Oem folder:37 From the Developer Command Prompt for VS2012 type the following from the Oem folder: 25 38 26 39 {{{ … … 44 57 === Manual === 45 58 46 Open Server.sln in Visual C++Express and build the solution using the same configuration used to build your Oem components.59 Open Server.sln in Visual Studio 2012 Express and build the solution using the same configuration used to build your Oem components. 47 60 48 61 === Automated === 49 62 50 From the Visual Studio 2008 command prompttype the following from the MgDev\Server folder:63 From the Developer Command Prompt for VS2012 type the following from the MgDev\Server folder: 51 64 52 65 {{{ … … 58 71 === Manual === 59 72 60 Open WebTier.sln in Visual C++Express and build the solution using the same configuration used to build the Server solution.73 Open WebTier.sln in Visual Studio 2012 Express and build the solution using the same configuration used to build the Server solution. 61 74 62 75 === Automated === 63 76 64 From the Visual Studio 2008 command prompttype the following from the MgDev\Web\src folder:77 From the Developer Command Prompt for VS2012 type the following from the MgDev\Web\src folder: 65 78 66 79 {{{ … … 84 97 }}} 85 98 86 will copy all the compiled binaries and required files into a pre-defined output directory (default is `MgDev\Release` . You can specify a custom output directory by using the `-o` switch)99 will copy all the compiled binaries and required files into a pre-defined output directory (default is `MgDev\Release` for 32-bit and `MgDev\Release64` for 64-bit. You can specify a custom output directory by using the `-o` switch)