2 ms·
That Makefile works with BSD and GNU make, no extensions used. Bazel isn't really nicer than the autotools when you need something complicated, if it even supp
by mzs 7y ago
That Makefile works with BSD and GNU make, no extensions used.
Bazel isn't really nicer than the autotools when you need something complicated, if it even supports your platform. Here's a fun bazel bug report: https://github.com/bazelbuild/bazel/issues/4350#issuecomment-353742540 https://github.com/bazelbuild/bazel/issues/4350#issuecomment...
I've always managed to avoid autotools unless it was used before with things like LDFLAGS='-lsocket -lns' make ...
- pjmlp 7y agoFor me being POSIX compliant goes a little beyond BSD and GNU make.
- mzs 7y agoWhat does posix compliant* even mean for make? The posix standard doesn't even require support for c++! That's a VERY portable Makefile. It would work on any make from the late seventies (assuming you also had a c++ compiler and system Makefiles that knew how to use it). It only uses a small subset of the rules in the standard. * https://pubs.opengroup.org/onlinepubs/009695399/utilities/make.html https://pubs.opengroup.org/onlinepubs/009695399/utilities/ma...
- pjmlp 7y agoThat is what I mean by POSIX compliant, so I stand corrected. Thanks.