demosthenesk
Just to show that the flag is -b to compile a file without the .bas extension.
My procedure simply will do the same as above, but will show all compile errors (including gcc errors), if any, in a child window (for a compile log for instance)
ok, i understand this
but my question is, why to pass txt file to fbc and to write a program... the only answer is trying to make a fb ide and manipulate fbc.. but still i don't know why...?
Many thanks dear dodicat thats working perfect Here. I must Change my freebasic folder to Test the example cause there was a path Error Here.. but now its working all fine. Thats great
For demosthenesk: I Had Made a simple Editor with afx in winfbe Editor some weeks ago. I could load and save a File ( *.txt) into an editbox and then I tried to send this (Here) the Text File to fbc.. but without success. I wanted to know how compiling is Working and found therefore shell command Run execute and much more about this topic.. thats all
PS: the one liner with Shell with fbc exe -b a-calc1.txt produces successful an exe File with Same Name a-calc.exe but you cannot ready the result but I suppose thats Not possible
Löwenherz wrote: ↑Oct 14, 2024 19:13
Many thanks dear dodicat thats working perfect Here. I must Change my freebasic folder to Test the example cause there was a path Error Here.. but now its working all fine. Thats great
For demosthenesk: I Had Made a simple Editor with afx in winfbe Editor some weeks ago. I could load and save a File ( *.txt) into an editbox and then I tried to send this (Here) the Text File to fbc.. but without success. I wanted to know how compiling is Working and found therefore shell command Run execute and much more about this topic.. thats all
PS: the one liner with Shell with fbc exe -b a-calc1.txt produces successful an exe File with Same Name a-calc.exe but you cannot ready the result but I suppose thats Not possible
Regards loewenherz
yes i supposed that all this is for fb ide...
the real need is someone to create an msdos ide for fbc ... that would be real nice !
demosthenesk wrote: ↑Oct 14, 2024 19:43
the real need is someone to create an msdos ide for fbc ... that would be real nice !
My RETROGRA library implements a pseudo-terminal I call "VT 2000". This would be handy to create a console-based editor like that GFA BASIC used:
It allows PRINT-output and graphics like that of the C 64. But the library is not thought for MS-DOS, just for programs looking as if being MS-DOS based => VGA resolution. It's not optimised for an 8 bit enviroment. Further I want to take out the VT 2000 stuff for the long term and make an own library, supporting many resolutions and font sizes.
demosthenesk wrote: ↑Oct 14, 2024 19:43
the real need is someone to create an msdos ide for fbc ... that would be real nice !
My RETROGRA library implements a pseudo-terminal I call "VT 2000". This would be handy to create a console-based editor like that GFA BASIC used:
It allows PRINT-output and graphics like that of the C 64. But the library is not thought for MS-DOS, just for programs looking as if being MS-DOS based => VGA resolution. It's not optimised for an 8 bit enviroment. Further I want to take out the VT 2000 stuff for the long term and make an own library, supporting many resolutions and font sizes.
very nice !
i use dosbox-x and dos fbc
i have installed win3.11 in dosbox-x and the files are available in my win11 c drive, so i can edit files with win11 fb ide and compile back to dos fbc in dosbox-x
