On Fri, Feb 3, 2012 at 3:27 PM, Lukasz Mach <[email protected]> wrote:
> (03.02.2012 22:14), C Anthony Risinger wrote:
>> On Fri, Feb 3, 2012 at 2:38 PM, Rob Peters<[email protected]>  
>> wrote:
>>> Okay, I tried these suggestions, and here are the results...
>> try cleaning the git directory (`git status` should show nothing at
>> all) and using the `--no-compile-inplace` switch ... there is a stupid
>> issue where cache files get reused even when build opts change, and
>> there is no simple way to remove them without accidentally deleting
>> necessary JS files.
>>
>> i would recommend using `--no-compile-inplace` indefinitely until
>> noted otherwise.  this will force a full rebuild each time (a whopping
>> 10 seconds at most on my laptop)
>
> I use --no-compile-inplace all the time, and I don't have full rebuild
> each time. Only changed modules.

hmm, maybe my scripts do that manually then.

either way, `--no-compile-inplace` puts all the libs in one spot so
they are easy to remove if necessary (without a nuclear `git clean
-fdx` blasting away your files)

-- 

C Anthony

Reply via email to