rtems-source-builder - RTEMS tools and packages source builder.

	Commit message (Collapse)	Author	Files	Lines
2019-09-19	rtems/automake: Remove patch as it has moved to bare/devel.	Chris Johns	1	-6/+0

2017-11-10	5: Use ticket attachment for automake patch	Sebastian Huber	1	-1/+1
	Update #2616.
2017-10-12	4.12: Update all MD5 hashes to SHA256.	Chris Johns	1	-1/+1
	Closes #2536.
2016-02-29	config: Patch automake-1.12.6 to remove warning on newer perl versions.	Chris Johns	1	-0/+6
	Closes #2616.
2015-07-20	Canandian Cross Compiling and RTEMS 3rd party package building Fixes.	Chris Johns	1	-0/+4
	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.
2014-08-19	rtems: Remove the duplicate hashes from the config.	Chris Johns	1	-2/+0

2014-07-29	Add checksum support for downloaded files.	Chris Johns	1	-0/+2
	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.
2013-07-16	Automtically build the Autotools to bootstrap RTEMS.	Chris Johns	1	-0/+19
	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.