OneTBB redistribution

[loopfreq]

Hi,

My product is an unmanaged DLL that uses OneTBB. I'm trying to figure out the best way to provide OneTBB redsitributable DLLs to end users in an MSI-package-friendly way.

A few forum posts indicate that linking to OneTBB statically is not recommended. One example:

https://github.com/oneapi-src/oneTBB/issues/646

There isn't an opportunity to include OneTBB DLLs privately with a application since I don't create an application. So naturally it should be a system-wide installation.

Intel provides a OneAPI Runtime Installer here:

https://www.intel.com/content/www/us/en/developer/articles/tool/oneapi-standalone-components.html

However it's 228 MB which is overkill to install a <1MB DLL. (And not certain this runtime even includes TBB)

There's a OneTBB download further down the page that provides the entire SDK, but again, this is not what I am looking for.

The OneTBB SDK includes redistributable DLLs but no MSI. I've considered simply copying the necessary DLLs into Windows/System32 but this is fraught with complications.

So I'm stuck as to how to go about this. Does Intel provide a runtime installer specifically for installing OneTBB? Or am I going about this the wrong way?

Thanks,

George

[RahulC_Intel]

Hi George, we have sent you a private message. Kindly check your inbox.

[RahulC_Intel]

Hi George, yes you are correct, Intel® oneAPI Threading Building Blocks (oneTBB) has its own runtime (offline/online) installer with MSI only for windows operating system.

You may refer to the link: https://www.intel.com/content/www/us/en/developer/articles/tool/oneapi-standalone-components.html#onetbb and download the Intel® oneTBB standalone component for your system.

Also, visit to the link: https://www.intel.com/content/www/us/en/docs/onetbb/get-started-guide/ , and find the latest user guide for Intel® oneAPI Threading Building Blocks (oneTBB).

[RahulC_Intel]

Hi George, unfortunately we were unable to hear back from you. 

If you have any further query, please post a new question as this thread will no longer be monitored by Intel®.