There was a typo in the patch that added the HAVE_<LIBRARY> definition
that prevented "./waf configure" from succeeding. This adds the missing
character.
Conditionally compiled tests (consisting only of debugger01) were not
compiling as expected when libdebugger was present. This appears to have
occurred during the transition from header detection or due to an
intervening change in the waf internal libraries. The result of
check_cc() is the only location this information is reported, so library
checks now set HAVE_<LIBRARY> as appropriate when the library is found
so existing code for header configuration correctly recognize that a
library is present.
This alters the selection of the 4 Cadence GEM interfaces on the Zynq
Ultrascale+ MPSoC BSP to be provided by config.inc instead of being
provided by options in the RTEMS BSP itself since those options appear
to be dead code when not used in conjunction with LibBSD.
- Do not build a test if a dependency is not enabled.
- Perform a dependency check and generate an error if an enabled module
depends on a disabled module.
Closes#4077
- Provide support for separate user and kernel include paths in
libbsd.py.
- Update all added files with a suitable context to build them
with. Supported contexts are `kernel` and `user`.
- Kernel source use the kernel, CPU, and build header paths in
this order.
- User source use the user, kernel, CPU and build header paths
in this order. The FreeBSD /usr/include tree has some kernel
header files installed as well as user land header files. This
complicates the separation as some kernel header files are not
visible to user land code while other are. This is handled by
appending the kernel header paths to the user header paths so
user land code will include a user header with the same name as
a kernel header over the kernel header but will find a kernel
header if there is no matching user header file.
Closes#4067
- path-mappings allow to fix autogenerated include paths for some corner
cases of target platforms without the need to change the build system
- Currently used for i386 based bsps
In some applications, it's usefull if the files generated by lex or yacc
are not build automatically. With that it is for example possible to
create a wrapper source file that sets some defines before the generated
code is parsed.
The generated file defines a RTEMS_BSD_MODULE_xxx for each enabled
module. That is usefull for conditional compilation depending on whether
a module is build not.
Update #3351.
