On 09/03/15 02:42, Amar Takhar wrote:
> >include/arch/ - Private architecture specific
> >include/bsp/ - Common BSP files
> >include/bsp/<arch> - Architecture specific
>
>Does this mean all <arch> references are explicit and not using compiler
>include path tricks ?
Yes, 100% of include paths are explicit, no compiler tricks at all the only
include will be -Iinclude and nothing more.
This is actually a big problem and will break a lot of thinks. Currently
you use
#include <bsp.h>
and get for example RTEMS_BSP_NETWORK_DRIVER_ATTACH for the network
configuration.
You find the <bsp.h> via the -B compiler switch.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
