Re: Fixing module-specific, public include/*.h file inclusion on trunk

On Fri, Dec 16, 2016 at 1:22 PM, William A Rowe Jr wrote: > On Fri, Dec 16, 2016 at 12:57 PM, William A Rowe Jr > wrote: >> >> So today's primary bogus result is courtesy of is due to leaving >> public headers hiding in modules/class/*.h paths for our

Re: Fixing module-specific, public include/*.h file inclusion on trunk

On Fri, Dec 16, 2016 at 12:57 PM, William A Rowe Jr wrote: > So today's primary bogus result is courtesy of is due to leaving > public headers hiding in modules/class/*.h paths for our builds. > > I'd suggest one of two approaches, pick a favorite solution? > > [ ] Have

Fixing module-specific, public include/*.h file inclusion on trunk

So today's primary bogus result is courtesy of is due to leaving public headers hiding in modules/class/*.h paths for our builds. I'd suggest one of two approaches, pick a favorite solution? [ ] Have the top level build copy all modules/*/mod_*.h definitions to the build tree include/