Re: A couple more possible bugs
Re: A couple more possible bugs
- Subject: Re: A couple more possible bugs
- From: Scott Tooker <email@hidden>
- Date: Sat, 1 Nov 2003 10:45:36 -0800
On Nov 1, 2003, at 10:07 AM, Brian Barnes wrote:
> 1) Double-clicking the project name also opens the first source file,
> not the inspector
A known bug that is fixed in internal builds.
> 2) Get Info and Show Inspector *always* seem to do the same thing for
> every item in the groups and files
What do you mean by "the same thing". These menu items are designed to
be similar to the Finder's implementation of the same menu items. 'Get
Info' brings up a normal window focused on the selection, and doesn't
track selection changes. 'Show Inspector' brings up a floating utility
window that tracks selection changes.
> 3) When doing get Info on the project, and changing the "place build
> products in:" unnecessarily changes the "place intermediate build
> files in". I want those to stay the same, and I have to re-edit them
My guess is that you have "place intermediate build files in" set to
"Build products location" instead of "Separate location".
>
> Quick question: For the "place build products in" and "place
> intermediate build files", the paths are complete; is there a path
> variable that I can use to say "current project folder?" I want to
> pass out some of the code, and this will just serve to confuse people.
>
> For instance, some of my static libraries I want to intermediate files
> to go into the build folder, but the file libXXX.a file to go into a
> common folder that is one folder up, but not locked to my user name.
> So instead of:
>
> /users/bbarnes/code/dim3Common/Libraries
> /users/bbarnes/code/dim3BitmapUtility/build
>
> I could do:
>
> <current project>/../dim3Common/Libraries
> <current project>/build
>
> If that's not there, mark this as a feature request :)
One thing you could try is to define a 'source tree' path in the Source
Tree preference pane. Then use the 'Setting Name' for the source tree
in the path, like so:
Add a Source tree like 'CommonLibraries' and then in your path put
${CommonLibraries}
and use the SRCROOT variable to refer to the project directory
${SRCROOT}/build
If this doesn't work please file a bug on the part that doesn't work.
Note: for the 'Source Tree' each person needs to add the same source
tree and set their path to it's location on their disk.
Scott
>
> Repeating from before, I really like the new XCode. If I had a minor
> complaint, it would be that there seems way to many places to set the
> same thing :) But, that's what power is about ...
>
> [>] Brian
> _______________________________________________
> xcode-users mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/xcode-users
> Do not post admin requests to the list. They will be ignored.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.