Open pvmm opened 2 years ago
I like your comments and take them into account for the 2.0 version, which must comme this year. :-)
besides "Working Folder", I have another white space problem. I installed SDCC in d:\Program Files\sdcc... when running the compil.bat test with echo on, and sdcc with the -V parameter I get:
D:\Downloads\Fusion-C-v1.2-master\Working Folder>sdcc.exe --code-loc 0x106 --data-loc 0x0 --disable-warning 196 -mz80 --no-std-crt0 --opt-code-size fusion.lib -L fusion-c\lib\ fusion-c\include\crt0_msxdos.rel -V test.c
I suppose most of the people installed SDCC in a "space-less" directory? Otherwise you will never get the sdcc.exe to work? Or you should make a symbolic link to the directory using mklink.
Thanks for the feedback!
Hi, I do not really understood what you 've done.
As far as I remember, if SDCC was installed with the original setup, SDCC can be called from a DOS prompt without specifying its path...
Open a Command window and Just type
SDCC -V and you must have a response like this one .SDCC :
mcs51/z80/z180/r2k/r2ka/r3ka/gbz80/tlcs90/ez80_z80/z80n/ds390/pic16/pic14/TININative/ds400/hc08/s08/stm8/pdk13/pdk14/pdk15 4.1.0 #12072 (MINGW64) published under GNU General Public License (GPL)
Do not add "-V" inside the command line to compel your code. You do not have to specify the path of SDCC exe file in the compilation script.
Did I miss something ?
The path variable and the response were okay. But what I learned:
Then things go right ;-) Thanks for the feedback Eric!
Rename
Working Folder
to some other name without space characters. It's error prone for scripting. I likeworkspace
which is common practice in several IDEs.