You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not at this time. These files usually sit alongside their associated binary artifacts, so discoverability is usually not an issue. Anyway, what would be the use case for providing these?
I'm not opposed to the idea, but it's likely to be way, way down on the priority list.
My use case is CMake, where it's useful to copy the PDB files of dependencies to the build directory for a better debugging experience. Static libraries can also have associated PDB files.
Adding the PDB location is not enough: you also need to configure the location of the sources, and know the location of the sources on the build machine.
This way, IDE's can automatically configure the search path.
e.g. for gdb, this is done using settings set target.source-map /buildbot/path /my/path
This also means cps might need an extra component type named sources in addition to dylib, archive, interface, jar and symbolic.
Is there a way to encode debug information?
MSVC toolchains can embed debug information, or generate external PDB files.
GNU toolchains can also embed debug information, or split the dwarf information into an external library.
The text was updated successfully, but these errors were encountered: