New source layout.

[Joel Sherrill]

On March 11, 2015 3:44:04 AM CDT, Sebastian Huber <sebastian.huber at embedded-brains.de> wrote:
>
>
>On 09/03/15 18:02, Amar Takhar wrote:
>> On 2015-03-09 14:18 +0100, Sebastian Huber wrote:
>>> >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.
>> This will be changed so it is no longer required.  The real problem
>is that we
>> have to use multiple -I and -B.
>>
>> The waf build does not use -B anywhere yet it works perfectly fine. 
>All I am
>> proposing is unwinding all the include hacks that I added and being
>explicit.
>
>We need at least three -I options, one for the BSP headers, one for the
>
>CPU headers and one for the rest.

What will happen to source modules that are third party? Will we blend their .h with our own? Will this negatively impact the integrity of a source import? 

Will we be losing on the modularilty front?

Sebastian.. You have merged multiple pieces of third party code in the past year. Let's take a couple as examples and walk through the impact on them. Libcrypt? Sha? Jffs2?

--joel