Vulkan rendering pipeline dependency on libstdc++
Alexey Ushakov
alexey.ushakov at jetbrains.com
Mon Nov 13 10:05:24 UTC 2023
Thanks for the answer, Phil. It’s good to know the requirements at the early stage of the development. We’ll try to change the architecture to move as much logic as possible at the Java level.
Best Regards,
Alexey
> On 10 Nov 2023, at 10:36 PM, Philip Race <philip.race at oracle.com> wrote:
>
> It is a very bad idea. C++ ABI has been an issue before.
> It likely would make it impossible for us to create a single build that we can guarantee runs across distros
> and OS versions.
>
> So an emphatic no. We'd not accept that into OpenJDK.
>
> -phil.
>
> On 11/10/23 7:27 AM, Nikita Gubarkov wrote:
>> Vulkan has both C and C++ API (two types of the latter actually). When working on the prototype implementation of Vulkan rendering pipeline under Wayland we have chosen C++ API, as it is better in all aspects, but most importantly, speeds up development at early stages a lot. However, these C++ API headers bring a dependency on Standard Library, so this needs to be discussed:
>> How do you feel about bringing a dependency on libstdc++?
>
More information about the wakefield-dev
mailing list