| d5fe013c | 04-Oct-2016 |
York Sun <york.sun@nxp.com> |
tools: buildman: Add compiler wrapper
Now we can use compiler wrapper such as ccache or distcc for buildman.
Signed-off-by: York Sun <york.sun@nxp.com> CC: Simon Glass <sjg@chromium.org> Acked-by:
tools: buildman: Add compiler wrapper
Now we can use compiler wrapper such as ccache or distcc for buildman.
Signed-off-by: York Sun <york.sun@nxp.com> CC: Simon Glass <sjg@chromium.org> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| f40fa9b3 | 04-Oct-2016 |
York Sun <york.sun@nxp.com> |
tools: buildman: Remove duplicated code
Signed-off-by: York Sun <york.sun@nxp.com> CC: Simon Glass <sjg@chromium.org> Fixed commit subject: Signed-off-by: Simon Glass <sjg@chromium.org> Acked-by: Si
tools: buildman: Remove duplicated code
Signed-off-by: York Sun <york.sun@nxp.com> CC: Simon Glass <sjg@chromium.org> Fixed commit subject: Signed-off-by: Simon Glass <sjg@chromium.org> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 34c38896 | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
dtoc: Make integer division python 3.x safe
If we use the '/' operator then python 3.x will produce a float, and refuse to multiply the string sequence in Conv_name_to_c by it with:
TypeError:
dtoc: Make integer division python 3.x safe
If we use the '/' operator then python 3.x will produce a float, and refuse to multiply the string sequence in Conv_name_to_c by it with:
TypeError: can't multiply sequence by non-int of type 'float'
Use the '//' operator instead to enforce that we want integer rather than floating point division.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| c4c5f9ee | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
dtoc: Decode strings for struct.unpack on python 3.x
On python 3.x struct.unpack will complain if we provide it with a string since it expects to operate on a bytes object. In order to satisfy this
dtoc: Decode strings for struct.unpack on python 3.x
On python 3.x struct.unpack will complain if we provide it with a string since it expects to operate on a bytes object. In order to satisfy this requirement, encode the string to a bytes object when running on python 3.x.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 4ae6549f | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
dtoc: Use items() to iterate over dictionaries in python 3.x
In python 3.x the iteritems() method has been removed from dictionaries, and the items() method does effectively the same thing. On pytho
dtoc: Use items() to iterate over dictionaries in python 3.x
In python 3.x the iteritems() method has been removed from dictionaries, and the items() method does effectively the same thing. On python 2.x using items() is a little less efficient since it involves copying data, but as speed isn't a concern in the affected code switch to using items() anyway for simplicity.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| f5d44b9b | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
patman: Fix doctest StringIO import for python 3.x
In python 3.x StringIO is no longer a module, and the class can instead be found in the io module. Adjust the code in the doctest input to account
patman: Fix doctest StringIO import for python 3.x
In python 3.x StringIO is no longer a module, and the class can instead be found in the io module. Adjust the code in the doctest input to account for both.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| c9eac38a | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
patman: Use items() to iterate over dictionaries
In python 3.x the iteritems() method has been removed from dictionaries, and the items() method does effectively the same thing. On python 2.x using
patman: Use items() to iterate over dictionaries
In python 3.x the iteritems() method has been removed from dictionaries, and the items() method does effectively the same thing. On python 2.x using items() is a little less efficient since it involves copying data, but as speed isn't a concern in this code switch to using items() anyway for simplicity.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 2ce7b21e | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
patman: Import 'configparser' lower case to be python 3.x safe
In python 3.x module names used in import statements are case sensitive, and the configparser module is named in all lower-case. Import
patman: Import 'configparser' lower case to be python 3.x safe
In python 3.x module names used in import statements are case sensitive, and the configparser module is named in all lower-case. Import it as such in order to avoid errors when running with python 3.x.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| ac3fde93 | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
patman: Make exception handling python 3.x safe
Syntax for exception handling is a little more strict in python 3.x. Convert all uses to a form accepted by both python 2.x & python 3.x.
Signed-off-
patman: Make exception handling python 3.x safe
Syntax for exception handling is a little more strict in python 3.x. Convert all uses to a form accepted by both python 2.x & python 3.x.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| a920a17b | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
patman: Make print statements python 3.x safe
In python 3.x, print must be used as a function call. Convert all print statements to the function call style, importing from __future__ where we print
patman: Make print statements python 3.x safe
In python 3.x, print must be used as a function call. Convert all print statements to the function call style, importing from __future__ where we print with no trailing newline or print to a file object.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 12e5476d | 27-Sep-2016 |
Paul Burton <paul.burton@imgtec.com> |
patman: Replace tabs with spaces
In preparation for running on python 3.x, which will refuse to run scripts which mix tabs & spaces for indentation, replace 2 tab characters present in series.py wit
patman: Replace tabs with spaces
In preparation for running on python 3.x, which will refuse to run scripts which mix tabs & spaces for indentation, replace 2 tab characters present in series.py with spaces.
Signed-off-by: Paul Burton <paul.burton@imgtec.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 3cb44ba8 | 25-Sep-2016 |
Simon Glass <sjg@chromium.org> |
dtoc: Add a way for tests to request the fallback library
We need to test both the normal (Python libfdt module) and fallback (fdtget) implementations of the Fdt class. Add a way to select which imp
dtoc: Add a way for tests to request the fallback library
We need to test both the normal (Python libfdt module) and fallback (fdtget) implementations of the Fdt class. Add a way to select which implementation to use.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 8828254c | 25-Sep-2016 |
Simon Glass <sjg@chromium.org> |
dtoc: Adjust GetProps() in fdt_normal to use the node path
There is no need to pass a node path separately. Instead we should use the path for the node provided. Correct this.
Signed-off-by: Simon
dtoc: Adjust GetProps() in fdt_normal to use the node path
There is no need to pass a node path separately. Instead we should use the path for the node provided. Correct this.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 2f256648 | 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Don't show a stacktrace on Ctrl-C
When Ctrl-C is pressed, just exited quietly. There is no sense in displaying a stack trace since buildman will always be in the same place: waiting for th
buildman: Don't show a stacktrace on Ctrl-C
When Ctrl-C is pressed, just exited quietly. There is no sense in displaying a stack trace since buildman will always be in the same place: waiting for threads to complete building all the jobs on the queue.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| d436e381 | 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Allow builds to terminate cleanly
It is annoying that buildman does not respond cleanly to Ctrl-C or SIGINT, particularly on machines with lots of CPUS. Unfortunately queue.join() blocks t
buildman: Allow builds to terminate cleanly
It is annoying that buildman does not respond cleanly to Ctrl-C or SIGINT, particularly on machines with lots of CPUS. Unfortunately queue.join() blocks the main thread and does not allow it to see the signal. Use a separate thread instead,
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| a556eeeb | 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Put our local libraries first in the path
If patman is installed on the machine (e.g. in the standard dist-packages directory), it will find libraries from there in preference to our local
buildman: Put our local libraries first in the path
If patman is installed on the machine (e.g. in the standard dist-packages directory), it will find libraries from there in preference to our local libraries. Adjust the order of the path to ensure that local libraries are found first.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 745b395a | 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Print a message indicating the build is starting
Make it clear when buildman actually starts building. This happens when it has prepared the threads, working directory and output directori
buildman: Print a message indicating the build is starting
Make it clear when buildman actually starts building. This happens when it has prepared the threads, working directory and output directories.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| b222abe7 | 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Print a message when removing old directories
When buildman starts, it prepares its output directory by removing any old build directories which will not be used this time. This can happen
buildman: Print a message when removing old directories
When buildman starts, it prepares its output directory by removing any old build directories which will not be used this time. This can happen if a previous build left directories around for commit hashes which are no-longer part of the branch.
This can take quite a while, so print a message to indicate what is going on.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 21f0eb33 | 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Tidy up the 'cloning' message
On a machine with a lot of CPUs this prints a lot of useless lines of the form:
Cloning repo for thread <n>
Adjust the output so that these all appear on
buildman: Tidy up the 'cloning' message
On a machine with a lot of CPUs this prints a lot of useless lines of the form:
Cloning repo for thread <n>
Adjust the output so that these all appear on one line, and disappear when the cloning is complete.
Note: This cloning is actually unnecessary and very wasteful on disk space (about 3.5GB each time). It would be better to create symlinks.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|