<solved> QB64 without its IDE GUI ?

[Fifi]

I don't get the movement to make QB64PE like Freebasic. Is the IDE really that bad?

Hi mnrvovrfc

I don't think there is any movement from anyone to make qb64pe like fb. And no, the IDE isn't that bad but on macOS where it's almost unusable without the MouseWheel.

Just use -o and -x switches with the regular QB64PE executable. Why so much work only to remove what is not needed, to save a few megabytes on a 64-bit system? 

Of course I use the command line with the -x-q -o switches. 

However, my personal need for a long time to separate the compiler from the IDE is for a very specific project where the compiler is on an embedded system that will fit on a chipset.

So every byte saved will be a real plus for this very special project.

At the same time, the devs of this specific project will continue to use the complete qb64pe with its iDE but on their development machines (whatever the OS of their choice) and only the finished sources will be sent to the project to be compiled and executed "on the fly".

I just can't tell you more, but this is the principle.

But now that it's so easy to separate the IDE from the compiler, wouldn't it be a good idea if these two parts were effectively separated (the IDE and the compiler) and the two executables were called one else: ie. the IDE calls the compiler to pass it the source to compile (and run if needed) and conversely if needed the compiler calls the IDE to send it back the error codes (and the line number of the problem)?

This would have multiple advantages:
a) although the whole project would still be delivered in its entirety (IDE and compiler in the same package), it would still leave the choice to the users to use another editor that they master or prefer. So this will not distort the image or the spirit of the initial QB64 project.
b) it would also make it possible for others to create special tools where only the compiler is used, like in my case.
c) this would place the compiler like any other standard compiler (eg. GCC, C++, etc) and I imagine would open a very large audience.

Also, I don't think it's a huge development to make since the two parts are well and truly separate.

But it's up to the developers of the qb64pe project to decide even if some of the old team categorically opposed it for no real reason (especially since the separation already exists).

Moreover, as a complete package, it would continue to differentiate qb64pe from other BASIC languages like FB or others which precisely don't have an IDE.

Just my two cents.
Cheers.
Fifi