On 2018-06-12 23:34, Olivier Hainque wrote: > > >> On 12 Jun 2018, at 23:12, Jeff Law <l...@redhat.com> wrote: >> >> I'm going to defer to Olivier on all 6 parts of this kit. He knows >> vxworks far better than I. > > No pb. I haven't forgotten about this :) > > As I mentioned on another > thread, exceptions on VxWorks is an intricate nest of > multiple parameters when you consider the possible variations > of kinds of modules you can make (RTP, DKMs, SKMs) combined > with different lines of VxWorks versions (6.7 introduced support > for dwarf eh for example), combined with the various context > in which a toolchain may be used (straight from a command line > or driven by the WindRiver IDEs). > > This include path part alone looks sensible. I'd still like to > evaluate how it fares in a environment where many of there variations > are exercised, and I'm not quite done with this yet.
Thanks, I do hope for careful scrutiny. As I said, I'm only working on a VxWorks 5.5 powerpc target, and I obviously don't want to break stuff for other settings, but I can't really test on other combinations than the one I have. I try to break up the changes in small pieces, maybe even smaller than one would usually do, to hopefully get the uncontroversial parts upstream, and then we may just have to maintain some patches in-house if there's no reasonable way to make it work for everybody. Rasmus
