Deployment install location
Deployment install location
- Subject: Deployment install location
- From: Ruediger Hanke <email@hidden>
- Date: Sat, 15 Nov 2003 21:34:06 +0100
Hello,
I'm new to XCode and Mac development in general, as I received my first
Mac (Dual G5) just a month ago. However, I have had lots of experience
with GCC and PowerPC systems before. I hope I don't bother you with
too stupid or obvious questions, but my time is limited and I've been
working
on this for two weekends already & getting nowhere which is all time I
could
have spent on my project.
First thing I wanted to do in XCode was to convert my own "base class"
library to a Mac Framework. I already spent lots of time figuring out
where to
specify which headers are public. Ok, I've found it now :-)
Now I'm stuck. I wanted XCode to put the deployment build into the
Library/Frameworks folder in my home dir. I left the INSTALL_PATH in the
target build settings at its default ($(HOME)/Library/Frameworks) and
checked "Deployment Location" in the "Deployment" build style.
The HOME var is set correctly, but for whatever reason, XCode always
prepends "/tmp/<Project>.dst/" to that path, so the framework ends up
somewhere
in the temp directory. How do I get rid of this? The only "workaround"
that came
to my mind is copy the framework manually after each build.
Another newbie question:
Besides that it may be better for development of a new framework to
first
make it a simple executable and turn it into a framework when everything
is working, what's the benefit of *not* having XCode to copy the
framework
in the install location (default)? When I'm adding the framework folder
from
the build directory to another project using it and it start the
project, it does
always try to load the framework from its install location ... how do
programs
access it there?
Is there a good book answering stuff like that (e.g. what to set the
framework
install path to if I want to make it part of an application bundle)?
I've read
through the Apple docs but I think they're very basic and do not get
very
much in-depth here or I've missed something. What I'm missing is
something
like, I'd like to see something more complex like small "big
application" sample
of an application bundle using both private frameworks and public
frameworks
shared among other applications (but part of the project, not 3rd
party), what
would be the preferred (most convenient?) way to realize this and manage
debug/release builds in XCode and on disk. Eventually, I could probably
figure
it out myself. I'd just rather spend my very very limited time
developing.
Thanks,
Ruediger
_______________________________________________
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.