some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
the version we have in-tree, but experience has shown that if systemwide
boost was installed at some point during build then junked by dpb build
was failing. Boo.
Note that in newer releases of kicad those bundled boost headers were removed,
and now cmake downloads boost tarball during build and patch its headers on
the fly. Yay.
https://lists.launchpad.net/kicad-developers/msg10503.html
Don't redirect errors to /dev/null and don't return true(1)
unconditionally. Instead, don't check for the existence of index.theme.
This will allow us to catch errors that may be happening because of a
missing dependency in the chain.
Some hidden issues may appear, in which case please contact me.
discussed with and ok blind jasper@
Kicad is an open source software for the creation of electronic schematic
diagrams and printed circuit board artwork.
with some ideas from freebsd.
also tested by Antti Harri <iku at openbsd.fi>, thanks
