Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 To set up GMAT dependencies, double-click run the configure.sh (Mac/Linux) or configure.bat (Windows) script.

  • Run configure.sh by name from the Terminal on Mac/Linux, and configure.bat by double-clicking on it in Windows.
  • On Windows you will be prompted to select 32-vs-64 bit dependencies and a VisualStudio version. Choose according to your VisualStudio installation. On Mac/Linux these choices are currently auto-selected based on the system architecture.
  • You can also run these scripts by name from the Terminal (Mac/Linux) or Command Prompt (Windows).

 The script will download, build, and configure the GMAT dependencies. The resulting <GMAT>/depends folder structure should look like Figure 2.

...

 Launch the CMake GUI:

Tip: Make sure to select  Select the "Grouped" option in the CMake GUI (Figure 3) to sort CMake variables and make them easier to find.

...

  1. Enter the full path to the <GMAT> cloned repository on your computer
  2. Enter the full path to the folder where all CMake files and build products should be placed
    1. CMake produces out-of-source builds. It is recommended to use <GMAT>/build/<OS>/cmake-buildcmakebuild for this value.
  3. Click "Configure"
    1. CMake may ask for permission to create the folder you chose specified in Step 2 ("Where to build the binaries")
    2. CMake will ask you to choose a generator (see Figure 4). See the CMake Generator webpage for an explanation of available generators.
      Recommended generators are:
      1. Mac: Unix Makefiles (although XCode has also been observed to work)
      2. Linux: Unix Makefiles
      3. Windows: Visual Studio (note e.g. "Visual Studio 12 2013" is 32-bit, whereas "Visual Studio 12 2013 x64" is 64-bit)

        Figure 4. Choosing a generator in CMake

        CMake choose generator

    3. CMake will start the configuration process, after which the Variable List and Configure Results sections (Figure 3 sections 4a and 4b) will be populated:

      Figure 5. Output of CMake Configure

      CMake initial configure
  4. Use the Configure results output box (Figure 3 section 4a) to change variables in the CMake variable list (Figure 3 section 4b) as follows:

    1. Always start at the top of the configure results output box and correct errors one-by-one
    2. For each error: change the appropriate CMake variable, re-configure, confirm the error was fixed (in the results output box), then repeat for next error
    3. In addition to errors, there are several CMake variables that allow you to control how the build system configures GMAT:

      CMake Variable (Group)DescriptionAssociated CMake Error
      CSPICE_DIR (Ungrouped)Path to CSPICE root directory
      (containing include/, lib/, etc.) 
      CSPICE NOT FOUND (make sure to run depends script from Step 1) 
      F2C_DIR (Ungrouped)Path to F2C root directory
      (containing f2c.h) 
      Note: this should generally be CSPICE_DIR/include
      F2C NOT FOUND (make sure to run depends
      script from Step 1) 
      CMAKE_BUILD_TYPE (CMAKE)On makefile systems, this specifies the desired build type
      On VisualStudio/XCode systems, this specifies all possible build types
      Valid values: Release, Debug, RelWithDebInfo, MinSizeRel
      Note: On makefile systems, you should create a separate out-of-source build folder for each desired build type (Figure 3 box 2).
      (e.g. cmakecmakebuild-build-release or cmakecmakebuild-build-debug)
      N/A
      CMAKE_INSTALL_PREFIX (CMAKE)Location to install GMAT when doing make install
      or building the VisualStudio->INSTALL project 
      N/AGMAT_GUI (GMAT)Whether to build the GMAT GUINote: This is autofilled to <GMAT>/GMAT-<release>-<OS>-<BitType> for convenience.N/A
      GMAT_PROPRIETARYPLUGINS_PATH
      (GMAT)

      Full path to the top-level GMAT Proprietary Plugins code/ folder.

      (

      containing code/)

      folder that contains CMakeLists.txt) This will be automatically found if you name it gmatinternal-git and place it next to the main <GMAT> repository folder.

      N/A
      Matlab_ROOT_DIR (Matlab)Path to MATLAB root directory
      (on Mac, this is the path to MATLAB_R20xxx.app)
      Matlab NOT FOUND (make sure MATLAB
      is installed) 
      PLUGIN_XXX (PLUGIN)Whether to build a particular GMAT Plugin
      Note: the proprietary plugins only show up here if
      GMAT_PROPRIETARY_PLUGINS has been correctly set 
      N/A
      wxWidgets_ROOT_DIR (wxWidgets)Mac/Linux: Path to wxWidgets wx-config utility
      (usually this is the wxWidgets bin/ folder)
      Windows: Path to wxWidgets
      (containing include/ and lib/)
      wxWidgets NOT FOUND (make sure to run depends
      script from Step 1) 
  5. When all CMake errors are handled and you have specified all desired GMAT options, click "Generate".
    CMake will create the build system in the chosen out-of-source build folder (Figure 3 box 2).

...

In these instructions, <CMake_binarybuild_path> is the path to the build system folder that you chose in Step 2 (Figure 3 box 2).

  1. Open a command prompt and type the following commands (assuming $ is your command prompt):
    $ cd <CMake_binarybuild_path>
    $ make
    • Note: if you know your computer has N cores, you can also do "make -jN" to significantly speed up the compile time
  2. (Optional) Do Type "make install" if you want a fully standalone and relocatable distributable version of GMAT.

Step 4: Run GMAT

...