Congratulation for your video. So, I want only give one recomendation for other partners, in my case the solución for some code lines was: "label": "make build dir", "type": "shell", "command": "if (!(Test-Path -Path \"./build\")) { New-Item -ItemType Directory -Path \"./build\" }"
Great tutorial! While testing your example files, I recognized that the "local" settings, which are located in the .vscode directory, are only applied if you open a single project folder as workspace in vscode. It gave me some headache to figure this out, since I initially loaded the complete folder, including all example folders into vscode and this way it did not work. Correct me if I'm wrong, I just started using vscode. But maybe this helps others, facing the same issue. Best regards!
This was a lot more useful by adding {fileBasenameNoextension}.exe and .f95 into the argument list. Then a Ctrl-Shft-B builds the target project. No libraries but for simple builds it works well.
thank you Lukas, the series is awesome! Really great! How can I also generate .o files and put them in a separate folder? I do have a way but not as simple as I think it could be
Dear Mao Yang, thank you! There are at least two more episodes planned for this series. Since I am quiet busy at the moment, I can not tell you when they will go online. I hope you understand. So stay tuned. ;) Best regards
Very helpful tutorial series. Thank you, Lukas. Though in my case 'Run Tasks' did not show the 'hello' tasks, even though I followed all steps closely.
Thanks! That was really useful, especially the last part using the make file as this is what most people do in real life situations.
Congratulation for your video. So, I want only give one recomendation for other partners, in my case the solución for some code lines was:
"label": "make build dir",
"type": "shell",
"command": "if (!(Test-Path -Path \"./build\")) { New-Item -ItemType Directory -Path \"./build\" }"
Thanks, I've been looking for a ide fortran debugger working on mac for a while
Great tutorial!
While testing your example files, I recognized that the "local" settings, which are located in the .vscode directory, are only applied if you open a single project folder as workspace in vscode.
It gave me some headache to figure this out, since I initially loaded the complete folder, including all example folders into vscode and this way it did not work.
Correct me if I'm wrong, I just started using vscode. But maybe this helps others, facing the same issue.
Best regards!
Thanks for the good remark.
This was a lot more useful by adding {fileBasenameNoextension}.exe and .f95 into the argument list. Then a Ctrl-Shft-B builds the target project. No libraries but for simple builds it works well.
thank you Lukas, the series is awesome! Really great!
How can I also generate .o files and put them in a separate folder? I do have a way but not as simple as I think it could be
fantastic, Will there be more new episode?
Dear Mao Yang,
thank you! There are at least two more episodes planned for this series. Since I am quiet busy at the moment, I can not tell you when they will go online. I hope you understand. So stay tuned. ;)
Best regards
Very helpful tutorial series. Thank you, Lukas.
Though in my case 'Run Tasks' did not show the 'hello' tasks, even though I followed all steps closely.
... and a little later I figured out my mistake. All works perfectly fine now :)
Hugely helpful, thanks for making this
This series is awesome, Lukas.
Thank you so much for sharing!
how do you put vertical line in vs code?
Hey,
if you mean a ruler, take a look here: ua-cam.com/video/MZZLhodCzRY/v-deo.html
Best regards.