On Thu, May 14, 2009 at 9:54 AM, Steven Knight <[email protected]> wrote: > We're getting closer to the final (?) conversion of chrome.sln on Windows to > GYP. While that work's getting finished, we want to make sure how we want > everyone to use GYP is adequately documented. > > This will be structured as a set of how-to examples for the common tasks > that cover, say, 90% of what a typical developers needs from the build. > (I'm sure everyone is familiar with the counter-example: having nothing but > an exhaustive language reference manual that leaves you scratching your > head, searching for the right feature and how to apply it...) > > Here's a quick list of relatively obvious topics that we're already planning > to cover in the how-to doc: > > Add new source files > Add a new library > Add a new executable > Add new compile/link settings > Exclude some compile/link settings on a specific platform > Move files between targets (refactoring) > Compiling against header files from a different target > Adding a new include directory > Linking against another target library > "Dragging in" library B that library A uses, whenever an executable links > with library A > Adding a custom build step > Adding a rule for handling files with a different suffix > Adding a new variable to let the user configure a differently-flavored build > at gyp time > > What's missing from the above list? Let me know so we can (over time) > arrive at something that's reasonably complete.
It looks pretty good to me. One question that comes up is "why is file [foo] getting built (or not built)?" Similarly with mystery include paths, or libs, etc. Maybe some tips on diagnosing common errors would help. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
