| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Close #3292
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Updates #2655.
|
| |
|
|
| |
Updates #2655.
|
| |
|
|
| |
Updates #2655.
|
| |
|
|
|
|
|
|
| |
Add support for pkgconfig checks to fail when just downloading the
source so it is actually downloaded on hosts that may have a package
installed.
Updates #2657.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Fix Windows support to allow MSYS2 Python to be used.
Updates #2619.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
Add support for simulator options to enable special features of
some gdb simulators.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the 'opt' from various macros and shell variables.
Add pkgconfig to the checks to make it clear the check is a
pkgconfig check.
Add NTP support as the first package to be built using the RSB.
Split the RTEMS URL's out from the base bset file into a separate
file that be included by other files.
Add an RTEMS BSP configuration file to help abstract the process
of building 3rd party packages.
Clean the cross and canadian cross support up so we can cleanly support
cross and canadian cross building.
Refactor the pkgconfig support and clean up the PC file handling of
loading modules.
Add support for %{?..} to return false if a macro is %{nil}.
Add %{pkgconfig ..} support to allow better control of access RTEMS
pkgconfig files.
|
| |
|
|
|
|
| |
Remove the numbered source and patches and automatically manage
sources and patches. This removes the overhead in maintaining large
collections of patches.
|
| |
|
|
|
|
|
|
|
|
| |
Hack round the FreeBSD iconv support in Freebsd 10. In 10 libc now
supports iconv however iconv.h is present under /usr/local.
Start to add support to build qemu for MinGW via a Cxc. This is a
work in progress and contains lots of hidden traps.
In config.py separate out of the canadian build status.
|
| |
|
|
|
| |
Add the extra actions: ccflags, cflags, ldflags and libs to allow the
fetching of these from pkg-config files.
|
| |
|
|
|
|
|
| |
Add a pkg-config look alike command so packages that use pkg-config can
build if pkg-config is not present on a host.
Add support to query package config from configuration scripts.
|
| | |
|
| |
|
|
|
|
| |
Nesting if statements did not correctly process the contents of
the nested if script. This change makes the processing uniform
across all the logic stages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
Fix paths that need to be coverted to host format.
The shell expansion needs to invoke a shell on Windows as cmd.exe
will not work.
Munch the paths into smaller sizes for Windows due to the limited
path size.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
User macro files passed on the command line allow a user to
override the defaults in configuration files to test new changes
in pending releases.
Fix macros issues with keys with more than one map.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Package descritions and info and now always added to macros.
Hack to get the source in macros into the source this. This needs
to move to the package class and will soon.
Fix a bug where the old defines was still referenced.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To support building snapshots and pre-release source the defaults
has been refactored. The defaults have been moved to a stand alone
file and a macros.py module added. This modile abstracts the
old default dictionary turning it into a class. The macros
class can load macros from a file therefore the defaults have
been moved to a stand alone file.
The use of defaults has been removed from the project. The only
case where it is used in the options where the defaults are read
from a file. Macros are used everywhere now.
The defaults.py has been moved to the option.py and the separate
options and defaults values has been moved to a new pattern. When
constructing an object that needs macros and options if the macros
passed in is None the defaults from the options are used. This makes
it clear when the defaults are being used or when a modified set of
macros is being used.
The macros class support maps. The default is 'global' and where all
the defaults reside and where configuratiion file changes end up.
Maps allow macros to be read from a file and override the values
being maintained in the 'global' map. Reading a macro first checks
the map and if not present checks the 'global' map.
The addition of maps to the macros provides the base to support
snapshots and pre-release testing with standard configurations.
This functionality needs to be added. It works by letting to
specify a snapshot with:
source0: none, override, 'my-dist.tar.bz2'
and it will be used rather the value from the standard configuration.
With a build set you need to also specify the package these macros
are for. The maps provide this.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support to build MinGW tools using Cygwin. This is a Canadian cross
build.
Do not expand the directives when parsing a configuration file. Hold
in the package object the text as read from the configuration file. Still
parse the logic but leave the macros. This allows a configuration to be
varied when the build happens. The Canadian cross uses this to build a
build compiler used to build a Cxc runtime.
Add Cxc support to the build module. In the defaults add rm and rmfile
macros, add Cxc paths and pre-build script code.
In the setbuilder check for a Cxc build and if so and the package
allow Cxc build the build host version then the host target
version.
Add cygiwn support to the defaults processing and to the Windows module.
|
| | |
|
| | |
|
| |
|
|
|
| |
Analysis of the current script shows a number of updates are happening
and this should be the default.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Add URL and summary to the info helpers. Fix the package get_info and
allow infos to be appended to. This lets a summary be on more than
one line.
Fix the %{?} expansion logic so %{?macro} expands to the macro if it
exists.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The RPM spec file will return value for %{?macro:value} if the
macro is defined. This means you need to:
%if %something
%define macro 1
%else
%undefine macro
%endif
which means you have to have more complex tests to check for the macro
and its value. Therefore we support defined as true and defined and
0 as false.
|
| |
|
|
|
|
|
| |
Building on Windows showed the --enable-plugin was being set yet
it was disabled. The code was just checking if the macro was defined
and not actually testing the value. The value is now being tested
and it needs to be true to succeed.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add arch build files. This allows archs to have different versions
and patches for specific tools.
Break the RTEMS config directory up into separate directories to
make long term maintenance easier. This required a change to config.py
to handle the config files being in subdirs of the config directory.
The defaults have been updated to include the install SB root so
packages built before a package are available.
Add makeinfo to the required tools. GDB (and others) need it to
build without error.
|
| |
|
