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
After much research, importing dep sources is not that simple. The binaries are built with references to absolute source paths.
For example, I built sqliter on this machine, so adding those exact source files allows the debugger to work, but adding the same files in a different folder does not. The absolute paths must be in the IR output, and would need a way to be changed.
Possibly change KN compilation and include sources in the klib file.
It's a lot of work and not just in this plugin (unless there's a way to alter the binary and change paths).
The text was updated successfully, but these errors were encountered:
kpgalligan
changed the title
Import dependency sources
Debug dependency sources
May 11, 2019
After much research, importing dep sources is not that simple. The binaries are built with references to absolute source paths.
For example, I built sqliter on this machine, so adding those exact source files allows the debugger to work, but adding the same files in a different folder does not. The absolute paths must be in the IR output, and would need a way to be changed.
Possibly change KN compilation and include sources in the klib file.
It's a lot of work and not just in this plugin (unless there's a way to alter the binary and change paths).
The text was updated successfully, but these errors were encountered: