Big increase in build-time on Windows, after adding LimeLM to product.

Hi,

Since I've added LimeLM/TurboActivate to my project (32 & 64bit VST, VST3 and AAX plugins), my Windows (release) build time became ~5-8x slower. From about 4-5 min, it now never goes under 30min.

I believe the reason to be the bunch of static libs that are required on Windows (I am guessing those probably come as part of OS X, so that's why they are not needed there), that are slowing things down.

Is this normal? If yes, is there something I can do to speed my build up?Thanks.

Regards,Nikolay Tsenkov

Yes, the best and fastest way to build with TurboActivate is to use the dynamic version of TurboActivate. And if you ever find a "bug" in TurboActivate and you're using the static version of TurboActivate, then the solution is 9 times out of 10 to simply use the dynamic version of TurboActivate.

The static versions of TA and TF are complicated to use. That's just the nature of static libraries. They require specific configurations, specific compilers (on Windows, that means MSVC), and they require you not replace, modify, or otherwise overwrite any internal reference in TurboActivate.

Long story short, it's much easier to use the dynamic version of TurboActivate.

Thanks for the reply.

Would you recommend this in a plugin setup, where I have multiple plugins installed in different locations that need to somehow share the dynamic libraries and know where they are?

It depends on your setup. If you know where your plugins will be then you can put TurboActivate in a centralized place. If not, it doesn't hurt anything to have multiple copies of TurboActivate.dll

We are pretty close to a release and I feel this change isn't that safe. I definitely will give this a go once I get to the next dev iteration of our product.

Reply
Discard post