ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-18 20:37:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
A versatile (cross-)toolchain generator.
1,399 Commits 23 Branches 93 Tags 20 MiB
Shell 50.8%
C 27.4%
M4 16.9%
Makefile 1.9%
Yacc 1.4%
Other 1.6%
85b96f88fe
Go to file
Yann E. MORIN" 85b96f88fe TODO: update 
Add TODO list for m4, autoconf, automake and libtool.
Building our own versions would remove burden from the users
who have older versions on their distributions, and are not
ready/able/allowed to upgrade.
2009-09-04 17:27:16 +02:00
config config: move the patch choice to the extract section 2009-08-31 22:55:26 +02:00
contrib Update the OpenRISC or32 contrib to correctly set EXPERIMENTAL. 2008-10-15 08:15:28 +00:00
docs config: choose whether to use the shell or the C wrapper 2009-08-30 00:27:12 +02:00
kconfig Under Cygwin, executables have the .exe suffix: 2009-03-09 22:01:59 +00:00
licenses.d Rename directory "licenses" to "licenses.d" for those filesystems unable to handle lower/upper case. 2007-03-11 09:46:22 +00:00
patches Merge the AVR32 support branch to the default branch. 2009-08-08 22:15:25 +02:00
samples Merge the AVR32 support branch to the default branch. 2009-08-08 22:15:25 +02:00
scripts config.{gues,sub}: update 2009-09-01 10:41:44 +02:00
.hgignore Add .hgignore file. 2009-06-17 15:27:55 +02:00
.hgtags update tags 2009-06-14 18:19:22 +00:00
.version [configure] Use hg to compute the version string 2009-06-17 10:46:28 +02:00
configure Merge the bash_array branch. 2009-08-19 19:52:04 +02:00
COPYING Update and clarify COPYING (plus a typo). 2008-09-14 18:20:03 +00:00
ct-ng.comp Add a new action: show-tuple 2009-05-13 18:10:47 +00:00
ct-ng.in Add a new action: show-tuple 2009-05-13 18:10:47 +00:00
LICENSES Add the full crosstool-NG sources to the new repository of its own. 2007-02-24 11:00:05 +00:00
Makefile.in ./configure: 2009-05-13 21:32:48 +00:00
README README: fix some space alignment 2009-08-28 12:09:04 +02:00
steps.mk /devel/gcc-4.4: 2009-05-25 18:22:26 +00:00
TODO TODO: update 2009-09-04 17:27:16 +02:00

README 

This is the README for crosstool-NG

TABLE OF CONTENT /
________________/

  - GETTING STARTED
  - PARTICIPATING
    - Sending a bug report
    - Sending patches
  - CREDITS
  - KNOWN ISSUES


GETTING STARTED /
_______________/

To get you started, just enter:
  ./configure --help

You can find a (terse and WIP) documentation in docs/overview.txt.

You can also point your browser to
  http://ymorin.is-a-geek.org/projects/crosstool

PARTICIPATING /
_____________/

Sending a bug report
--------------------

If you need to send a bug report, please send a mail with subject
prefixed with "[CT_NG]" with to following destinations:
    TO: yann.morin.1998 (at) anciens.enib.fr
    CC: crossgcc (at) sourceware.org

Sending patches
---------------

If you want to enhance crosstool-NG, there's a to-do list in the TODO file.

Patches should come with the appropriate SoB line. A SoB line is typically
something like:
   Signed-off-by: John DOE <john.doe@somewhere.net>

The SoB line is clearly described in Documentation/SubmittingPatches , section
12, of your favourite Linux kernel source tree.

Then you'll need to correctly configure Mercurial. There are two extensions
that you may find usefull:
  - mq        : http://mercurial.selenic.com/wiki/MqExtension
  - patchbomb : http://mercurial.selenic.com/wiki/PatchbombExtension

Here's a typical hacking session:
  hg clone http://ymorin.is-a-geek.org/hg/crosstool-ng crosstool-ng
  cd crosstool-ng
  hg qinit
  hg qnew -D -U -e my_first_patch
  *edit patch description*
  *hack* *hack* *check* *fails* *hack* *hack* *check* *works*
  hg qref -D -e
  *edit patch description, serving as commit message*
  hg qnew -D -U -e my_second_patch
  *edit patch description*
  *hack* *hack* *check* *fails* *hack* *hack* *check* *works*
  hg qref -D -e
  *edit patch description, serving as commit message*
  hg email --outgoing --intro   \
           --from '"Your Full NAME" <your.email (at) your.domain>'   \
           --to '"Yann E. MORIN" <yann.morin.1998 (at) anciens.enib.fr>'    \
           --cc 'crossgcc (at) sourceware.org'
  *edit introductory message*
  *wait for feedback*
  *re-send if no answer for a few days*

Note: replace' (at) ' above with a plain '@'.

CREDITS /
_______/

The people that helped are listed in docs/CREDITS. Many thanks to them! :-)

KNOWN ISSUES /
____________/

The list of known issues is listed in docs/known-issues.txt.

Aloha!