u-boot.git/tools/buildman/toolchain.py, branch v2016.09

buildman: Avoid overwriting existing toolchain entries

2016-08-01T01:37:08Z

The current code for setting up the toolchain config always writes the new paths to an item called 'toolchain'. This means that it will overwrite any existing toolchain item with the same name. In practice, this means that: buildman --fetch-arch all will fetch all toolchains, but only the path of the final one will be added to the config. This normally works out OK, since most toolchains are the same version (e.g. gcc 4.9) and will be found on the same path. But it is not correct and toolchains for archs which don't use the same version will not function as expected. Adjust the code to use a complete glob of the toolchain path. Signed-off-by: Simon Glass Reviewed-by: Tom Rini

buildman: Fix a typo in TestSettingsHasPath()

2016-08-01T01:37:08Z

The function comment should say 'buildman'. Fix it. Signed-off-by: Simon Glass Reviewed-by: Tom Rini

buildman: Improve the toolchain progress/error output

2016-08-01T01:37:08Z

Use colour to make it easier to see what is going on. Also print a message before downloading a new toolchain. Mention --fetch-arch in the message that is shown when there are no available toolchains, since this is the quickest way to resolve the problem. Signed-off-by: Simon Glass Reviewed-by: Tom Rini

buildman: Allow the toolchain error to be suppressed

2016-08-01T01:37:08Z

When there are no toolchains a warning is printed. But in some cases this is confusing, such as when the user is fetching new toolchains. Adjust the function to supress the warning in this case. Signed-off-by: Simon Glass

buildman: Add a way to specific a full toolchain prefix

2016-03-18T03:27:39Z

At present buildman allows you to specify the directory containing the toolchain, but not the actual toolchain prefix. If there are multiple toolchains in a single directory, this can be inconvenient. Add a new 'toolchain-prefix' setting to the settings file, which allows the full prefix (or path to the C compiler) to be specified. Update the documentation to match. Suggested-by: Stephen Warren Reviewed-by: Joe Hershberger Signed-off-by: Simon Glass Tested-by: Stephen Warren

buildman: Allow the toolchain architecture to be specified

2016-03-14T21:34:50Z

At present the architecture is deduced from the toolchain filename. Allow it to be specified by the caller. Signed-off-by: Simon Glass Reviewed-by: Joe Hershberger

buildman: Allow the toolchain priority to be specified

2016-03-14T21:34:50Z

At present the priority of a toolchain is calculated from its filename based on hard-coded rules. Allow it to be specified by the caller. We will use this in a later patch. Also display the priority and provide a message when it is overriden by another toolchain of higher priority. Signed-off-by: Simon Glass Reviewed-by: Joe Hershberger

buildman: Fix up a few code inconsistencies in toolchain.py

2016-03-14T21:34:50Z

Normally we use a single quote for strings unless there is a reason not to (such as an embedded single quote). Fix a few counter-examples in this file. Also add a missing function-argument comment. Signed-off-by: Simon Glass Reviewed-by: Joe Hershberger

buildman: Add gcc 4.9.0 with Microblaze toolchain

2015-04-23T18:31:54Z

Also read gcc 4.9.0 at kernel.org which also have Microblaze toolchain. Signed-off-by: Michal Simek Acked-by: Simon Glass Tested-by: Simon Glass Fixed unit test failure by updating the test: Signed-off-by: Simon Glass

buildman: Correct toolchain download feature

2015-03-05T23:14:01Z

Commit d908898 updated the ScanPath() function but not its documentation and not all its callers. This breaks the toolchain check after it is downloaded. Fix it. Signed-off-by: Simon Glass Acked-by: Heiko Schocher