Currently, a typical %GAMSDIR% in my organisation looks something like C:\GAMS\win64\25.1.3;C:\GAMS\win64\25.1.3\gbin;C:\GAMS\win64\25.1.3\apifiles\Java\api. This means __find_gams takes tries to find gams in the folder C:\GAMS\win64\25.1.3;C:\GAMS\win64\25.1.3\gbin;C:\GAMS\win64\25.1.3\apifiles\Java\api which doesn't exist.
One option is to validate the path before using it.
I'm digging into why this is but would it be possible to hotfix this or check which/where?
Currently, a typical %GAMSDIR% in my organisation looks something like
C:\GAMS\win64\25.1.3;C:\GAMS\win64\25.1.3\gbin;C:\GAMS\win64\25.1.3\apifiles\Java\api
. This means__find_gams
takes tries to find gams in the folderC:\GAMS\win64\25.1.3;C:\GAMS\win64\25.1.3\gbin;C:\GAMS\win64\25.1.3\apifiles\Java\api
which doesn't exist.One option is to validate the path before using it.
I'm digging into why this is but would it be possible to hotfix this or check which/where?