![]() ![]() Holy Build Box should be activated as early as possible. Without activation, a large part of Holy Build Box does not work. They are installed in /hbb*, so the compiler toolchain won't find them by default.Īctivating the Holy Build Box environment is important. ![]() The reason why this is needed because some of the software inside the Holy Build Box environment is not installed via YUM, but compiled from source instead. It then executes the command specified in its parameters - that is, gcc. The activate-exec command sets various environment variables - such as PATH, CFLAGS and C_INCLUDE_PATH - so that the compiler toolchain can find various software that is included in Holy Build Box. ![]() Note that gcc is preceded by a "magical" invocation to /hbb_exe/activate-exec. Start a Bash shell inside the Holy Build Box environment so that you can look around and inspect things: Support for other architectures may be introduced in the future. Support for x86 was dropped in Holy Build Box 3. Holy Build Box consists of one Docker image: foobarwidget/holy-build-box-amd64, for building amd64 binaries. Holy Build Box will probably make little sense to you otherwise. You should be comfortable with using the compiler, make, autotools, environment variables etc. We also assume that you are adept at using the C/C++ compilation toolchain. If you are not familiar with Docker, then these tutorials will probably make little sense to you. Please read the Docker documentation first. So to use Holy Build Box, you must be at least adept at using Docker. This tutorial serves to give you a feel of what Holy Build Box is and how it works. Welcome to the Holy Build Box introductory tutorial. Tutorial index | Skip to Tutorial 2: Compilation via a script > ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |