Question about static libraries...
Question about static libraries...
- Subject: Question about static libraries...
- From: Chas Spillar <email@hidden>
- Date: Mon, 24 Jul 2006 11:42:47 -0700
- Thread-topic: Question about static libraries...
Hello,
So, I have a set of code that I would like to share within my own code.
Additionally, I have the requirement to give this code to a developer
outside my company.
Heretofore, I have just copied the set of 10-20 files into each target that
needs this capability. Now that I have a need to give it to an external
developer, I can't give the sources out, I need another solution.
I am aware of frameworks, but would prefer to avoid using one in this case
as I prefer to keep this code relatively opaque (that is I prefer for myself
and the other developer to directly compile it into our code).
In Mac OS 9 / MPW, there was the concept of a "static library". By which I
was able to collect a group of sources into a "library" and the library was
statically bound at compile time. That is the library was not needed after
compile time.
I have created a "static library" target in XCode and included this target
in my other target which needs the use of the code. However, I am getting
undefined symbols for the various defined symbols in the static library when
building.
So, my questions are:
1) Do static libraries on MacOS X work like they did in MacOS 9, that is
resolved completely at compile time?
2) What is preferred solution to this problem? As I said, I would prefer to
not build a framework as that would enable others to use this capability,
which I wish to avoid.
Thank you,
Chas.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden