SOLVED! : WO build queries
SOLVED! : WO build queries
- Subject: SOLVED! : WO build queries
- From: "Sonali Batish" <email@hidden>
- Date: Mon, 18 Aug 2003 23:44:17 -0400
Thanks to all those who posted their comments. Special note of thanks to
Serge who spent some offline time!
I was looking for a solution that allowed me to keep build data separate
from the source code in my project. (since anything else would be solving
the symptom, and not the problem)
I realized this can be done using Project Builder > Preferences > Build
Option wherein you can specify a path (outside the project) for your build
files.
The other solutions suggested were:
1. Having cvsignore include all the build and pb file extensions (Art,
thanks for the comprehensive list)
2. Deleting the build folder from the project before cheking code into the
cvs repository
Thanks again,
-Sonali.
-----Original Message-----
From: email@hidden
[mailto:email@hidden]On Behalf Of Art Isbell
Sent: Monday, August 18, 2003 5:06 PM
To: email@hidden
Subject: Re: WO build queries
On Monday, August 18, 2003, at 03:46 AM, Serge Froment wrote:
> I solve this by leaving the build folder in the project folder and
> instructing CVS to ignore it. This is done by adding the string
> "build" to the "cvsignore" file in CVSROOT. You can easily manager the
> cvsignore file using Sente's CVL (www.sente.ch). CVL is a very nice
> software to use when working with CVS.
> Le lundi, 18 ao{ 2003, ` 06:47 America/Montreal, Sonali Batish a icrit
> :
>
>> Is there a best practise as regards to what should be checked into the
>> cvs repository as a part of the WO project? I noticed that PB creates
>> the
>> build folder within the project and from what little I know, I don't
>> think
>> the build details should be checked into the repository.
CVS is a complex topic. I have added the following bookmarks to help
me with CVS:
file:///Developer/Documentation/DeveloperTools/cvs/cvs_toc.html
http://developer.apple.com/internet/macosx/cvsoverview.html
CVS has a feature called wrappers. This allows one to treat file
packages (e.g., *.emodeld, *.wo) as single files by tar'ing and
gzip'ing them prior to CVS checkin. I suggest avoiding this feature.
You cannot examine the differences between versions of wrappers and
they don't work correctly with some CVS features. The OS X developer
tools contains a sample cvswrappers file, /Developer/Tools/cvswrappers.
I would comment out all entries in the "Wrapped files" and "Wrapped
directories" sections. The only wrapped file that will affect normal
WO projects is *.emodeld. If you develop Java Client apps using WO,
*.nib should not be wrapped. *.nib file packages do contain a binary
file which I would add to the "Binary files" section.
In your cvsignore file, I would also add "*.pbxuser", ".DS_Store", and
PBUserInfo*. *.pbxuser and PBUserInfo* are Project Builder and
ProjectBuilderWO (the Windows ProjectBuilder), respectively, project
files that contain user-specific project information which I don't
check into CVS. But the remaining project files are necessary if you
want to be able to check out a valid Project Builder project.
Project Builder's CVS integration is far from complete. For this
reason, I use CVL as Serge mentioned above. Its CVS integration is far
more complete although you will still need to invoke a few CVS
operations from its command-line interface.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.