On 24.01.2011 22:49, James Turner wrote:
>> Perhaps another approach would be to do out-of-source builds. I think
>> automake/conf should support that, although it's been a while since I've
>> tried it.
> Cmake is very good at out-of-source builds :)
Hmm. The out-of-source builds alone don't really help with switching
branches. Changing branches back and forth still results in all
differing sources getting new timestamps. So the next "make" triggers a
rebuild of all affected sources/objects anyway. "make" isn't smart
enough to notice that the older object files were generated from (older)
sources, which had identical content to the current ("newer") sources.
So it's all the same if you maintained one or two sets of objects.
You'll also need to keep git from touching any _sources_, so maintain
two sets of matching sources and their objects. Using two completely
separate repos helps - or the "magic" feature to create two separate
source checkouts from one repository, which James mentioned.
Could some git guru (git-goroo? ;) ) enlighten me, on how I can create
two checkouts from one repo? That would actually be very useful -
especially now that fgdata is branched. I don't want to pull another
fgdata repo... and I don't feel brave enough to switch fgdata branches,
since its release branch is already stripped (=> switching affects
thousands of files...).
cheers,
Thorsten
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
