| 1 |
Signed-off-by: Michał Górny <mgorny@g.o> |
| 2 |
--- |
| 3 |
eclass/scons-utils.eclass | 7 ++++--- |
| 4 |
1 file changed, 4 insertions(+), 3 deletions(-) |
| 5 |
|
| 6 |
diff --git a/eclass/scons-utils.eclass b/eclass/scons-utils.eclass |
| 7 |
index 212b29e089e8..b8e3332a1263 100644 |
| 8 |
--- a/eclass/scons-utils.eclass |
| 9 |
+++ b/eclass/scons-utils.eclass |
| 10 |
@@ -16,12 +16,13 @@ |
| 11 |
# and use appropriate Python suite eclass to select the implementation. |
| 12 |
# The eclass needs to be inherited before scons-utils, and scons-utils |
| 13 |
# will automatically take advantage of it. For more details, please see: |
| 14 |
-# https://wiki.gentoo.org/wiki/Project:Python/scons-utils_integration |
| 15 |
+# https://projects.gentoo.org/python/guide/buildsys.html#scons |
| 16 |
# |
| 17 |
# Please note that SCons is more like a 'build system creation kit', |
| 18 |
# and requires a lot of upstream customization to be used sanely. |
| 19 |
-# You will often need to request fixes upstream and/or patch the build |
| 20 |
-# system. In particular: |
| 21 |
+# We attempt to force sane behavior via custom patching but this is not |
| 22 |
+# guaranteed to work. You will sometimes need to request fixes upstream |
| 23 |
+# and/or patch the build system. In particular, normally: |
| 24 |
# |
| 25 |
# 1. There are no 'standard' variables. To respect CC, CXX, CFLAGS, |
| 26 |
# CXXFLAGS, CPPFLAGS, LDFLAGS, upstream needs to define appropriate |
| 27 |
-- |
| 28 |
2.38.1 |
Archives