summaryrefslogtreecommitdiff
path: root/config/libc/newlib.in
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2009-10-26 21:00:30 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2009-10-26 21:00:30 (GMT)
commit49e5b08739dd69624e7a5e7173bc32fe3fd8fd91 (patch)
tree6f218e6c533046006f55ab5bd4991bb967819686 /config/libc/newlib.in
parente73418236d013152b3891948faa791a45ddc9c20 (diff)
libc/newlib: allow using CVS snapshots
The newlib "team" rolls new releases about once a year (december). This is quite a long time between releases, in case code was fixed. So, allow user to use a CVS snapshot to benefit early from fixes and enhancements to newlib.
Diffstat (limited to 'config/libc/newlib.in')
-rw-r--r--config/libc/newlib.in21
1 files changed, 21 insertions, 0 deletions
diff --git a/config/libc/newlib.in b/config/libc/newlib.in
index 61803d7..446cb4d 100644
--- a/config/libc/newlib.in
+++ b/config/libc/newlib.in
@@ -20,13 +20,34 @@ config LIBC_NEWLIB_V_1_17_0
bool
prompt "1.17.0"
+config LIBC_NEWLIB_CVS
+ bool
+ prompt "Use CVS snapshot"
+ help
+ The newlib "team" rolls new releases about once a year (december).
+ This is quite a long time between releases, in case code was fixed.
+
+ Saying 'Y' here will allow you to use the bleeding-edge code from
+ the CVS repository. This may or may not fix your issues, may or may
+ not build, may or may not crash your machine, may or may not withdraw
+ money from your bank account, may or may not date your girlfriend,
+ may or may not resurect Elvis... :-)
+
+ In a word: use the CVS snapshot at your own risk!
+
endchoice
config LIBC_VERSION
string
+ prompt "use CVS tag" if LIBC_NEWLIB_CVS
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
default "1.17.0" if LIBC_NEWLIB_V_1_17_0
+ help
+ Enter the tag you want to use.
+ Leave empty to use the 'head' of the repository.
+
+comment "Architecture specific options"
config ATMEL_AVR32_HEADERS
bool