Re: Namespacing of Zephyr headers and API

Paul Sokolovsky

Hello David,

On Sun, 2 Apr 2017 10:14:48 -0600
David Brown <> wrote:

On Sat, Apr 01, 2017 at 12:44:43PM +0300, Paul Sokolovsky wrote:

specific proposal, I'd say it's not yet too late to move all headers
under zephyr/, while providing compatibility symlinks for couple of
versions (until interested parties will settle with Windows builds,
where symlinks likely won't be supported).
Interestingly, Windows has supported symlinks for quite some time
(Windows Vista),
I believe some form of symlinks was available since 2000 (junctions, or
how was it called), and in XP was quite usable already. But there's
difference between systems support and ecosystem support: would normal
copy operation in command line and GUI shells work with them? 3rd-party
shells? archivers and similar tools?


But, I agree, if we want to support Windows, we probably shouldn't use

Can this be handled by just adding the other path with a -I option?
D'oh, indeed, if we just move everything consistently under zephyr/,
without further restructurings or renamings, that will work! So,
there's a pretty good migration path, and maybe we should really
consider resolving the header namespacing issue.


Best Regards,
Paul | Open source software for ARM SoCs
Follow Linaro:!/linaroorg -

Join to automatically receive all group messages.