Add documentation for out-of-source builds to README and manuals

Signed-off-by: Gavin Howard <gavin@yzena.com>
line_libs
Gavin Howard 11 months ago
parent c8d0d016fb
commit 9e688779a0
Signed by: gavin
GPG Key ID: C08038BDF280D33E
  1. 18
      README.md
  2. 17
      manuals/build.md

@ -184,6 +184,24 @@ The library is built as `bin/libbcl.a` on POSIX-compatible systems or as
#### Package and Distro Maintainers
This section is for package and distro maintainers.
##### Out-of-Source Builds
Out-of-source builds are supported; just call `configure.sh` from the directory
where the actual build will happen.
For example, if the source is in `bc`, the build should happen in `build`, then
call `configure.sh` and `make` like so:
```
../bc/configure.sh
make
```
***WARNING***: The path to `configure.sh` from the build directory must not have
spaces because `make` does not support target names with spaces.
##### Recommended Compiler
When I ran benchmarks with my `bc` compiled under `clang`, it performed much

@ -83,6 +83,23 @@ where `<config>` is either one of `Debug`, `ReleaseMD`, or `ReleaseMT`.
Building `bc`, `dc`, and `bcl` (the library) is more complex than on Windows
because many build options are supported.
### Out-of-Source Builds
Out-of-source builds are done by calling `configure.sh` from the directory where
the build will happen. The `Makefile` is generated into that directory, and the
build can happen normally from there.
For example, if the source is in `bc`, the build should happen in `build`, then
call `configure.sh` and `make` like so:
```
../bc/configure.sh
make
```
***WARNING***: The path to `configure.sh` from the build directory must not have
spaces because `make` does not support target names with spaces.
### Cross Compiling
To cross-compile this `bc`, an appropriate compiler must be present and assigned

Loading…
Cancel
Save