GYP debugger? On Mon, Sep 28, 2009 at 2:00 PM, Nick Carter <[email protected]> wrote: > I've noticed that the use of the 'direct_dependent_settings' in gyp to > propagate #defines and include paths makes it trickier to decipher the > actual build-order dependencies. I've had cases where I needed to add a gyp > dependency just to get an #include path for a header file that was > transitively included by a bona-fide dependent. The pollution obscures the > actual dependency structure. > A transitive version of 'direct_dependent_settings' that works on indirect > dependencies might improve the situation. Another possibility is a > lightweight 'mix-in' target type that has no .vcproj associated with it, but > that can still impart the side effect of 'direct_dependent_settings' on its > dependents. > > - nick > > On Sun, Sep 27, 2009 at 6:13 PM, Peter Kasting <[email protected]> wrote: >> >> Thanks Mark-Antoine. >> It has been a very long time since I fixed the dependencies years ago to >> not be so crazy. Not surprising that it is once again goofed up. >> It would be nice to have some of this stuff auto-calculated by GYP if that >> is feasible... >> PK >> >> > >
--~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
