| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- replace all echo(1) and printf(1) constructs with a single cat(1).
- do not eliminate -I${prefix}/lib and -L${exec_prefix}/lib;
- eliminate trailing spaces from the end of a line.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Special thanks to Jonas 'Sortie' Termansen, author of the Sortix operating
sys (https://sortix.org), for brainstorming about the best way to forward
arguments containing special symbols or characters to a sourced (aka dot)
shell script, as well as sharing single-quote tips and tricks.
|
|
|
|
|
|
|
|
This patch guards against the case where -lfoo would result in the linking
in of either an external import library libfoo.lib.a, or a static libfoo.a,
be it internal or external to the build system.
|
|
|
|
|
|
These definitions come in handy when a project generates alongside
its ``primary shared library'' one or more ``extension libraries''
that depend on it. When the rules for generating extension
libraries use the $^ directive, the above dependency must
be declared in a target-aware manner.
In most cases, one would want to express this dependency by way
of $(DSO_REF_SONAME), thereby pulling in lib/libfoo.so.$(MAJOR)
on ELF targets, lib/libfoo.$(MAJOR).lib.a on midipix targets,
and lib/libfoo.$(MAJOR).dll.a on win32 targets.
|
|
|
|
|
|
|
|
|
|
|
|
'cause you cannot eat your Apfel and eat it two.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
