Introduce the notion of a 'sample comment'.
- presence of the sample's reported.by file is now mandatory.
- when saving a sample, reporter name & URL are queried, to avoid operator forget about creating the reported.by file.
- when saving a sample, one can store a few-liner comment.
- when recalling a sample, the reporter name, URL and comment (if present) are printed.
- update the powerpc-e500v2-linux-gnuspe sample to include Nate's comment (from his original mail).
- update all samples that were missing the reported.by file.
/trunk/scripts/saveSample.sh | 46 35 11 0 ++++++++++++++++++------
/trunk/scripts/showSamples.sh | 12 6 6 0 +++---
/trunk/samples/powerpc-e500v2-linux-gnuspe/reported.by | 15 15 0 0 ++++++++
/trunk/samples/samples.mk | 22 17 5 0 +++++++++--
4 files changed, 73 insertions(+), 22 deletions(-)
1 menu "Toolchain options"
3 comment "General toolchain options"
7 prompt "Use sysroot'ed toolchain"
10 Use the 'shinny new' sysroot feature of gcc: libraries split between
11 prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
13 You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
17 prompt "Build shared libraries"
18 depends on ! BARE_METAL
21 Say 'y' here, unless you don't want shared libraries.
23 You might not want shared libraries if you're building for a target that
24 don't support it (maybe some nommu targets, for example, or bare metal).
28 prompt "Vendor string"
31 Vendor part of the target tuple.
33 A tuple is of the form arch-vendor-kernel-system.
34 You can set the second part, vendor, to whatever you see fit.
35 Use a single word, or use underscores "_" to separate words.
37 Keep the default (unkown) if you don't know better.
39 config TARGET_ALIAS_SED_EXPR
41 prompt "Target sed transform"
44 Normaly, you'd call your toolchain components (especially gcc) by
45 prefixing the target tuple followed by a dash and the component name
46 (eg. armeb-unknown-linux-uclibc-gcc).
48 You can enter here a sed expression to be applied to ${CT_TARGET} to
49 create an alias for your toolchain.
51 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
52 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
55 You shouldn't need to enter anything here, unless you plan to manually
56 call the tools (autotools-based ./configure will use the standard name).
63 Normaly, you'd call your toolchain components (especially gcc) by
64 prefixing the target tuple followed by a dash and the component name
65 (eg. armeb-unknown-linux-uclibc-gcc).
67 You can enter a shortcut here. This string will be used to create
68 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
69 then gcc for your toolchain will also be available as "foo-bar-gcc" along
70 with the original name).
72 You shouldn't need to enter anything here, unless you plan to manually
73 call the tools (autotools-based ./configure will use the standard name).
75 comment "Toolchain type"
84 prompt "Native (EXPERIMENTAL)"
85 depends on EXPERIMENTAL
87 Build a native toolchain.
94 Build a cross-toolchain.
99 prompt "Cross-native (EXPERIMENTAL)"
100 depends on EXPERIMENTAL
102 Build a cross-native toolchain.
103 See docs/overview.txt
107 prompt "Canadian (EXPERIMENTAL)"
108 depends on EXPERIMENTAL
110 Build a canadian-toolchain.
111 See docs/overview.txt
115 config TOOLCHAIN_TYPE
117 default "native" if NATIVE
118 default "cross" if CROSS
119 default "cross-native" if CROSS_NATIVE
120 default "canadian" if CANADIAN
124 prompt "Build system tuple"
127 Canonical name of the machine building the toolchain.
128 You should leave empty, unless you really now what you're doing.
135 The native C compiler.
137 You can set this to an alternative compiler if you have more than one
138 installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
140 You can leave this empty as well, in which case gcc will be used.
144 prompt "Host system tuple"
146 depends on NATIVE || CANADIAN
148 Canonical name of the machine running the toolchain.
152 prompt "Cross-compiler prefix for host system"
153 default "${CT_HOST}-"
154 depends on NATIVE || CANADIAN
156 C compiler targeting the host system.
160 prompt "Cross-compiler prefix for target system"
161 default "${CT_TARGET}-"
164 C compiler targeting the target system.