• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to handle link dependencies under Xcode vs. MS Visual C++
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to handle link dependencies under Xcode vs. MS Visual C++


  • Subject: Re: How to handle link dependencies under Xcode vs. MS Visual C++
  • From: email@hidden
  • Date: Thu, 23 Jun 2005 19:06:51 +0200
  • Importance: High


jump-ING <email@hidden> wrote on 06/23/2005 04:47:39 PM:

>
> Am 23.06.2005 um 15:45 schrieb email@hidden:
>
> > I had some .dll on windows, that I tried to compile and link  
> > to .bundles under MAC.
>
> You're probably talking about .dylibs on Mac OS X?
>
>
> > The linker than makes errors for double definitions when I link the  
> > final application file.
>
> Then you include some symbols or entire libraries twice. This makes  
> no sense and won't work.
>
> > What are convient options for the linking ?
>
> Start a new project of the correct type and they should be already  
> set. A design using Frameworks is preferred on Mac OS X.
>
> > What are the corresponding Linker parameters in Xcode to tell the  
> > linker the depencies ?
>
> Add the library/Framework like a source file to your project. The  
> build mechanism will pick it up.
>
> > In Xcode I use Direct Dependencies in the General Tab in the Target  
> > Info of my targets to add dependencies.
>
> This is a build dependency. You probably want to add parts of the  
> results of the dependent build to your project as well. Again,  
> similar to how you add a source file.
>
> If you want to deploy your app for drag & drop installation (this is  
> how Mac users expect it), read up Xcode's documentation for "embedded  
> frameworks". There's a nice step by step description.
>
> > As the file is generated everytime, I do not know how to influence  
> > this.
>
> When adding an item to the project's file list, you actually add a  
> file reference. Make sure it references the just built file, not a  
> copy of it. If the file temporarily goes away while you rebuilt the  
> dependency, this doesn't matter.
>
>
> Cheers,
> Markus
>
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. Markus Hitter
> http://www.jump-ing.de/
>
>
>
>
>

Thanks for your prompt answer.

I tried what you described in the email. So I did a new project for one of my .dylib as a .framework and then I tried using the add Files ... menu to add the .framework into my project.

But I could not do so, it was greyed out ? By the way it was the same for my .dylib file. Does this mean, they are already part of my project, so I cannot add them again ?

But how do I explain that I need for my final application the .dylib of .framework to be included ?

Regards

Jürgen Jäger
________________________________
mail: 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

  • Prev by Date: Re: Xcode-users Digest, Vol 2, Issue 302
  • Next by Date: Re:The Mac XCode 2 Book now available
  • Previous by thread: Re: How to handle link dependencies under Xcode vs. MS Visual C++
  • Next by thread: How to conditionally run a script based on build configuration
  • Index(es):
    • Date
    • Thread