842
edits
Legoboyvdlp (talk | contribs) |
Legoboyvdlp (talk | contribs) |
||
Line 102: | Line 102: | ||
4. Set ROOT_DIR to the FlightgearBuild folder you created (the above directory structure) | 4. Set ROOT_DIR to the FlightgearBuild folder you created (the above directory structure) | ||
==== Post-compilation ==== | ==== Post-compilation: Launching FlightGear ==== | ||
'''In the debugger:''' | |||
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG. | Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG. | ||
To launch FlightGear from Visual Studio, you can | To launch FlightGear from Visual Studio, you can follow the following steps: | ||
The first time | The first time only: | ||
# Make sure you set your build type to RelWithDebInfo in the top bar. | # Make sure you set your build type to RelWithDebInfo in the top bar. | ||
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK. | # To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK. | ||
# Press the green arrow (Local Windows Debugger) to start up FlightGear. | # Press the green arrow (Local Windows Debugger) to start up FlightGear. | ||
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start. | # The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start. | ||
NB these instructions are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development). | Therafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them! | ||
'''As a standard .exe:''' | |||
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development). | |||
Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLS as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them. | Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLS as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them. |
edits