I wasn't really trying to relay the explicits since there are a few. :) And example is the generate_localizer action on the 'browser' target in the chrome project. It has all it's inputs/outputs, and it runs when needed. But the source file that includes it's output, doesn't always recompile when the header is regenerated, it can take a second build to have the file compiled.
TVL On Tue, Sep 22, 2009 at 1:12 PM, Eric Seidel <[email protected]> wrote: > I'm not sure I understand what you're saying. I assume you're aware > that script phases in XCode list explicit dependencies. > > I think I'd have an easier time parsing your paragraph with specific > examples. > > -eric > > On Tue, Sep 22, 2009 at 5:30 AM, Thomas Van Lenten > <[email protected]> wrote: > > I've confirmed this with Xcode 3.2; but my suspicion is it also happens > with > > Xcode 3.1.x, just less frequently. > > In our build process, we run scripts in a few places to generate headers. > > Those steps are usually done via Actions on targets. We have listed all > of > > the outputs generated so the tool chains can properly track the > dependencies > > and figure out what needs to be rebuilt. It appears that Xcode has some > > bugs in this space. So it's possible to make changes to the input for > one > > of these scripts (say a GRD files), and on your next build, the script > will > > run to generate the new header, but Xcode appears to be checking the > header > > before the script has run, so it doesn't always rebuild all the sources > that > > include the headers. Most of the time, on the next build, the compiles > will > > happen and your build will be back in a good state. So far my attempts > to > > create a small test case have failed (the exact same setup, just will all > > the other sources removed, suddenly works). > > So if you are working on GRDs or localized XIB; and see odds issues with > > strings, you might have gotten bitten by this, a rebuild should fix it. > > Failing that, go for a clean build before spending too much time > debugging > > just to make sure you aren't fighting the tool chain. > > TVL > > ps-this doesn't seem to be an issue with us missing dependencies for > build > > order, this happens within a single target. I can get it to happen on a > 4 > > core box, so it is not something that only shows with > more parallelization. > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
