alephmodular-devel

[Alephmodular-devel] Panther, PBProjects, XCode and you

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

With the release of Panther real soon now, I expect myself and those 
developers who haven't already upgraded to pick up the new OS and use 
new development tools.

At this point we will be updating our compiler tools from 
ProjectBuilder to XCode. Alexander can correct me, but I presume it 
uses an updated version of the .pbproj's that we use. If so, the most 
likely outcome is that the PBProject files will be branched with a 
PB-2_0 tag on the last version of the project file that supports 
ProjectBuilder and then the file will be updated for XCode along the 
main trunk.

I admit I'm still marshaling my funds so may not update immediately. 
But I'd like to make sure we're all on the same page on this issue.

-Jeremy Parsons
http://alephmodular.sourceforge.net/

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

[Alexander S. <ast...@it...>]

On Oct 22, 2003, at 2:50 AM, Br'fin wrote:

> With the release of Panther real soon now, I expect myself and those 
> developers who haven't already upgraded to pick up the new OS and use 
> new development tools.
>
> At this point we will be updating our compiler tools from 
> ProjectBuilder to XCode. Alexander can correct me, but I presume it 
> uses an updated version of the .pbproj's that we use. If so, the most 
> likely outcome is that the PBProject files will be branched with a 
> PB-2_0 tag on the last version of the project file that supports 
> ProjectBuilder and then the file will be updated for XCode along the 
> main trunk.
>

Yes, XCode upgrades the Project Builder project; I've been holding off 
on commiting it so as not to break all of yours.

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

[<wo...@tr...>]

	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

On Thu, 23 Oct 2003, Alexander Strange wrote:

> 
> On Oct 22, 2003, at 2:50 AM, Br'fin wrote:
> 
> > With the release of Panther real soon now, I expect myself and those 
> > developers who haven't already upgraded to pick up the new OS and use 
> > new development tools.
> >
> > At this point we will be updating our compiler tools from 
> > ProjectBuilder to XCode. Alexander can correct me, but I presume it 
> > uses an updated version of the .pbproj's that we use. If so, the most 
> > likely outcome is that the PBProject files will be branched with a 
> > PB-2_0 tag on the last version of the project file that supports 
> > ProjectBuilder and then the file will be updated for XCode along the 
> > main trunk.
> >
> 
> Yes, XCode upgrades the Project Builder project; I've been holding off 
> on commiting it so as not to break all of yours.
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by OSDN developer relations
> Here's your chance to show off your extensive product knowledge
> We want to know what you know. Tell us and you have a chance to win $100
> http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
> _______________________________________________
> Marathon-devel mailing list
> Mar...@li...
> https://lists.sourceforge.net/lists/listinfo/marathon-devel
> 

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

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

[Gregory S. <wo...@tr...>]

	Heheh, wow that was inflammatory. Teaches me to post from work. I'll 
roll a 1d20 for my compile penalty

On Thursday, October 23, 2003, at 05:29  PM, Br'fin wrote:

> 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
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The SF.net Donation Program.
> Do you like what SourceForge.net is doing for the Open
> Source Community?  Make a contribution, and help us add new
> features and functionality. Click here: http://sourceforge.net/donate/
> _______________________________________________
> Marathon-devel mailing list
> Mar...@li...
> https://lists.sourceforge.net/lists/listinfo/marathon-devel

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

[Alexander S. <ast...@it...>]

On Oct 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

You can open newer projects with an old PB, it just spits up errors and 
causes unnecessary commit noise.

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

[Timothy C. <da...@ma...>]

> With the release of Panther real soon now, I expect myself and those 
> developers who haven't already upgraded to pick up the new OS and use 
> new development tools.
>
> At this point we will be updating our compiler tools from 
> ProjectBuilder to XCode. Alexander can correct me, but I presume it 
> uses an updated version of the .pbproj's that we use. If so, the most 
> likely outcome is that the PBProject files will be branched with a 
> PB-2_0 tag on the last version of the project file that supports 
> ProjectBuilder and then the file will be updated for XCode along the 
> main trunk.
>
> I admit I'm still marshaling my funds so may not update immediately. 
> But I'd like to make sure we're all on the same page on this issue.

Speaking as someone with the GM build installed and running since last 
Friday, when the seed went out to ADC Seed Program members, I can 
confirm that the .pbproj will be a new format.  Also, projects compiled 
under XCode may not work under previous versions; however, there is an 
install option with XCode for cross-compiling support (only for 
previous OS X versions, unfortunately :-\ ).  So be sure to check that 
under Custom when installing XCode!

Timothy Collett

Three things are certain:
Death, taxes, and lost data.
Guess which has occurred.
~haiku~