On 2015-03-12 08:01 -0500, Joel Sherrill wrote: > 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?
Yes, their public APIs will become part of our own. If we take ownership we will be able to properly document the APIs which currently gets ignored. It's more work to maintain however it is extremely beneficial to shipping RTEMS as 'one package'. We also need to test these packages within our own test suite this makes it easier. > Will we be losing on the modularilty front? No, the goal here is to make RTEMS more modular. We lose by hiding headers where we can't see them. There is so much interdependence within RTEMS this is why we have to use -link-start / link-end hacks in the linker. The goal is to eventually remove the requirement for this hack as it can hide issues. This is a long term goal. > 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? That is a great idea. Amar. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
