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
A docker container will only be used if you explicit configure it.
The part that is missing in your setup is that the compiler you use (a MinGW based one) is not built for the path you have it placed in (it rarely isn't), cobc is not relocatable (a feature that looks for the files relative to itself, something that is worked on in GnuCOBOL 4+, currently works in GNU/Linux) and you did not instruct it to use a different path.
So: instruct it to use a different path as you do when using this version of cobc in other setups - either globally set COB_CONFIG_DIR and friends in your Windows environment, or set it before starting vscode (commonly by double-click on set_env.cmd then starting vscodium.exe / code.exe from the opening command prompt) or by creating a minimal cobc.cmd that just contains X:\path\to\set_env.cmd && cobc.exe %* - then point this extension to use this cobc.cmd.
D:\VertSoft\Cobol\learning\MyTest>cobc -x TestProgram01
configuration error:
/mingw/share/gnu-cobol/config\default.conf: No such file or directory
How can I fix this.
I think if the last separator is changed it will work but how to do it?
I use VSCode on Windows but apparentlythe debugger uses a docker container and that is linux
The text was updated successfully, but these errors were encountered: