diff options
Diffstat (limited to 'BOOTSTRAP-WINDOWS-MINGW.cli')
| -rw-r--r-- | BOOTSTRAP-WINDOWS-MINGW.cli | 224 |
1 files changed, 224 insertions, 0 deletions
diff --git a/BOOTSTRAP-WINDOWS-MINGW.cli b/BOOTSTRAP-WINDOWS-MINGW.cli new file mode 100644 index 0000000..163d3a7 --- /dev/null +++ b/BOOTSTRAP-WINDOWS-MINGW.cli @@ -0,0 +1,224 @@ +// file : BOOTSTRAP-WINDOWS-MINGW.cli +// copyright : Copyright (c) 2014-2019 Code Synthesis Ltd +// license : MIT; see accompanying LICENSE file + +" +Continuing from \l{#bootstrap-windows Bootstrapping on Windows}, if you are +using your own MinGW distribution, then the resulting \c{build2} binaries will +most likely require a number of DLLs in order to run. It is therefore +recommended that you copy the following files from your MinGW \c{bin\\} +subdirectory to \c{C:\\build2\\bin\\} (\c{*} in the last name will normally be +\c{dw2-1}, \c{seh-1}, or \c{sjlj-1}): + +\ +libwinpthread-1.dll +libstdc++-6.dll +libgcc_s_*.dll +\ + +To build with MinGW you can either perform the following steps manually or, if +after reviewing the steps, you are happy with using the defaults, run the +\c{build-mingw.bat} batch file. It performs (and echoes) the same set of steps +as outlined below but only allows you to customize the compiler, installation +directory, and a few other things (run \c{build-mingw.bat /?} for usage). + +For example, if your MinGW distribution is in \c{C:\\mingw\\}, then you could +run it (from the command prompt that we have started earlier) like this: + +\ +> .\build-mingw.bat C:\mingw\bin\g++ +\ + +If you are using the \c{build2-mingw} package then you should be able to +use just \c{g++} for the compiler: + +\ +> .\build-mingw.bat g++ +\ + +If you would like to speed the process up by compiling in parallel, then you +can instruct \c{build-mingw.bat} to bootstrap using GNU make (comes in +the \c{build2-mingw} package), for example: + +\ +> .\build-mingw.bat --make mingw32-make --make -j8 g++ +\ + +\N|Note that at about half way through (\c{bpkg fetch} at step 4 below) the +script will stop and prompt you to verify the authenticity of the repository +certificate. To run the script unattended you can specify the certificate +fingerprint with the \c{--trust} option (see \c{build-mingw.bat /?} for +details).| + +The end result of the bootstrap process (performed either with the script or +manually) is the installed toolchain as well as the \c{bpkg} configuration in +\c{build2-toolchain-X.Y\\} that can be used to \l{#upgrade upgrade} to newer +versions. It can also be used to uninstall the toolchain: + +\ +> cd build2-toolchain-X.Y +> bpkg uninstall build2 bpkg bdep +\ + +\N|Note that in both cases (manual or scripted bootstrap), if something goes +wrong and you need to restart the process, you \b{must} start with a clean +toolchain source by unpacking it afresh from the archive.| + +The rest of this section outlines the manual bootstrap process. + +\dl| + +\li|\b{1. Bootstrap, Phase 1}\n + +First, we build a minimal build system with the provided +\c{bootstrap-mingw.bat} batch file. Normally, the only argument you will pass +to this script is the C++ compiler to use but there is also a way to specify +compile options; run \c{bootstrap-mingw.bat /?} and see the +\c{build2\\INSTALL} file for details. + +\ +> cd build2 +> .\bootstrap-mingw.bat g++ -static + +> build2\b-boot --version +\ + +Alternatively, we can use the \c{bootstrap.gmake} GNU makefile to bootstrap +in parallel: + +\ +> cd build2 +> mingw32-make -f bootstrap.gmake -j 8 CXX=g++ LDFLAGS=-static + +> build2\b-boot --version +\ + +| + +\li|\n\b{2. Bootstrap, Phase 2}\n + +Then, we rebuild the build system with the result of Phase 1 linking +libraries statically. + +\ +> build2\b-boot config.cxx=g++ config.bin.lib=static build2\exe{b} +> move /y build2\b.exe build2\b-boot.exe + +> build2\b-boot --version +\ + +| + +\li|\n\b{3. Stage}\n + +At this step the build system and package manager are built with shared +libraries and then staged: + +\ +> cd .. # Back to build2-toolchain-X.Y.Z\ + +> build2\build2\b-boot configure ^ + config.cxx=g++ ^ + config.bin.suffix=-stage ^ + config.install.root=C:\build2 ^ + config.install.data_root=root\stage + +> build2\build2\b-boot install: build2/ bpkg/ +\ + +The strange-looking \c{config.install.data_root=root\\stage} means install +data files (as opposed to executable files) into the \c{stage\\} subdirectory +of wherever \c{config.install.root} points to (so in our case it will be +\c{C:\\build2\\stage\\}). This subdirectory is temporary and will be removed +in a few steps. + +Verify that the toolchain binaries can be found and work (this relies on the +\c{PATH} environment variable we have set earlier): + +\ +> where b-stage +C:\build2\bin\b-stage.exe + +> where bpkg-stage +C:\build2\bin\bpkg-stage.exe + +> b-stage --version +> bpkg-stage --version +\ + +At the next step we will use \c{bpkg} to build and install the entire +toolchain. If for some reason you prefer not to build from packages (for +example, because the machine is offline), then you can convert this step into +the \"final\" installation and skip the rest. For this you will need to change +the \c{configure} and \c{install} command lines above along these lines: + +\ +> build2\build2\b-boot configure ^ + config.cxx=g++ ^ + config.cc.coptions=-O3 ^ + config.install.root=C:\build2 + +> build2\build2\b-boot install: build2/ bpkg/ bdep/ +\ + +| + +\li|\n\b{4. Install}\n + +Next, we use the staged tools to build and install the entire toolchain from +the package repository with the \c{bpkg} package manager. First, we create +the \c{bpkg} configuration. The configuration values are pretty similar to the +previous step and you may want/need to make similar adjustments. + +\ +> cd .. # Back to build2-build\ +> md build2-toolchain-X.Y +> cd build2-toolchain-X.Y + +> bpkg-stage create ^ + cc ^ + config.cxx=g++ ^ + config.cc.coptions=-O3 ^ + config.install.root=C:\build2 +\ + +Next, we add the package repository, build, and install: + +\ +> bpkg-stage add https://pkg.cppget.org/1/alpha +> bpkg-stage fetch +> bpkg-stage build --for install build2 bpkg bdep +> bpkg-stage install build2 bpkg bdep +\ + +Finally, we verify the result (note that the \c{where} command is not +available on Windows XP without the Resource Kit installed): + +\ +> where b +C:\build2\bin\b.exe + +> where bpkg +C:\build2\bin\bpkg.exe + +> where bdep +C:\build2\bin\bdep.exe + +> b --version +> bpkg --version +> bdep --version +\ + +| + +\li|\n\b{5. Clean}\n + +The last thing we need to do is uninstall the staged tools: + +\ +> cd ..\build2-toolchain-X.Y.Z # Back to bootstrap. +> b uninstall: build2/ bpkg/ +\ + +|| +" |