1 |
--- |
2 |
eclass/scons-utils.eclass | 17 ++++++++++++++++- |
3 |
1 file changed, 16 insertions(+), 1 deletion(-) |
4 |
|
5 |
diff --git a/eclass/scons-utils.eclass b/eclass/scons-utils.eclass |
6 |
index 2c52b59..4b1fe49 100644 |
7 |
--- a/eclass/scons-utils.eclass |
8 |
+++ b/eclass/scons-utils.eclass |
9 |
@@ -9,8 +9,23 @@ |
10 |
# @DESCRIPTION: |
11 |
# This eclass provides a set of function to help developers sanely call |
12 |
# dev-util/scons and pass parameters to it. |
13 |
-# @EXAMPLE: |
14 |
# |
15 |
+# Please note that SCons is more like a 'build system creation kit', |
16 |
+# and requires a lot of upstream customization to be useful. |
17 |
+# You will often need to request fixes upstream and/or patch the build |
18 |
+# system. In particular: |
19 |
+# |
20 |
+# 1. There are no 'standard' variables. To respect CC, CXX, CFLAGS, |
21 |
+# CXXFLAGS, CPPFLAGS, LDFLAGS, upstream needs to define appropriate |
22 |
+# variables explicitly. In some cases, upstreams respect envvars, |
23 |
+# in others you need to pass them as options. |
24 |
+# |
25 |
+# 2. SCons scrubs out environment by default and replaces it with some |
26 |
+# pre-defined values. To respect environment variables such as PATH, |
27 |
+# upstreams need to explicitly get them from os.environ and copy them |
28 |
+# to the build environment. |
29 |
+# |
30 |
+# @EXAMPLE: |
31 |
# @CODE |
32 |
# inherit scons-utils toolchain-funcs |
33 |
# |
34 |
-- |
35 |
2.6.4 |