| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
Turns out this was semantically the right way to do it.
|
|
We don't share them often and those that are shared (e.g., cxx{} in
obja/objs{}) are lightweight (SOO).
|
|
|
|
|
|
With small string optimizations this is most likely a hindrance rather
that an optimization.
|
|
|
|
A library dependency on another libraries is either "interface" or
"implementation". If it is interface, then everyone who links to this library
should also link to the interface dependency, explicitly. A good example of
an interface dependency is a library API that is called in inline functions.
Interface dependencies of a library should be explicitly listed in the
*.export.libs (where we can also list target names). So the typical usage
will be along these lines:
import int_libs = libfoo%lib{foo}
import int_libs += ...
import imp_libs = libbar%lib{bar}
import imp_libs += ...
lib{baz}: ... $int_libs $imp_libs
lib{baz}: cxx.export.libs = $int_libs
|
|
We now have two new modules: cc (c-common) and c.
|
|
|
|
We no longer enter paths from the src tree into scope map. Instead, targets
from the src tree now include their out tree directory (in essence their
"configuration"). This is then used to find a target's scope. See the
comment in class target for details.
The result of this change is that we can now again build multiple
configurations (out trees) for same project at once.
|
|
|
|
Probably can also do for the rest of the target_key members.
|
|
|
|
|
|
|
