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
Whenever an error occurs in a library header, the make command will jump to the header file in dev/dist because that is the location the file was included from to build the application.
Unfortunately changing the header file is not persistent. We want to change the header file in the corresponding dev/src directory. But it could be a valid use case to make a temporary change in dev/dist in order to fix the problem without rebuilding the library (e.g. for header-only library).
How to proceed with this? It is necessary to give the user a hint, that he is changing a file in dev/dist, which will be overwritten as soon as the library implementation changes in dev/src.
One solution could be to open files in dev/dist as read-only.
Next question is, how to get from this file to the corresponding file in dev/src as fast as possible? Maybe something like BobGotoSrc.
The text was updated successfully, but these errors were encountered:
Whenever an error occurs in a library header, the make command will jump to the header file in dev/dist because that is the location the file was included from to build the application.
Unfortunately changing the header file is not persistent. We want to change the header file in the corresponding dev/src directory. But it could be a valid use case to make a temporary change in dev/dist in order to fix the problem without rebuilding the library (e.g. for header-only library).
How to proceed with this? It is necessary to give the user a hint, that he is changing a file in dev/dist, which will be overwritten as soon as the library implementation changes in dev/src.
One solution could be to open files in dev/dist as read-only.
Next question is, how to get from this file to the corresponding file in dev/src as fast as possible? Maybe something like
BobGotoSrc
.The text was updated successfully, but these errors were encountered: