Re: Adding Frameworks Not Installed in /System/Library/Frameworks
Re: Adding Frameworks Not Installed in /System/Library/Frameworks
- Subject: Re: Adding Frameworks Not Installed in /System/Library/Frameworks
- From: "Alain Ciphat" <email@hidden>
- Date: Thu, 25 Oct 2007 10:56:15 -0400
Hi Kyle,
Thanks. I believe this is the issue. I did build the library myself
using the library's makefiles, which are generated by GNU autotools. I
have no idea how the frameworks are packaged; I would have to rebuild
the library and/or investigate the makefiles. Therefore, my guess is
that the headers were not set as "Public" in this process.
This may be a dumb question, but is there a way to reset the role of
the headers as "Public" after they have been packaged in the
framework? A related question is: what is the mechanism that convey
this information (i.e., is it in some meta-file within the framework)?
Thanks for your help and also Marjus Hitter's reply.
Alain
On 10/25/07, Kyle Sluder <email@hidden> wrote:
> Did you build the library yourself, or did you download some sort of
> installer package? If you built it yourself using Xcode, make sure
> you set the role of the headers as "Public" in Xcode.
>
> --Kyle Sluder
>
> On 10/25/07, Alain Ciphat <email@hidden> wrote:
> > Hello,
> >
> > I'm a newbie to Xcode. I'm using Xcode 2.4.1 on a PPC (G4) Mac. I have
> > a problem when adding a framework to a Carbon Application project that
> > is not installed in /System/Library/Frameworks (i.e., some open source
> > framework that I just downloaded and installed somewhere else). My
> > problem is that adding such a framework does not seem to add the path
> > to the framework's header files to the compile command line (i.e.,
> > there is no -I/path-to/my-framework's/header-files in the compile
> > command line displayed in the build transcript window when I build).
> > Consequently, compilation fails to find the header files for the
> > framework. The procedure I followed to add the framework is as
> > follows:
> >
> > 1) Right-clicking on the "External Frameworks and Libraries" node in
> > the project's file tree and selecting Add | Existing Frameworks...
> > 2) Select the framework from the file selection dialog.
> > 3) I left the Reference Type to default.
> > 4) I made sure that the add to target box is checked.
> >
> > Now, I can edit the active target and set the Header Search Paths
> > property under the build tab to add the necessary directories (and
> > possibly also the Framework Search Paths property), but I would think
> > that such a fine IDE would not require such arcane actions :) BTW, I
> > have noticed that for frameworks that are installed in
> > /System/Library/Frameworks the above procedure works fine even though
> > the explicit include path is not in the compile command line. I'm
> > assuming that /System/Library/Frameworks is somehow in a default
> > search path defined somewhere.
> >
> > Please, if someone can tell me what I'm missing here, I would greatly
> > appreciate it. Better yet, if someone can explain the details of what
> > happens behind the scenes when adding frameworks so that an old unix
> > makefile guy like me can understand it, that will really make my day.
> > Although the latter may be asking too much.
> >
> > Thanks in Advance,
> >
> > Alain
> > _______________________________________________
> > 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
> >
>
_______________________________________________
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