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)
It is puzzling that Executable_soffice.bin.mk contains the line
$(eval $(call gb_Executable_set_targettype_gui,$(sofficebin),YES))
yet, in the build log we see -SUBSYSTEM:CONSOLE among the linker flags.
I added -SUBSYSTEM:WINDOWS flag exlicitely, and it comes later so it
prevails. I guess MinGW will be still affected. It really should be
fixed correctly by a gbuild expert.
the previous solution couldnt work:
- Packages are toplevel targets, so they need to be in a separate file
- However, Packages should not be used here as it interferes with the
pattern rules on $(OUTDIR)/bin
- replacing those instead with explicit (non-pattern) rules for this
exceptional case
- depending from the regular target in $(OUTDIR) on the special one
- depending from the special target on the $(WORKDIR) one
