Static C libraries not in TurboActivate download

The static libraries for Mac are coming with TA 3.3, and that's coming early next week.

We are distributing a command line utility for mac and a static library for x86_64 would be extremely helpful.
Where can we download the package for Mac?

Is there any ETA for TA 3.3?

Regards,

Petr

We're trying to get it out before the end of the month.

Ok, great. Any idea when that will be released?

The static Mac library is coming with TA 3.3.

Hi there, just wondering if there was any progress on the OS X static libraries. Would really like to start using these if possible.

[quote]Really? When I try to just rename the .dll, I can't run my app[/quote]

It's possible to rename the dll/dylib and use it with your app, but I didn't say it would be easy. :D


On Windows you have to link directly to the *.dll file (which I can't remember how to do off the top of my head, but I'm sure Google can help you out). That is, don't use the #pragma(comment, lib, "TurboActivate.lib").

On Mac OS X you might have to use some developer tools to change the "internal" name of the dylib so the correct file is loaded. You'll also have to changed the embedded rpath.


In short, it's probably more hassle than it's worth.



[quote]One more question - do the dynamic libs have any other dependencies? I.e., on Windows, does TurboActivate.dll require the MSVCRT dlls? I just want to make sure I can ship my program without the user needing to install anything else.
[/quote]


There are no external dependencies. See [url=http://wyday.com/limelm/help/using-turboactivate/#requirements]Requirements for TurboActivate[/url].

Really? When I try to just rename the .dll, I can't run my app ("The program can't start because TurboActivate.dll is missing...") But after some, Googling, it seems that I can use the "LIB" command on Windows. Is that what I need to do?

Similarly, just renaming the .dylib doesn't work either. How would I do this on Mac?

One more question - do the dynamic libs have any other dependencies? I.e., on Windows, does TurboActivate.dll require the MSVCRT dlls? I just want to make sure I can ship my program without the user needing to install anything else.

[quote]like "Data.dll/.dylib", would be a very quick and easy way to add just a bit more protection.[/quote]

You can always rename TurboActivate.dll/dylib to anything you want.


We are planning to release Mac OS X static libraries, but we wanted to get some other things out first. But if you need it we can push it up the priority list.

Sure, I know that a determined cracker will get what he wants.

But it just seems to me that naming the dynamic library something generic that's not easily trackable on Google, and something completely unrelated to licensing, like "Data.dll/.dylib", would be a very quick and easy way to add just a bit more protection.

If I Google "TurboActivate", your web site is the first result, and then I can download all your SDK code to investigate further -- which I assume would be helpful to any cracker.

Again, not a big deal, but just a suggestion to consider.