Linker errors using Mac static libsSolved

I get linker errors when using the Mac static lib. Is there something I'm not doing right?

Undefined symbols for architecture i386:"_curl_easy_cleanup", referenced from:CurlDownload::~CurlDownload() in libTurboActivate.a(CurlDownload.o)

...etc. There's 8 curl functions that are undefined, and also there's "_SCDynamicStoreCopyProxies".

Oh, sorry, we never finished the article about the Mac static library. I've just updated it: Using the static library (libTurboActivate.a)

Ok, that was it. Thanks. Another problem though:

Undefined symbols for architecture i386: "_IsGenuineEx", referenced from: ...

This is the only linker error I'm getting now, and it ONLY happens when in build in Debug. When I build in Release, it links properly. Any ideas? It seems like it's finding the library (otherwise it would complain about all the other functions), just not that one function.

This linker issue seems only to exist on older XCode versions. On XCode 4.2.1, for example, it can't find IsGenuineEx when building in Debug. But on XCode 4.5.2, it does link properly.

Hmmm... it works fine on Xcode 3.x as well. It must be a bug in XCode 4.2.x

So you were able to confirm that it doesn't work on 4.2.x? Just want to make sure I'm not doing something wrong.

No, I haven't tested it on XCode 4.2. I'm assuming you're doing things identically between the versions.

Yup, identical. But it's always good to get a second opinion.

I'm using OS X 10.7.5, and I've upgraded to the latest XCode (4.6.3), but I'm still getting the linker error with IsGenuineEx in Debug. So I don't think I'm doing anything wrong. Have you tested on 10.7?

This is for a 32-bit build, by the way.

I thought you said this was fixed in 4.5.x? Did this XCode bug pop up again?

I realized that the issue is not what XCode version it is, but what OS X version it is. Previously when I said it was fixed, I was using my 10.8 machine. However, when I tried it on my 10.7 machine, it was still broken.

Hi, are you working on this at all? I'm awaiting any info.Thanks

No, we weren't working on it. This sounds like a bug in Mac OS X 10.7. We can't reproduce this in Mac OS X 10.6 or 10.8, and we haven't tested with 10.7. Is there any reason you're using Mac OS X 10.7 if the bug (and many others) are fixed in 10.8?

Yes, I need to be able to debug on 10.7 to find bugs specific to that operating system. But honestly, even apart from that, I'm a paying customer and if you say that you haven't tested your own product on 10.7, that's a bit surprising and disappointing. As a software developer myself, I couldn't imagine not testing software on all available operating systems that my product claims to support.

We have tested TurboActivate on 10.7 (and 10.5, 10.6, an 10.8) quite extensively. What we haven't tested is building an app with the *static* version of TurboActivate with an old version of XCode on an old version of Mac OS X. Why? Because you reported it solved (or at least, that's how I read it). Now, if it's still a problem for you we'll look into it.

If you read my post(s), what I said is the following:

- When using the latest version of XCode (4.6.3 at the time),- on my OS X 10.7.5 machine,- building 32-bit only,- building Debug,- and using your static library,"it was still broken."

I thought that was pretty clear. If there's some other way you would have liked me to phrase it, please share.

And FYI, I was not the one who added "[Solved]" to the title of this post.

Further, this still surprises me: "What we haven't tested is building an app with the *static* version of TurboActivate with an old version of XCode on an old version of Mac OS X."

In my company, we test as many configurations as possible. This would at least include every version of our product on every major recent operating system (Windows Vista/7/8, OSX 10.6/7/8). This is just common sense, don't you think? Especially since in this case, the XCode version doesn't seem to matter.

We were not able to reproduce this. Closing this as resolved. If more information is provided we'll gladly re-investigate.