Will using different versions of the library conflict with each other and cause undefined behavior? about onetbb

[pavelkumbrasev]

Both you and your customers use oneTBB (not the old TBB)?
We support backward compatibility so when customer's library will load newer version of oneTBB it will also be used for your library.

[balleb6545anickk]

Both you and your customers use oneTBB (not the old TBB)? We support backward compatibility so when customer's library will load newer version of oneTBB it will also be used for your library.

Can you explain the linking process more clearly? I can ensure that the dynamic link library I provide uses oneTBB. But I can't estimate the customer's behavior.

[pavelkumbrasev]

When you compile your library using TBB headers certain amount of symbols will be expected during linking stage (from TBB).
For example if your library is built and linked with oneTBB 2021.2 all later versions of library will have the same list of symbols as 2021.2 (+ something new) that is done to support backward compatibility.

1. Let's say your library is linked with oneTBB 2021.10 and your customers use oneTBB 2021.11. During runtime loader will load oneTBB 2021.11 which will indeed satisfy required symbols from your library.
2. Let's say your library is linked with oneTBB 2021.10 and your customers use oneTBB 2021.2. During runtime loader will load oneTBB 2021.2 which may not satisfy required symbols from your library.

So it's better to clarify what version of TBB your customers are using so you can adjust and use the same or earlier versions respectively.