Re: [Alephmodular-devel] Re: [M-dev]Panther, PBProjects, XCode and you

[Br'fin <br...@ma...>]

My own suspicion is that if we branch the project file in CVS. Then we 
can do cvs joins from trunk (XCode) to branch (PB-2_0) to copy over 
file additions/minor compiler tweaks while leaving the majority of the 
file intact for each build system.

Look on the bright side, as convoluted as it is, the file is still a 
mergable text file and not something woefully binary which would 
require by hand tweaks for each IDE.

And I give you a 1 compile penalty for inflammatory comments :) (I 
suppose I'd not mind chatting about it in IM, just doesn't seem the 
place here on the lists.)

-Jeremy Parsons

On Thursday, October 23, 2003, at 10:24  AM, wo...@tr... wrote:

> 	Ugh. Would it be possible to make a script that takes a file
> containing the locations of sources, headers, libraries, and creates 
> the
> correct respective PBProject file for? This is twice now Apple has
> capriciously changed the project file format so that old versions can't
> build new projects. I guess it's too much to ask for a little 
> forethought
> when designing a file format that is essentially a glorified makefile, 
> so
> instead the developers have to deal with it each year.
> 	/me crawls back to his cozy GNU cave where they figured out how to
> do it right long ago
>
> Gregory