In 5589c72b88e502bfca045ae38af16c854afdd401 a problem due to linking
pyuno_wrapper with g++ was fixed: the library should not have a
dependency on libstdc++. It's possible to implement this in gbuild
directly by checking whether there are any C++ input files.
(apparently on GNU/Linux g++ implicitly links in libm too...)
Change-Id: I04dce06f796e20047ce7f5eab65e6110c0244445
- remove --unix-qstart-libpng:
the internal libpng is static lib so this option is pointless
- clean up duplicative libpng checks
- replace usage of ENABLE_QUICKSTART_LIBPNG with ENABLE_HEADLESS,
which is the one case where it could still be disabled
Change-Id: Ie2e2c7e4a2396572742fdf056bf23c4271f04811
GUI only takes values UNX or WNT, so it is fairly pointless. One can check
whether OS is WNT or not instead.
Change-Id: I78ae32c03536a496a563e5deeb0fca78aebf9c34
Reviewed-on: https://gerrit.libreoffice.org/1304
Reviewed-by: Peter Foley <pefoley2@verizon.net>
Tested-by: Peter Foley <pefoley2@verizon.net>
Always link in gb_STDLIBS, except when the library explicitly opts out
with gb_LinkTarget_disable_standard_system_libs.
Change-Id: I489a99114fbfa46d0421a27cf6c7b899dc268a4a
Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
(i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
(i.e. it is registered at the Module, has it's own makefile, may be
in a different module than the target)