Note that you aren’t on the master branch after a fresh installation, but a specific commit because the Scenery Tools tree is registered as a git submodule in the build environment. Similary you can update the Scenery Tools source tree with: cd /xptools In this case just re-run the Buildenvironment Installer over an existing installation to update the environment (you will need an installer version >= 1.1.1 for this to work). This however might fail when we update bash or git in the environment because Windows locks files which are currently in use. when we added a new gcc release for example) just start the environment and execute following commands: cd / To update the build environment itself (i.e. It will put you automatically in the Scenery Tools Source directory if you choosed to download the sources during the installation, or into your home directory if you skipped that step. To start the environment, run startenv.bat from the root of the installation directory. The build environment is entirely self-contained – simply delete it when done – it does not install any registry keys, COM components, or other global “stuff”. The installer is a net-installer – that is, it will download the latest components to the build environment. The simplest way to do that is with the XPTools Environment Installer, which can be downloaded here. MinGW is the supported compiler – you will need to set up a full mingw environment with GCC 4.2.x or newer. You may want to consider this when installing the tools. WARNING: Make sure there are no spaces in the paths up to the code on Windows! The Makefile does not handle this case yet. The rest of this section covers using MinGW-if you’re using Visual Studio (recommended), jump ahead to Getting the source code. In addition to the standard installation of Microsoft Visual Studio Community, you’ll also need some kind of Git client Git GUI is a simple choice, and the command-line syntax listed here will work in the “GIT Bash” shell that comes with it. If you want to work on older versions of WED (pre-1.3) you will need to use MinGW.This is the easier, and recommended option. If you want to work on WED 1.3 or later (i.e., any version we’ve shipped for years now) you can use Visual Studio 2017 or later (the free Community edition is fine).There are two choices for toolchains on Windows. The easiest way to get CMake is via Homebrew: $ brew install cmake Windows You also need a command-line version of CMake installed. To build on macOS, you’ll need at least macOS 10.12 (Sierra) and the latest version of Xcode ( free in the Mac App Store) your OS supports. Before you can work on the tools, you may need to get/update your development environment. The X-Plane scenery tools code (XPTools) can be compiled for Mac, Windows, or Linux. This article describes how to get, compile, and modify the scenery tools code. The X-Plane Scenery Tools are available as source code, as well as binaries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |