Explore >> Select a destination
|
You are here 
|
blog.packagist.com | ||
| | | | |
blog.bitexpert.de
|
|
| | | | | Automate and simplify the process of applying patches to your project files during the Composer install procedure with cweagans/composer-patches and symplify/vendor-patches. | |
| | | | |
leoloso.com
|
|
| | | | | Or how to avoid getting impatient while waiting for Composer to finish an update... | |
| | | | |
packagist.org
|
|
| | | | | The PHP Package Repository | |
| | | | |
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. | ||
