• 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
using a CW compiled Mach-O static lib in a XCode Project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

using a CW compiled Mach-O static lib in a XCode Project


  • Subject: using a CW compiled Mach-O static lib in a XCode Project
  • From: "Stefan Csomor" <email@hidden>
  • Date: Thu, 3 Feb 2005 07:48:19 +0100

Hi

sorry if I'm not seeing the obvious, but I have a problem :

- I've converted a project which includes some libraries (for which I don't
have Source Code access to) to Xcode using the Converter

- the used libs show up nicely in the tree, have correct (=the same as .a
libs) symbol

- but they are not linked into the executable

- reading the docs, I thought maybe a simple rename to lib*.a will help, but
then I get a linker complaint about an incorrect magic number

Thanks for any pointers

Stefan

 _______________________________________________
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: How to put files in app bundle?
  • Next by Date: Re: Distributed build overhead and Mac Mini vs XServe pricing
  • Previous by thread: Re: XcodeBootCamp script
  • Next by thread: Re: Distributed build overhead and Mac Mini vs XServe pricing
  • Index(es):
    • Date
    • Thread