On Sunday, January 10, 2021 6:29:07 AM CET Shane Ambler wrote:
Hello Shane,
> You don't have to do it all yourself, you create the bug reports to
> change tbb and to create onetbb, one report can depend on the other so
> they get committed together. My experience is being told to submit one
> rep
On 10/1/21 4:29 am, Ganael Laplanche wrote:
> 1) Move devel/tbb to a dedicated subdir and install devel/onetbb to its
> default location. Here, we just anticipate what is written above. As you say,
> as having devel/onetbb-only is the target, that would be the best solution
> *BUT* it has the m
On Saturday, January 9, 2021 9:49:24 AM CET Shane Ambler wrote:
Hello Shane,
Thanks for your reply.
> > - leave devel/tbb in place and introduce a new port: devel/onetbb
>
> While I would generally support moving the old libs to a new portname,
> the fact that the project has renamed itself mak
On 8/1/21 9:51 pm, Ganael Laplanche wrote:
> - leave devel/tbb in place and introduce a new port: devel/onetbb
While I would generally support moving the old libs to a new portname,
the fact that the project has renamed itself makes this acceptable.
> - design devel/onetbb to install files in de
Hello,
First of all, happy new year :)
Intel oneAPI tbb (formerly known as Intel tbb) 2021.1 has been released and
has deprecated several interfaces over tbb 2020.
See:
https://software.intel.com/content/www/us/en/develop/articles/intel-oneapi-threading-building-blocks-release-notes.html
a