| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This helps to avoid issues with user names which contain space
characters.
Close #3830.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
| | |
|
| |
|
|
| |
Closes #3769
|
| |
|
|
|
|
| |
- Staging lets build sets use previously built build sets.
- Fix the rtems-bsp builds to support staging.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- 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.
|
| |
|
|
| |
FTP is an outdated protocol and blocked by some firewalls.
|
| |
|
|
| |
Closes #3562.
|
| |
|
|
|
|
|
|
| |
The command python has been removed from upstream python and python2
and python3 is now used. This patch wraps the commands in a shell
script that locates a suitable python to run.
Updates #3537
|
| |
|
|
|
|
|
|
|
|
|
| |
In order to build a tool chain with Ada support a native GCC with Ada
support of the same version as the cross compiler is required. The RSB
used hard coded paths for the gcc and g++ programs. This forced the RSB
user to change the main GCC installation of the machine to build a
particular RTEMS tool chain. This is undesired/infeasible in most
situations.
Close #3284.
|
| |
|
|
|
|
| |
- Fix a minor bug in the to addr processing.
Update #3210
|
| |
|
|
|
|
|
|
|
|
| |
The support is added at the top level and so not lost when we
move to a new version of RTEMS.
The change also moves all 3rd party packages to use a common
rtems-package.bset build set file.
All packages except Microwindows itself build cleanly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The default without the option is to prepend the release URL to the URL
list to download from the RTEMS FTP site first if the RSB is released. This
option can force the RTEMS FTP to be tried first when not a release,
or you can supply a different URL to download from or you can request
no RTEMS URL is tried first. Eg:
--with-release-url
--with-release-url=file://opt/local/cache
--without-release-url
Move the RTEMS release URL to the default.mc file. Change the URL
to the RTEMS FTP server and do not use the https method of access.
The option's with_arg call was cleaned up to make sense.
Remove the log's raw output of an extra space.
Some download error message formating was cleaned up.
Closes #2636.
|
| | |
|
| |
|
|
| |
Add a --without-error-reports flags to reduce the noise on --with-downloading.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
The ARM on 4.9.0 with clang fails and needs an extra option and
this is only valid building the build cross compiler. This change
fxies the host and build flags so they only apply where needed.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
Qemu requires gettext, glib, libffi, and pixman. DTC is built
as a submodule.
On Mavrick provide a pkg-config command so avoid needing a pkgconfig.
The one here is only just good enough to work.
Provide an internal autotools build including libtool so qemu can
be built from git.
|
| |
|
|
|
| |
If doing a Cxc add the ld flags to the CC to allow the expat to
build. This broke with the change to support clang on Mavrick.
|
| |
|
|
|
|
| |
The clang compiler on MacOS 10.9 (Maverick) generated a warning when
LDFLAGS where passed on the command line. This change lets the RSB
build RTEMS GCC tools on a clean Maverick install.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Set up the rules to manage the separate host and build setting to
allow a Canadian cross to complete.
Update the scripts to move the build directory and host/build
flags into the defaults so they are common for all build
configurations.
|
| |
|
|
|
|
|
|
|
| |
Rework the RTEMS build set files to point to the new location.
Move the files into devel, this follows the ports naming in
FreeBSD.
Update the macros, defaults, and options to support this.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is used in the configuration scripts to specify which
libraries you want to be linked as static. For gdb this is
libexpat which is built as part of most build sets.
|
|
|
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.
|
