Adds a --sanitize option to command line for reports.py
and also for the reports.report() interface from setbuilder.py
to remove the Remotes information from git.
Closes#3887.
- Use the same VERSION file format as rtems-tools so a common release
generation can be used.
- The version.py is almost the same as rtems-tools. There are some
minor differences, one is the RTEMS version is present in this
file while rtems-tool uses config/rtems-release.ini.
Updates #3822
- Add '%source download <source>' to only download the source
and do not unpack and prep. This can used when a package
internally needs another source package.
- Install the staging root only if it is present. A package
may internally build another package that is not staged as it
is not suitable for installing.
Updates #3250
Updatew #3797
- Update rtems-bsp support to correctly handle hosts for BSP.
- Clean up the options for a BSP.
- Check all RTEMS 5 packages and add 5/rtems-packages for all that build.
- Update download locations and checksum of all packages.
- The work requires the kernel and Libbsd hacve the same prefix.
- Track the size of a build of a package in a build set to determine the
maximum amout of disk space used. This can be used as a guide to
documenting how much space a user needs to set aside to build a specific
set of tools.
- The `%clean` stage of a build is now split into a separate script.
I do not think this is an issue because I could not find any `%clean`
sections in any build configs we have. In time support for the
`%clean` section will be removed, the package builder cleans up.
Closes#3516
Directives in if statements end at the end of an if. The cannot
change or split across directive boundaries.
Add more trace detail to config.py.
Updates #2661.
The building of 3rd party packages for an RTEMS BSP requires a valid
BSP so the standard method to download the source for releasing does
not work. This change adds support to allow this. The RTEMS BSP support
will not generate an error is no BSP or tools are provided or found.
The change addis logic operators to the %if statement so you can '||'
to 'or' and '&&' to 'and' logic expressions.
A new %log directive has been added to clean up the messages.
A new %{!define ...} has been added to aid checking within logic
expressions.
All command line --with/--without now appear as macros.
Add version.version to get just the RTEMS major and minor version.
Some pkg-config issues have been resolved.
Closes#2655.
If the package references macros yet to be defined an error is
generated. Let the macro expands happen when the package name is
actually used.
Closes#2645.
Add support to release the RSB by adding the VERSION file. The file
is a single line with the version.
Fix the reports to include the version. Update the INI file
support to include the details of the build.
Show the GIT or released version when the command starts.
Closes#2480.
The change fixes installing for RTEMS 3rd Party packages where the
RSB considered them Canadian Cross Compiling (Cxc). Fixing the
Cxc issue broke real Cxc builds. The change corrects the issue of
macros being changed in the Cxc and the prep data not being udpated.
The configuration is loaded again after the updated macros. The
macros are also copied and restored to ensure a clean stable base.
The change also introduces --rtems-tools and --rtems-bsp to align
the command line with the waf configure process or RTEMS application.
File download by http, ftp, pw support checksum. The %hash
directive provides a means of setting a hash used to
checksum the file.
Files on disk or just downloaded are checked.
Generate a separate report of each package being built in a build set.
This creates a better list of faults in the case of nesting build sets
such as */rtems-all.
Remove the numbered source and patches and automatically manage
sources and patches. This removes the overhead in maintaining large
collections of patches.
Python's distutil's copy tree code maintains a cache of directories
created so deleting a tree a different way then coping the same
tree results in an error because the destination folders in the
tree are not present because distutils thinks they exist. The
solution is to implement a copy tree function.
This changes adds support to build the autotools if the host installed
version is not a suitable version. Autoconf and automake have hard coded
references to the install prefix and host tools and this makes it impossible
to relocate, that is use in any path other than the install prefix. To
bootstrap automake you need to first build a suitable autoconf and with that
you can built automake for the install prefix. The other complication is
not referencing the install prefix in the path when building in the RSB.
Having the install prefix in the path can result in strange issues appearing
such as gcc using a new assembler feature not present in an older assember
installed under the install prefix.
The process is to build the autotools using an install prefix to an
internal path inside the RSB temporary path and to use that autoconf
to build the version for the install prefix. The internal install
prefix version is also used to bootstrap RTEMS.
