Explore >> Select a destination
|
You are here 
|
tomaugspurger.net | ||
| | | | |
blog.jak-linux.org
|
|
| | | | | In the past weeks, I was looking at several build systems. As it turned out, there is not a single sane generic build system out there. Autotools: Autotools are ugly, slow, and require an immense amount of code copies in the source tree. WAF: WAF is not as ugly as autools and it's faster and does not generate Makefiles or stuff like this. But it has serious issues: It requires one to copy it to the source tarball, has no stable API, and requires Python for building. Furthermore, support for unit testing is broken: It runs the unit tests, but does not abort the build process if the tests fail and does not display why the tests fail. | |
| | | | |
mariocarrion.com
|
|
| | | | | Using Go Modules to manage dependencies | |
| | | | |
alexgaynor.net
|
|
| | | | | [AI summary] The author discusses the advantages of the Rust programming language, particularly its tooling and package management system, Cargo, which simplifies development, testing, and deployment compared to other languages. | |
| | | | |
openchainproject.org
|
|
| | | ISO/IEC 5230 defines the key requirements of a quality open source license compliance program How Does ISO/IEC 5230 Work? ISO/IEC 5230 helps organizations manage open source licensing requirements for past,... | ||
