Noob question

[Manuel Dun]

What I hopefully want to do is to contribute to the mesa 3d project.
Since mesa has so many moving parts it seems overwhelming, I know the
documentation is there but I want to debug the source code with gdb to
compare and strengthen my knowledge. A good-first-task would be ideal
to start working. What is the correct way to, for example, test that
my patch is working? You mention a loader, can you explain that to me?

By the way, I am not used to using a mailing list, if this email is
not correctly sent please let me know.

El sáb, 30 mar 2024 a las 8:42, Jens Owen (<jens at jelo.com>) escribió:
>
>
>> I want to link a vulkan app written by me to the mesa3d source code to
>> be able to step in it with the debugger. The app has the mesa 3d as a
>> subproject. My question is, what is the name of the vulkan dependency
>> so i can add it to my executable in the meson.build? Is it possible to
>> do it this way? What would be the correct way to do this?
>>
>> My current setup is linux mint os with an amd gpu and I was able to
>> compile mesa 3d version 23.3
>
>
> My familiarity with exactly how Mesa integrates open source drivers like RADV, Mesa’s Vulkan driver for AMD, is minmal, but there is excellent documentation here:
> https://docs.mesa3d.org/drivers/radv.html
>
> Depending on what you need to do, you might not need to build a debuggable version of that driver and can instead rely on either logging from the RADV driver by setting environment variables, or using the validation layers from LunarG’s Vulkan SDK.
>
> I wouldn’t recommend rebuilding the main Vulkan library, unless you want to get into the guts of the loader itself.
>