Skip to content

Commit d40ec61

Browse files
authored
[docs] Restore section about build strategy (#1284)
1 parent 673c93e commit d40ec61

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/src/build_tips.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,12 @@ If your build fails with some errors, look at the [Build Troubleshooting](@ref)
66

77
*If you have additional tips, please submit a PR with suggestions.*
88

9+
## Build strategy
10+
11+
What BinaryBuilder does is to create a tarball containing all files that are found inside the `${prefix}` directory at the end of the build and which don't come from the dependencies listed in the build recipe.
12+
Thus, what you want to do in a build script is to install the relevant files under the appropriate directories in `${prefix}` (see the [Automatic environment variables](@ref) section): the libraries in `${libdir}`, the binary executables in `${bindir}`, etc...
13+
Most packages come with a build system to automate this process (GNU Autoconf, CMake, Meson, a plain Makefile, etc...), but sometimes you may need to manually move the files as appropriate.
14+
915
## Initiating different shell commands based on target
1016

1117
Sometimes, you need to adapt build scripts based on the target platform. This can be done within the shell script. Here is an example from [`OpenBLAS`](https://github.com/JuliaPackaging/Yggdrasil/blob/685cdcec9f0f0a16f7b90a1671af88326dcf5ab1/O/OpenBLAS/build_tarballs.jl):

0 commit comments

Comments
 (0)