diff options
| author | schmonz <schmonz> | 2002-12-25 05:16:12 +0000 |
|---|---|---|
| committer | schmonz <schmonz> | 2002-12-25 05:16:12 +0000 |
| commit | d3c296fa9468431d734b538c302484b81acf9d71 (patch) | |
| tree | 8b6ae06e912958567516afe1be4cc1873d2808a3 /mk/buildlink2 | |
| parent | 27592b8635ff619f1f042e9c8a2dd0983425e519 (diff) | |
| download | pkgsrc-d3c296fa9468431d734b538c302484b81acf9d71.tar.gz | |
Add a to-do item:
(*) Since buildlink2 is a layer of abstraction atop the toolchain,
it's a logical place to deal with the vagaries of unusual
toolchains. For example, on Darwin we could reliably pass
the "-no-cpp-precomp" switch to every compiler invocation
by emitting it from the compiler wrapper. Likewise, the
use of _USE_RPATH in bsd.pkg.mk might be better handled in
the linker wrapper.
Diffstat (limited to 'mk/buildlink2')
| -rw-r--r-- | mk/buildlink2/buildlink2.txt | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/mk/buildlink2/buildlink2.txt b/mk/buildlink2/buildlink2.txt index 9beefb39bc2..21025a62272 100644 --- a/mk/buildlink2/buildlink2.txt +++ b/mk/buildlink2/buildlink2.txt @@ -1,4 +1,4 @@ -$NetBSD: buildlink2.txt,v 1.6 2002/08/29 17:08:49 jlam Exp $ +$NetBSD: buildlink2.txt,v 1.7 2002/12/25 05:16:12 schmonz Exp $ The buildlink2 framework is a departure from the original buildlink framework, which tries to do its work up-front before the configure @@ -15,8 +15,16 @@ munge them into references into ${BUILDLINK_DIR}. To-do list: - (*) regression test targets to make sure _BLNK_TRANSFORM_SED is doing - what it's supposed to do + (*) Write regression test targets to make sure _BLNK_TRANSFORM_SED + is doing what it's supposed to do. + + (*) Since buildlink2 is a layer of abstraction atop the toolchain, + it's a logical place to deal with the vagaries of unusual + toolchains. For example, on Darwin we could reliably pass + the "-no-cpp-precomp" switch to every compiler invocation + by emitting it from the compiler wrapper. Likewise, the + use of _USE_RPATH in bsd.pkg.mk might be better handled in + the linker wrapper. Here are some FAQs and answers regarding buildlink2: |