• 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: CW .a files
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CW .a files


  • Subject: Re: CW .a files
  • From: Godfrey DiGiorgi <email@hidden>
  • Date: Wed, 19 Nov 2003 17:05:51 -0800

Mark,

Let me be certain I understand correctly:

- eSellerate is providing you with a library that you need to link into your application.
- The library generated by the CodeWarrior Mach-O tools.


If this is the case, presumably the CodeWarrior Mach-O tools should be producing a well-formed Mach-O library that ld is able to link. No conversion should be necessary, you should be able to include it in your project's build process, specify any link parameters required, and be done. On the other hand, if the library is not well-formed, it should emit link errors.

Testing has been done in the past that indicates the CodeWarrior Mach-O tools produced well-formed Mach-O libraries. However, there is always the possibility of an error, either in the specific library you are using or in the tools generically, at which point what you are seeing is a bug report for eSellerate or ultimately Metrowerks to correct.

Apple's engineering staff can determine what the problem with the library might be if we have a copy of it and a report of Xcode error report when you try to use it. However, your license agreement with eSellerate may not allow you to send us the library for analysis.

If you could send me the build log from Xcode when it chokes on this file, that will help determine what the situation is.

thanks
Godfrey
---
  Godfrey DiGiorgi - email@hidden
  408 974-6814 tel - 408 974-8101 fax - 408 832-8319 cell
  Technology Manager, Development Tools
  Apple Worldwide Developer Relations


On Nov 19, 2003, at 2:21 PM, Mark Munz wrote:

I may have missed earlier discussions on this (unfortunately, there doesn't seem to be any searchable archives), but Xcode seems to choke on a CW generated .a file. Specifically the libeSellerate.a (from eSellerate).

1. Do we have to do some sort of conversion when dealing with CW mach-o files? Or is this a bug with Xcode?
2. If it's the former, is there a reason why Xcode doesn't offer to do this for us instead of just complaining?


Thanks.

Mark Munz
_______________________________________________
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.
_______________________________________________
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.

References: 
 >CW .a files (From: Mark Munz <email@hidden>)

  • Prev by Date: Re: Xcode cross-developing to 10.1 and NSProgressIndicator (Modified by Justin Lundy)
  • Next by Date: zero-link vs library
  • Previous by thread: CW .a files
  • Next by thread: Re: CW .a files
  • Index(es):
    • Date
    • Thread