Version 2+ cannot compile SSL if the output path contains spaces

[blackpaulillyria]

Hi, I installed the latest version and couldn't compile SSL file to a target path that contained space(s) in its name. For example C:\My Scripts

I had to downgrade to version 1.16.3 which works well with such paths.

[burner1024]

What do you mean by couldn't?

[blackpaulillyria]

It fails to generate .INT file when the target path to the output folder contains a space.

Version 1+ would run the command like this

"D:\ScriptEditor\resources\compile.exe" -q -p -l -O2 -d -s -n test.ssl -o "C:\My Scripts"\test.int

Version 2+ runs it like this

"D:\ScriptEditor\resources\compile.exe" -q -p -l -O2 -d -s -n test.ssl -o C:\My Scripts\test.int

So since it doesn't wrap the target folder into quotes, the command gives back and error instead of INT file. That's what happens on my Windows 10 PC at least.

[burner1024]

Is there an error that you see?

[blackpaulillyria]

stdout: Warning: c:\My not found
Warning: Scripts\.tmp.ssl not found
Warning: -o not found
Warning: test.int not found

[burner1024]

Try this build

[blackpaulillyria]

Sorry, no luck. Still throws the same error

[burner1024]

Show screenshot.

[blackpaulillyria]

Here you go

[burner1024]

Try last build, see what it shows then.

[blackpaulillyria]

Hi, still no luck but I think we're getting closer to fixing it. I see you wrapped the output filename into quotes but not the .tmp.ssl path. If you wrap that path too, the problem would be gone.

[burner1024]

Ah you got source with spaces.
Should work now.

[blackpaulillyria]

That's it, works perfectly! Thank you so much!