File: README.msvc

package info (click to toggle)
flightgear 1:2016.4.4+dfsg-3+deb9u1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 48,512 kB
  • ctags: 71,727
  • sloc: cpp: 195,395; ansic: 177,152; sh: 13,661; perl: 4,475; python: 2,381; asm: 642; makefile: 398; java: 314; xml: 85
file content (114 lines) | stat: -rw-r--r-- 4,369 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
WINDOWS / VISUAL STUDIO BUILD INSTRUCTIONS
==========================================

[For Linux/Unix/OSX/... instructions see README.cmake]


Directory Structure
===================

On Windows, assumptions on the directory structure are made to automate
the discovery of dependencies.
This recommended directory structure is described below:

${MSVC_3RDPARTY_ROOT} /
      3rdParty /                 ( includes plib, fltk, zlib, libpng,
                                   libjpeg, libtiff, freetype, libsvn,
                                   gdal, ... )
         bin /
         include /
         lib /
      3rdParty.x64 /             ( 64 bit version )
         ...
      boost_1_44_0 /
         boost /
      install /
         msvc100 /               ( for VS2010 32 bits, or msvc90,
                                   msvc90-64 or msvc100-64 for VS2008 32,
                                   VS2008 64 and VS2010 64 )
            OpenSceneGraph /     ( OSG CMake install )
               bin /
               include /
               lib /
            SimGear /
               include /
               lib /

If you do not use the recommended structure you will need to enter paths
by hand. Source and build directories can be located anywhere.


Running CMake GUI
=================

The suggested inputs to cmake are :
  MSVC_3RDPARTY_ROOT : location of the above directory structure
  CMAKE_INSTALL_PREFIX : ${MSVC_3RDPARTY_ROOT}/install/msvc100/FlightGear
     (or any variation for the compiler version described above)

1. Set up a work directory as described above.

2. Open the CMake gui.

3. Set "Where is the source code" to wherever you put the FlightGear
   sources (from the released tarball or the git repository).

4. Set "Where to build the binaries" to an empty directory.

5. Press the "Configure" button. The first time that the project is
   configured, CMake will bring up a window asking which compiler you wish
   to use. Normally just accept Cmakes suggestion, and press Finish. CMake
   will now do a check on your system and will produce a preliminary build
   configuration.

6. CMake adds new configuration variables in red. Some have a value ending
   with -NOTFOUND. These variables should receive your attention. Some
   errors will prevent FlightGear to build and others will simply
   invalidate some options without provoking build errors. First check the
   MSVC_3RDPARTY_ROOT variable. If it is not set, chances are that there
   will be a lot of -NOTFOUND errors. Instead of trying to fix every error
   individually, set that variable and press the "Configure" button again.

7. Also check the lines with a checkbox. These are build options and may
   impact the feature set of the built program.

8. Change the CMAKE_INSTALL_PREFIX to
   ${MSVC_3RDPARTY_ROOT}/install/msvc100/FlightGear because
   C:\Program Files is likely unwritable to ordinary Windows users and
   will integrate better with the above directory structure (this is
   mandatory for SimGear if you don't want to solve errors by hand).

10. Repeat the process until the "Generate" button is enabled.

11. Press the "Generate" button.

12. Start Visual Studio 2010 and load the FlightGear solution
    (FlightGear.sln) located in "Where to build the binaries" (point 4.)

13. Choose the "Release" build in the VS2010 "Generation" toolbar

14. Generate the solution.

15. If there are build errors, return to CMake, clear remaining errors,
    "Configure" and "Generate"

16. When Visual Studio is able to build everything without errors, build
    the INSTALL project to put the product files in ${CMAKE_INSTALL_PREFIX}

17. Enjoy!


Rebuilding Updated Sources
==========================

When updating the sources from Git, it is usually unnecessary to restart
CMake as the solution is able to reconfigure itself when CMake files are
changed. Simply rebuild the solution from Visual Studio and accept the
reload of updated projects. It also possible to edit CMakeList.txt files
directly in Visual Studio as they also appear in the solution, and projects
will be reconfigured on the next generation. To change build options or
directory path, it is mandatory to use the CMake Gui. In case of problems,
locate the CMakeCache.txt in "Where to build the binaries" directory and
delete it to reconfigure from scratch or use the menu item
File->Delete Cache.