• 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: Avoiding link conflicts with a static library
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Avoiding link conflicts with a static library


  • Subject: Re: Avoiding link conflicts with a static library
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 04 Apr 2018 11:36:49 -0700


> On Apr 4, 2018, at 11:34 AM, Alastair Houghton <email@hidden>
> wrote:
>
> You could rename the symbols in your copy of OpenCV so that they don’t match
> the standard ones. One way to do that is with the preprocessor (use #defines
> to change the names of the OpenCV functions you use), which potentially
> avoids altering the OpenCV sources themselves (you can use a prefix header to
> get your #defines into the OpenCV build process if necessary).

Oh — I totally forgot that. We used that technique in our version-1 static
library.

—Jens
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Avoiding link conflicts with a static library (From: Redler Eyal <email@hidden>)
 >Re: Avoiding link conflicts with a static library (From: Alastair Houghton <email@hidden>)

  • Prev by Date: Re: Avoiding link conflicts with a static library
  • Next by Date: Re: Avoiding link conflicts with a static library
  • Previous by thread: Re: Avoiding link conflicts with a static library
  • Next by thread: Re: Avoiding link conflicts with a static library
  • Index(es):
    • Date
    • Thread