You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the project is built with make. However, the current build setup has several unfortunate properties, including:
It uses ambient toolchains,
It hard-codes various GCC-specific compiler flags, some of which drift by version,
It doesn't readily support cross-compilation and cross-testing.
Some of these things could be fixed by rewriting (and modernizing) the Makefile, but I actually think Make is the wrong tool. On the other hand, I also believe it's important for the library to be easily pulled out and hacked up into a new build environment, without deep connections to the environment I use to develop it. On that basis, I will probably not consider using Bazel.
One option is to build everything in Docker (see commit 899e202 for a nod in that general direction). That would let us keep the Make-based build but use containerization to ensure a stable build environment. Another option is djb redo, which has a recent decent reimplementation here.
The text was updated successfully, but these errors were encountered:
The doc.md file is now generated from doc.md.in, via a rule that uses the
mkdoc.py script. The rule depend on the headers so that it will get updated
when they change.
As a sleazy hack, I made doc.md a dependency of the test target to ensure it
gets run. This will do till I set up better automation (see #27 and #28).
Serves in partial satisfaction of #30.
Right now the project is built with
make
. However, the current build setup has several unfortunate properties, including:Some of these things could be fixed by rewriting (and modernizing) the Makefile, but I actually think Make is the wrong tool. On the other hand, I also believe it's important for the library to be easily pulled out and hacked up into a new build environment, without deep connections to the environment I use to develop it. On that basis, I will probably not consider using Bazel.
One option is to build everything in Docker (see commit 899e202 for a nod in that general direction). That would let us keep the Make-based build but use containerization to ensure a stable build environment. Another option is djb redo, which has a recent decent reimplementation here.
The text was updated successfully, but these errors were encountered: