07ae8dd48d
This commit introduces the following upstream changes: 5ae6fcc4bb82 kconfig: fix line number in recursive inclusion error message 1a90ce36c6ef kconfig: Update ncurses package names for menuconfig bf0bbdcf1003 kconfig: Don't leak choice names during parsing f4bc1eefc160 kconfig: set SYMBOL_AUTO to the symbol marked with defconfig_list cd81fc82b93f kconfig: add xstrdup() helper 523ca58b7db2 kconfig: remove const qualifier from sym_expand_string_value() d717f24d8c68 kconfig: add xrealloc() helper 9e3e10c72536 kconfig: send error messages to stderr f3ff6fb5db68 kconfig: echo stdin to stdout if either is redirected d2a04648a5db kconfig: remove check_stdin() cd58a91def2a kconfig: remove 'config*' pattern from .gitignnore 4f208f392103 kconfig: show '?' prompt even if no help text is available cb67ab2cd2b8 kconfig: do not write choice values when their dependency becomes n 1b9eda2e4892 kconfig: Warn if help text is blank cedd55d49dee kconfig: Remove silentoldconfig from help and docs; fix kconfig/conf's help 1ccb27143360 kconfig: make "Selected by:" and "Implied by:" readable 312ee68752fa kconfig: announce removal of oldnoconfig if used d0fd0428ecf0 kconfig: fix make xconfig when gettext is missing b53688014e33 kconfig: Clarify menu and 'if' dependency propagation 9d1a9e8bc18b kconfig: Document 'if' flattening logic d3465af60f44 kconfig: Clarify choice dependency propagation 3e41ba05b6d6 kconfig: Document SYMBOL_OPTIONAL logic 765f4cdef6f8 kconfig: use default 'yy' prefix for lexer and parser 84dd95d4f87a kconfig: make conf_unsaved a local variable of conf_read() 5a3dc717b3c7 kconfig: make xfgets() really static 52e58a3caeba kconfig: make input_mode static 6479f327dea6 kconfig: Warn if there is more than one help text b92d804a5179 kconfig: drop 'boolean' keyword df60f4b92d3d kconfig: Remove menu_end_entry() 0735f7e5def2 kconfig: Document important expression functions 05cccce58045 kconfig: Document automatic submenu creation code 7cf33f88e294 kconfig: Fix choice symbol expression leak 5b1374b3b3c2 kconfig: Fix expr_free() E_NOT leak ae7440ef0c80 kconfig: Fix automatic menu creation mem leak 0724a7c32a54 kconfig: Don't leak main menus during parsing bc28fe1d5ede kconfig: Don't leak 'option' arguments during parsing 24161a6711c9 kconfig: Don't leak 'source' filenames during parsing 26e47a3c11a2 kconfig: Don't leak symbol names during parsing 29c833061c1d kconfig: generate lexer and parser during build instead of shipping e3b03bf29d6b kconfig: display recursive dependency resolution hint just once f77850d3fe0c kconfig: Clean up modules handling and fix crash fa8cedaef814 kconfig: Clarify expression rewriting 9a826842ff2f kconfig: Rename menu_check_dep() to rewrite_m() c873443430eb kconfig: Sync zconf.y with zconf.tab.c_shipped 52aede4ba5ef kconfig: Document the 'symbol' struct 33ca1a248663 kconfig: Document the 'menu' struct 2c37e08464a8 kconfig: Warn if choice default is not in choice Signed-off-by: Chris Packham <judge.packham@gmail.com>
Crosstool-NG
Introduction
Crosstool-NG aims at building toolchains. Toolchains are an essential component in a software development project. It will compile, assemble and link the code that is being developed. Some pieces of the toolchain will eventually end up in the resulting binaries: static libraries are but an example.
Before reporting a bug, please read bug reporting guidelines. Bugs that do not provide the required information will be closed without explanation.
Refer to documentation at crosstool-NG website for more information on how to configure, install and use crosstool-NG.
Note 1: If you elect to build a uClibc-based toolchain, you will have to prepare a config file for uClibc with <= crosstool-NG-1.21.0. In >= crosstool-NG-1.22.0 you only need to prepare a config file for uClibc(or uClibc-ng) if you really need a custom config for uClibc.
Note 2: If you call ct-ng --help you will get help for make(2). This is because ct-ng is in fact a make(2) script. There is no clean workaround for this.
Repository layout
To clone the crosstool-NG repository:
git clone https://github.com/crosstool-ng/crosstool-ng
Build Status
Old repositories
These are the old Mercurial repositories. They are now read-only: http://crosstool-ng.org/hg/
Pull Requests and Issues
You can find open Pull Requests on GitHub here and you can find open issues here.
Contributing
To contribute to crosstool-NG it is helpful to provide as much information as you can about your change, including any updates to documentation (if appropriate), and test... test... test.
- Fork crosstool-ng on github
- Clone the fork you made to your computer
git clone https://github.com/crosstool-ng/crosstool-ng
- Create a topic branch for your work
git checkout -b fix_comment_typo
- Make changes
- hack
- test
- hack
- etc...
- Add your changes
git add [file(s) that changed, add -p if you want to be more specific]
- Verify you are happy with your changes to be commited
git diff --cached
- Commit changes
git commit -s
The -s automatically adds your Signed-off-by: [name] <email> to your commit message. Your commit will be rejected without this.
Also, please explain what your change does. "Fix stuff" will be rejected. For examples of good commit messages, read the changelog.
- Push your topic branch with your changes to your fork
git push origin fix_comment_typo
- Go to the crosstool-ng project and click the
Compare & pull requestbutton for the branch you want to open a pull request with. - Review the pull request changes, and verify that you are opening a pull request for the appropriate branch. The title and message should reflect the nature/theme of the changes in the PR, say the title is
Fix comment typosand the message details any specifics you can provide. - You might change the crosstool-ng branch, if you are opening a pull request that is intended for a different branch. For example, when you created your topic branch you could have done:
git checkout -b fix_out_of_date_patch origin/1.22
Then when you get to this pull request screen change the base branch from master to 1.22
- By creating a pull request, the PR is entered into the backlog. A travis-ci job will run to test your changes against a select set of samples. As they start to get worked, they should be placed in the
Readystate. PRs that are being worked areIn Progress. If a questions come up about the commit that might involve changes to the commit then the PR is placed inWaiting For Response, you have two options:
- Fix the issue with the commit by adding a new commit in the topic branch that fixes the code review. Then push your changes to your branch. This option keeps the comments in the PR, and allows for further code review. I personally dislike this, because people are lazy and fix reviews with
fix more review issues. Please make good commit messages! All rules about commits from above apply! THIS IS PREFERED
Add your changes
git add [file(s) that changed, add -p if you want to be more specific]
Verify you are happy with your changes to be commited
git diff --cached
Commit changes
git commit -s
- Push your topic branch with your changes to your fork
git push origin fix_comment_typo
At this point the PR will be updated to have the latest commit to that branch, and can be subsequently reviewed.
- Interactively rebase the offending commit(s) to fix the code review. This option is slightly annoying on Github, as the comments are stored with the commits, and are hidden when new commits replace the old commits. They used to disappear completely; now Github shows a grey 'View outdated' link next to the old commits.
This recipe also comes handy with other issues, like your topic branch not being up-to-date with master:
git fetch --all
git rebase --ignore-whitespace origin master
git rebase -i <offending-commit-id>^
NOTE: The --ignore-whitespace stops git apply (which is called by rebase) from changing any whitespace when it runs.
Replace pick with edit or remove the line to delete a commit.
Fix the issue in the code review.
git add [file(s)]
git rebase --continue
<update commit comment if needed>
git push --force origin fix_comment_typo
Patchwork
We previously used patchwork for development, but it is no longer used. I'd like to see patches that are still applicable turned into Pull Requests on GitHub.
You can find the list of pending patches available on patchwork.
More Info
You can find all of this and more at crosstool-ng.org
Report issues at the project site on GitHub.
We have a mailing list. Archive and subscription info can be found here: https://sourceware.org/ml/crossgcc/
Aloha! :-)