tip: IDE in "Program Files"

[ghost]

Maybe not a bug, but an issue with an alternate work-around...
ERROR:
"Compile failed (CreateChildProcess). Please install WinFBE into a folder without spaces."
RECREATE:
(Using v2.1.8 (64-bit) under Win7 in VirtualBox 6 under Linux Mint 20.1)
After testing the IDE in a folder under my downloads, I moved it into C:\Program Files\WinFBE_Suite and touched up the paths in WinFBE.ini. Trying to compile a project already created, I got the error message above.
WORKAROUND:
Instead of moving the app again, I recalled that in Win/DOS there is an 8.3 format alias for long files/paths or with spaces. Use "dir /x" to see aliases. Alias for "C:\Program Files" on Win7 is "C:\PROGRA~1". Making this substitution in WinFBE.ini allowed compile to complete.

[PaulSquires]

This is an issue that I have struggled with for some time and has been commented on over in https://www.freebasic.net/forum/viewtopic.php?f=8&t=25215 I am aware of the shortpathname vs longpathname approaches and have attempted to do the conversions "on the fly" during the compiling process. Sadly, I have not been successful and the failure occurs when the compile parameters are fed into the GCC backend toolchain (most of the time when attempting to invoke the linker). However, from my tests it appears that WinFBE code generated programs will compile successfully if I manually compile outside of WinFBE via the command line so there must be something within the WinFBE code that invokes the compiler that is tripping up the process. I will leave this issue open as a reminder to attempt to debug the error once again. (I will add that my research has shown that the GCC tools, being a unix/linux toolchain, does not like paths containing spaces even if they are enclosed in double quotes).

[ghost]

If I get time later, I may try moving it to a folder called "Programs', just to see what happens.