| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I4af00e2925df393523ad3d00bd3b95459ff77f9c
|
|
|
|
| |
Change-Id: Ib36d8c32c874cbdddc6ed3fe9ea6c7465ac334db
|
|
|
|
|
|
|
| |
Always link in gb_STDLIBS, except when the library explicitly opts out
with gb_LinkTarget_disable_standard_system_libs.
Change-Id: I489a99114fbfa46d0421a27cf6c7b899dc268a4a
|
|
|
|
|
|
|
|
|
|
|
| |
There are currently 3 different mechanisms being used for frameworks,
which is of course intolerable so we invent a 4th one and standardize on
it: gb_LinkTarget_use_darwin_frameworks
(This doesn't mean using add_libs or externals was wrong, it was just
inconsistent... and i don't see an obvious benefit of using externals here)
Change-Id: I5de9020402c87e7236c6a358c47f02fa56642d3d
|
|
|
|
|
|
| |
... new gb_LinkTarget_add_standard_system_libs
Change-Id: Ib2bc843098db3d8c6822b45a3d21724e67f57d69
|
| |
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit cd105c5ad2dc7176837a570e6507bd2ca0cd357f.
We can't use gb_Library_add_objcxxobjects here because
gb_ObjCxxObject_get_source has .mm suffix
|
| |
|
| |
|
|
|