Replies: 2 comments
-
I have the same problem. I followed all the instructions and guides but it fails to create the .exe when I change the cwd from |
Beta Was this translation helpful? Give feedback.
-
cwd is generally not something you want to change as it leads to more issues more often than not, you can instead try switching to CMake as it's far more flexible in this regard, and then copying the .txt file to the output directory with add_custom_command, or perhaps making a bash script that will copy that .txt file to output directory (like some do for .dll files), or even setting a cmake directory variable that leads to wherever that .txt file is located. |
Beta Was this translation helpful? Give feedback.
-
I am working on a project where
input.txt
is in the same level as the file to compile.However, the outputs are found in
/root/output/
Running the file through the extension keeps the
cwd
to/root/
and the input file won't be found.I am unable to find any sort of documentation to find a solution to my issue.
The
cwd
property fortasks.json
seems to only apply to the compiler part.Is forsaking the extension's Run C/C++ File the only option for me?
I had success for changing the
cwd
forlaunch.json
for debugging but it doesn't apply for running the program.Here is my
tasks.json
Beta Was this translation helpful? Give feedback.
All reactions