Get rid of eclipse fiels once and for all.
Homogenise the references to crosstool-NG:
- the project is named "crosstool-NG"
- the front-end is named "ct-ng"
- don't use shortcuts (such as "ct-ng" to stand for "crosstool-NG")
Default action is to print help.
Don't speak of make rules when dumping help, just speak of actions.
1.1 --- a/.cdtproject Mon Jul 02 17:52:15 2007 +0000
1.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
1.3 @@ -1,67 +0,0 @@
1.4 -<?xml version="1.0" encoding="UTF-8"?>
1.5 -<?eclipse-cdt version="2.0"?>
1.6 -
1.7 -<cdtproject id="org.eclipse.cdt.make.core.make">
1.8 -<extension id="org.eclipse.cdt.core.ELF" point="org.eclipse.cdt.core.BinaryParser"/>
1.9 -<data>
1.10 -<item id="scannerConfiguration">
1.11 -<autodiscovery enabled="true" problemReportingEnabled="true" selectedProfileId="org.eclipse.cdt.make.core.GCCStandardMakePerProjectProfile"/>
1.12 -<profile id="org.eclipse.cdt.make.core.GCCStandardMakePerProjectProfile">
1.13 -<buildOutputProvider>
1.14 -<openAction enabled="true" filePath=""/>
1.15 -<parser enabled="true"/>
1.16 -</buildOutputProvider>
1.17 -<scannerInfoProvider id="specsFile">
1.18 -<runAction arguments="-E -P -v -dD ${plugin_state_location}/${specs_file}" command="gcc" useDefault="true"/>
1.19 -<parser enabled="true"/>
1.20 -</scannerInfoProvider>
1.21 -</profile>
1.22 -<profile id="org.eclipse.cdt.make.core.GCCStandardMakePerFileProfile">
1.23 -<buildOutputProvider>
1.24 -<openAction enabled="false" filePath=""/>
1.25 -<parser enabled="true"/>
1.26 -</buildOutputProvider>
1.27 -<scannerInfoProvider id="makefileGenerator">
1.28 -<runAction arguments="-f ${project_name}_scd.mk" command="make" useDefault="true"/>
1.29 -<parser enabled="false"/>
1.30 -</scannerInfoProvider>
1.31 -</profile>
1.32 -<profile id="org.eclipse.cdt.managedbuilder.core.GCCManagedMakePerProjectProfile">
1.33 -<buildOutputProvider>
1.34 -<openAction enabled="false" filePath=""/>
1.35 -<parser enabled="true"/>
1.36 -</buildOutputProvider>
1.37 -<scannerInfoProvider id="specsFile">
1.38 -<runAction arguments="-E -P -v -dD ${plugin_state_location}/${specs_file}" command="gcc" useDefault="true"/>
1.39 -<parser enabled="false"/>
1.40 -</scannerInfoProvider>
1.41 -</profile>
1.42 -<profile id="org.eclipse.cdt.managedbuilder.core.GCCWinManagedMakePerProjectProfile">
1.43 -<buildOutputProvider>
1.44 -<openAction enabled="false" filePath=""/>
1.45 -<parser enabled="true"/>
1.46 -</buildOutputProvider>
1.47 -<scannerInfoProvider id="specsFile">
1.48 -<runAction arguments="-E -P -v -dD ${plugin_state_location}/${specs_file}" command="gcc" useDefault="true"/>
1.49 -<parser enabled="false"/>
1.50 -</scannerInfoProvider>
1.51 -</profile>
1.52 -</item>
1.53 -<item id="org.eclipse.cdt.core.pathentry">
1.54 -<pathentry kind="src" path=""/>
1.55 -<pathentry kind="out" path=""/>
1.56 -<pathentry kind="con" path="org.eclipse.cdt.make.core.DISCOVERED_SCANNER_INFO"/>
1.57 -</item>
1.58 -<item id="org.eclipse.cdt.make.core.buildtargets">
1.59 -<buildTargets>
1.60 -<target name="Build toolchain" path="" targetID="org.eclipse.cdt.make.MakeTargetBuilder">
1.61 -<buildCommand>make</buildCommand>
1.62 -<buildArguments/>
1.63 -<buildTarget>all</buildTarget>
1.64 -<stopOnError>true</stopOnError>
1.65 -<useDefaultCommand>true</useDefaultCommand>
1.66 -</target>
1.67 -</buildTargets>
1.68 -</item>
1.69 -</data>
1.70 -</cdtproject>
2.1 --- a/.project Mon Jul 02 17:52:15 2007 +0000
2.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
2.3 @@ -1,34 +0,0 @@
2.4 -<?xml version="1.0" encoding="UTF-8"?>
2.5 -<projectDescription>
2.6 - <name>crosstool-ng</name>
2.7 - <comment></comment>
2.8 - <projects>
2.9 - </projects>
2.10 - <buildSpec>
2.11 - <buildCommand>
2.12 - <name>org.eclipse.ui.externaltools.ExternalToolBuilder</name>
2.13 - <triggers>full,incremental,</triggers>
2.14 - <arguments>
2.15 - <dictionary>
2.16 - <key>LaunchConfigHandle</key>
2.17 - <value><project>/.externalToolBuilders/org.eclipse.cdt.make.core.makeBuilder.launch</value>
2.18 - </dictionary>
2.19 - </arguments>
2.20 - </buildCommand>
2.21 - <buildCommand>
2.22 - <name>org.eclipse.ui.externaltools.ExternalToolBuilder</name>
2.23 - <triggers>full,incremental,</triggers>
2.24 - <arguments>
2.25 - <dictionary>
2.26 - <key>LaunchConfigHandle</key>
2.27 - <value><project>/.externalToolBuilders/org.eclipse.cdt.make.core.ScannerConfigBuilder.launch</value>
2.28 - </dictionary>
2.29 - </arguments>
2.30 - </buildCommand>
2.31 - </buildSpec>
2.32 - <natures>
2.33 - <nature>org.eclipse.cdt.core.cnature</nature>
2.34 - <nature>org.eclipse.cdt.make.core.makeNature</nature>
2.35 - <nature>org.eclipse.cdt.make.core.ScannerConfigNature</nature>
2.36 - </natures>
2.37 -</projectDescription>
3.1 --- a/CREDITS Mon Jul 02 17:52:15 2007 +0000
3.2 +++ b/CREDITS Mon Jul 02 19:40:54 2007 +0000
3.3 @@ -9,8 +9,8 @@
3.4 And in order of appearance on the crossgcc ML:
3.5
3.6 Allan CLARK for his investigations on building toolchains on MacOS-X.
3.7 - Allan made extensive tests of the first alpha of ct-ng on his MacOS-X
3.8 - and unveiled some bash-2.05 weirdness.
3.9 + Allan made extensive tests of the first alpha of crosstool-NG-ng on his
3.10 + MacOS-X, and unveiled some bash-2.05 weirdness.
3.11
3.12 Enrico WEIGELT for some improvements of the build procedure:
3.13 - cxa_atexit disabling for C libraries not supporting it (uClibc)
4.1 --- a/Makefile.in Mon Jul 02 17:52:15 2007 +0000
4.2 +++ b/Makefile.in Mon Jul 02 19:40:54 2007 +0000
4.3 @@ -1,4 +1,4 @@
4.4 -# Makefile.in for building crosstool-ng
4.5 +# Makefile.in for building crosstool-NG
4.6 # This file serves as source for the ./configure operation
4.7
4.8 all: build
5.1 --- a/config/global.in Mon Jul 02 17:52:15 2007 +0000
5.2 +++ b/config/global.in Mon Jul 02 19:40:54 2007 +0000
5.3 @@ -9,7 +9,7 @@
5.4
5.5 menu "Paths and misc options"
5.6
5.7 -comment "Crosstool-ng behavior"
5.8 +comment "crosstool-NG behavior"
5.9
5.10 config EXPERIMENTAL
5.11 bool
5.12 @@ -172,11 +172,11 @@
5.13 default n
5.14 depends on CUSTOM_PATCH
5.15 help
5.16 - Don't apply patches coming with CT-NG, only those patches available in
5.17 - the directory below.
5.18 + Don't apply patches coming with crosstool-NG, only those patches available
5.19 + in the directory below.
5.20
5.21 - If you say 'N' here, then the patches provided with CT-NG will be applied
5.22 - first, and then your patches.
5.23 + If you say 'N' here, then the patches provided with crosstool-NG will be
5.24 + applied first, and then your patches.
5.25
5.26 config CUSTOM_PATCH_DIR
5.27 string
5.28 @@ -311,14 +311,14 @@
5.29 default n
5.30 depends on ! LOG_ERROR
5.31 help
5.32 - Treat warnings from the different tools as crosstool-ng warnings.
5.33 + Treat warnings from the different tools as crosstool-NG warnings.
5.34 If you say 'y' here, then those warnings will be prefixed with
5.35 '[WARN ]' instead of the default '[ALL ]'.
5.36
5.37 You can safely say 'n' here. Those warnings will anyway be
5.38 recorded in the log file (provided you configured one).
5.39
5.40 - Tools error will always be logged as crosstool-ng errors.
5.41 + Tools error will always be logged as crosstool-NG errors.
5.42
5.43 config LOG_PROGRESS_BAR
5.44 bool
6.1 --- a/configure Mon Jul 02 17:52:15 2007 +0000
6.2 +++ b/configure Mon Jul 02 19:40:54 2007 +0000
6.3 @@ -71,7 +71,7 @@
6.4
6.5 do_help() {
6.6 cat <<__EOF__
6.7 -\`configure' configures ct-ng ${VERSION} to adapt to many kind of systems.
6.8 +\`configure' configures crosstool-NG ${VERSION} to adapt to many kind of systems.
6.9
6.10 USAGE: ./configure [OPTION]...
6.11
6.12 @@ -129,7 +129,7 @@
6.13 Makefile.in >Makefile
6.14
6.15 cat <<__EOF__
6.16 -ct-ng configured as follows:
6.17 +crosstool-NG configured as follows:
6.18 PREFIX="${PREFIX}"
6.19 BINDIR="${BINDIR}"
6.20 LIBDIR="${LIBDIR}"
7.1 --- a/ct-ng.in Mon Jul 02 17:52:15 2007 +0000
7.2 +++ b/ct-ng.in Mon Jul 02 19:40:54 2007 +0000
7.3 @@ -13,7 +13,7 @@
7.4 export CT_LIB_DIR:=@@CT_LIBDIR@@
7.5 export CT_DOC_DIR:=@@CT_DOCDIR@@
7.6
7.7 -# This is crosstool-ng version string
7.8 +# This is crosstool-NG version string
7.9 export CT_VERSION=$(shell cat $(CT_LIB_DIR)/version)
7.10
7.11 export CT_STOP=$(STOP)
7.12 @@ -21,7 +21,7 @@
7.13
7.14 .PHONY: $(PHONY)
7.15 PHONY += all
7.16 -all: build
7.17 +all: help
7.18
7.19 HOST_CC = gcc -funsigned-char
7.20
7.21 @@ -29,23 +29,23 @@
7.22 help:: help-head help-config help-samples help-build help-distrib help-env help-tail
7.23
7.24 help-head::
7.25 - @echo 'Available make rules:'
7.26 + @echo 'Available actions:'
7.27
7.28 help-config::
7.29 @echo
7.30 - @echo 'Configuration rules:'
7.31 + @echo 'Configuration actions:'
7.32
7.33 help-samples::
7.34 @echo
7.35 - @echo 'Preconfigured rules:'
7.36 + @echo 'Preconfigured actions:'
7.37
7.38 help-build::
7.39 @echo
7.40 - @echo 'Build rules:'
7.41 + @echo 'Build actions:'
7.42
7.43 help-distrib::
7.44 @echo
7.45 - @echo 'Distribution rules:'
7.46 + @echo 'Distribution actions:'
7.47
7.48 help-env::
7.49 @echo
7.50 @@ -53,14 +53,14 @@
7.51
7.52 help-tail::
7.53 @echo
7.54 - @echo 'Execute "$(CT_NG) config" or "$(CT_NG) menuconfig" to configure ct-ng'
7.55 - @echo 'Execute "$(CT_NG)" or "$(CT_NG) all" to build all targets marked with [*]'
7.56 + @echo 'Execute "$(CT_NG) config" or "$(CT_NG) menuconfig" to configure crosstool-NG'
7.57 + @echo 'Execute "$(CT_NG) build" to build your toolchain'
7.58 @echo 'See "man 1 ct-ng" for some help as well'
7.59
7.60 # End help system
7.61
7.62 help-build::
7.63 - @echo '* build - Build the toolchain'
7.64 + @echo ' build - Build the toolchain'
7.65 @echo ' clean - Remove generated files'
7.66 @echo ' distclean - Remove generated files, configuration and build directories'
7.67
8.1 --- a/docs/ct-ng.1.in Mon Jul 02 17:52:15 2007 +0000
8.2 +++ b/docs/ct-ng.1.in Mon Jul 02 19:40:54 2007 +0000
8.3 @@ -1,15 +1,15 @@
8.4 -." crosstool-ng man page
8.5 +." crosstool-NG man page
8.6 ." Copyright 2007 Yann E. MORIN
8.7 ." Licensed under the Creative Commons BY-SA, v2.5
8.8 ."
8.9 ." Beautifying URLs
8.10 .mso www.tmac
8.11 ."
8.12 -.TH ct-ng 1 "@@CT_DATE@@" "version @@CT_VERSION@@" "User Commands"
8.13 +.TH crosstool-NG 1 "@@CT_DATE@@" "version @@CT_VERSION@@" "User Commands"
8.14 ."
8.15 ."
8.16 .SH NAME
8.17 -ct-ng, crosstool-ng \- Build cross-toolchains
8.18 +ct-ng, crosstool-NG \- Build cross-toolchains
8.19 ."
8.20 ."
8.21 .SH SYNOPSIS
8.22 @@ -19,7 +19,7 @@
8.23 .SH DESCRIPTION
8.24 Building a cross-toolchain can be a real pain.
8.25 .PP
8.26 -.B ct-ng
8.27 +.B crosstool-NG
8.28 makes it easy to build cross-toolchains, and allows you to take all the juice
8.29 out of your target by configuring the differents components of the toolchain
8.30 accordingly to the targeted processor.
8.31 @@ -35,7 +35,7 @@
8.32 .TP
8.33 .B menuconfig
8.34 Configures
8.35 -.B ct-ng
8.36 +.B crosstool-NG
8.37 using a configurator menu very similar to that of the Linux kernel.
8.38 ."
8.39 .TP
8.40 @@ -47,7 +47,7 @@
8.41 .TP
8.42 .B saveconfig
8.43 Save the current
8.44 -.B ct-ng
8.45 +.B crosstool-NG
8.46 configuration, and associated components' config files, into a sample. Samples
8.47 are saved in their own sub-directory, named after the target's triplet, in the
8.48 .I samples
8.49 @@ -61,11 +61,7 @@
8.50 ."
8.51 .TP
8.52 .B build
8.53 -Builds the configured toolchain. If
8.54 -.B ct-ng
8.55 -is called without action, then
8.56 -.B build
8.57 -is impiled.
8.58 +Builds the configured toolchain.
8.59 ."
8.60 .TP
8.61 .B liststeps
8.62 @@ -76,7 +72,7 @@
8.63 .TP
8.64 .B clean
8.65 Remove files generated by
8.66 -.B ct-ng
8.67 +.B crosstool-NG
8.68 for itself (these are mostly the configurators' binaries).
8.69 ."
8.70 .TP
8.71 @@ -91,7 +87,7 @@
8.72 .TP
8.73 .B regtest
8.74 Calls the
8.75 -.B ct-ng
8.76 +.B crosstool-NG
8.77 regression test suite. All samples are build, and the regression test suite is
8.78 run against every one of them.
8.79 ."
8.80 @@ -102,12 +98,12 @@
8.81 and
8.82 .I config.sub
8.83 scripts. These scripts are used by
8.84 -.B ct-ng
8.85 +.B crosstool-NG
8.86 to canonicalise the machines' name (host, build and target machines).
8.87 .TP
8.88 .B tarball
8.89 Builds a tarball of the generated toolchain, also saving the scripts from
8.90 -.B ct-ng
8.91 +.B crosstool-NG
8.92 that are needed to rebuild the target, and also saving the tarballs of the
8.93 componnents that were used.
8.94 ."
8.95 @@ -132,27 +128,27 @@
8.96 .SH BUGS
8.97 As of today (@@CT_DATE@@), building tarballs is broken. It is difficult to
8.98 foresee how every parts of
8.99 -.B ct-ng
8.100 +.B crosstool-NG
8.101 are going to be installed. Each parts is needed to build a tarball, as it
8.102 contains all that is needed to rebuild the toolchain from scratch: toolchain
8.103 components' sources,
8.104 -.B ct-ng
8.105 +.B crosstool-NG
8.106 configuration, but also all
8.107 -.B ct-ng
8.108 +.B crosstool-NG
8.109 scripts.
8.110 ."
8.111 .SH SECURITY
8.112 .B Don't run as root!
8.113 Great care has been taken to avoid mistakes, but bug-free programs don't
8.114 exist. During normal operation,
8.115 -.B ct-ng
8.116 +.B crosstool-NG
8.117 removes entire directories. If you run as root, and there is a bug or you
8.118 mis-configured
8.119 -.BR ct-ng ,
8.120 +.BR crosstool-NG ,
8.121 entire important directories could be removed (eg.
8.122 .IR /usr ),
8.123 although
8.124 -.B ct-ng
8.125 +.B crosstool-NG
8.126 will refuse to install in some well known critical directories.
8.127 ."
8.128 .SH AUTHORS
9.1 --- a/docs/overview.txt Mon Jul 02 17:52:15 2007 +0000
9.2 +++ b/docs/overview.txt Mon Jul 02 19:40:54 2007 +0000
9.3 @@ -1,5 +1,5 @@
9.4 File.........: overview.txt
9.5 -Content......: Overview of how ct-ng works.
9.6 +Content......: Overview of how crosstool-NG works.
9.7 Copyrigth....: (C) 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
9.8 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
9.9
9.10 @@ -38,7 +38,7 @@
9.11 - they are proven if used by a wide community.
9.12
9.13 But once you want to get all the juice out of your specific hardware, you will
9.14 -want to build your own toolchain. This is where crosstool-ng comes into play.
9.15 +want to build your own toolchain. This is where crosstool-NG comes into play.
9.16
9.17 There are also a number of tools that builds toolchains for specific needs,
9.18 which is not really scalable. Examples are:
9.19 @@ -80,9 +80,9 @@
9.20 support.
9.21
9.22 The only option left to me was rewrite crosstool from scratch. I decided to go
9.23 -this way, and name the new implementation ct-ng, standing for crosstool Next
9.24 -Generation, as many other comunity projects do, and as a wink at the TV series
9.25 -"Star Trek: The Next Generation". ;-)
9.26 +this way, and name the new implementation crosstool-NG, standing for crosstool
9.27 +Next Generation, as many other comunity projects do, and as a wink at the TV
9.28 +series "Star Trek: The Next Generation". ;-)
9.29
9.30 ____________________________
9.31 /
9.32 @@ -126,7 +126,7 @@
9.33
9.34 CT_LOCAL_TARBALLS_DIR:
9.35 If you already have sone tarballs in a direcotry, enter it here. That will
9.36 - speed up the retrieving phase, where crosstool-ng would otherwise download
9.37 + speed up the retrieving phase, where crosstool-NG would otherwise download
9.38 those tarballs.
9.39
9.40 CT_PREFIX_DIR:
9.41 @@ -148,7 +148,7 @@
9.42 Running crosstool-NG /
9.43 _____________________/
9.44
9.45 -ct-ng is configured by a configurator presenting a menu-stuctured set of
9.46 +crosstool-NG is configured by a configurator presenting a menu-stuctured set of
9.47 options. These options let you specify the way you want your toolchain built,
9.48 where you want it installed, what architecture and specific processor it
9.49 will support, the version of the components you want to use, etc... The
9.50 @@ -235,29 +235,30 @@
9.51 one it is built on, and running again on this exact same machine. You have
9.52 to build such a toolchain when you want to use an updated component, such
9.53 as a newer gcc for example.
9.54 - ct-ng calls it "native".
9.55 + crosstool-NG calls it "native".
9.56
9.57 2) build == host != target
9.58 This is a classic cross-toolchain, which is expected to be run on the same
9.59 machine it is compiled on, and generate code to run on a second machine,
9.60 the target.
9.61 - ct-ng calls it "cross".
9.62 + crosstool-NG calls it "cross".
9.63
9.64 3) build != host == target
9.65 Such a toolchain is also a native toolchain, as it targets the same machine
9.66 as it runs on. But it is build on another machine. You want such a
9.67 toolchain when porting to a new architecture, or if the build machine is
9.68 much faster than the host machine.
9.69 - ct-ng calls it "cross-native".
9.70 + crosstool-NG calls it "cross-native".
9.71
9.72 4) build != host != target
9.73 This one is called a canadian-toolchain (*), and is tricky. The three
9.74 machines in play are different. You might want such a toolchain if you
9.75 have a fast build machine, but the users will use it on another machine,
9.76 and will produce code to run on a third machine.
9.77 - ct-ng calls it "canadian".
9.78 + crosstool-NG calls it "canadian".
9.79
9.80 -ct-ng can build all these kinds of toolchains (or is aiming at it, anyway!)
9.81 +crosstool-NG can build all these kinds of toolchains (or is aiming at it,
9.82 +anyway!)
9.83
9.84 (*) The term Canadian Cross came about because at the time that these issues
9.85 were all being hashed out, Canada had three national political parties.
10.1 --- a/kconfig/Makefile Mon Jul 02 17:52:15 2007 +0000
10.2 +++ b/kconfig/Makefile Mon Jul 02 19:40:54 2007 +0000
10.3 @@ -1,5 +1,5 @@
10.4 # ===========================================================================
10.5 -# crosstool-ng configuration targets
10.6 +# crosstool-NG configuration targets
10.7 # These targets are used from top-level makefile
10.8
10.9 # Derive the project version from, well, the project version:
11.1 --- a/scripts/crosstool.sh Mon Jul 02 17:52:15 2007 +0000
11.2 +++ b/scripts/crosstool.sh Mon Jul 02 19:40:54 2007 +0000
11.3 @@ -39,7 +39,7 @@
11.4 CT_DoLog INFO "Checking environment sanity"
11.5
11.6 # Enable known ordering of files in directory listings:
11.7 -CT_Test "Crosstool-NG might not work as expected with LANG=\"${LANG}\"" -n "${LANG}"
11.8 +CT_Test "crosstool-NG might not work as expected with LANG=\"${LANG}\"" -n "${LANG}"
11.9 case "${LC_COLLATE},${LC_ALL}" in
11.10 # These four combinations are known to sort files in the correct order:
11.11 fr_FR*,) ;;
12.1 --- a/scripts/tarball.sh.broken Mon Jul 02 17:52:15 2007 +0000
12.2 +++ b/scripts/tarball.sh.broken Mon Jul 02 19:40:54 2007 +0000
12.3 @@ -52,7 +52,7 @@
12.4 mkdir -p "${CT_BUILD_DIR}"
12.5 CT_MktempDir tempdir
12.6
12.7 -# Save crosstool-ng, as it is configured for the current toolchain.
12.8 +# Save crosstool-NG, as it is configured for the current toolchain.
12.9 topdir=`basename "${CT_TOP_DIR}"`
12.10 CT_Pushd "${CT_TOP_DIR}/.."
12.11
12.12 @@ -77,7 +77,7 @@
12.13 # Render the install directory writable
12.14 chmod u+w "${CT_PREFIX_DIR}"
12.15
12.16 -CT_DoLog INFO "Saving crosstool-ng into the toolchain directory"
12.17 +CT_DoLog INFO "Saving crosstool-NG into the toolchain directory"
12.18 tar cvjf "${CT_PREFIX_DIR}/${topdir}.${CT_TARGET}.tar.bzip2" \
12.19 --no-wildcards-match-slash \
12.20 -X "${exclude_list}" \
13.1 --- a/tools/extractConfig.sh Mon Jul 02 17:52:15 2007 +0000
13.2 +++ b/tools/extractConfig.sh Mon Jul 02 19:40:54 2007 +0000
13.3 @@ -1,7 +1,7 @@
13.4 #!/bin/sh
13.5
13.6 -# This scripts extracts a crosstool-ng configuration from the log file
13.7 -# of a toolchain build with crosstool-ng.
13.8 +# This scripts extracts a crosstool-NG configuration from the log file
13.9 +# of a toolchain build with crosstool-NG.
13.10
13.11 # Usage: $0 <logfile>
13.12