The following two calls in one console provide an overview of all relevant Gambas programs, such as the GB compiler or the GB interpreter:
hans@linux:~$ cd /usr/local/bin hans@linux:/usr/local/bin$ ls -l g* lrwxrwxrwx 1 root root 14 Okt 31 15:57 gambas3 -> gambas3.gambas -rwxr-xr-x 1 root root 3720658 Nov 19 19:44 gambas3.gambas -rwxr-xr-x 1 root root 116451 Nov 19 19:44 gba3 -rwxr-xr-x 1 root root 564804 Nov 19 19:44 gbc3 -rwxr-xr-x 1 root root 113171 Nov 19 19:44 gbi3 lrwxrwxrwx 1 root root 4 Nov 19 19:44 gbr3 -> gbx3 lrwxrwxrwx 1 root root 11 Okt 31 19:24 gbs3 -> gbs3.gambas -rwxr-xr-x 1 root root 25204 Nov 19 19:44 gbs3.gambas lrwxrwxrwx 1 root root 11 Okt 31 19:24 gbw3 -> gbs3.gambas -rwxr-xr-x 1 root root 1924420 Nov 19 19:44 gbx3 hans@linux:/usr/local/bin$
The chapter' Gambas intern' is dedicated to the following questions: How does Gambas work? Or how and in which hierarchy do the individual programs compilers, archiver and interpreters work together for a Gambas project? The following graphic only represents this hierarchy statically:
If you are writing a program in Gambas, then create in a project folder
This is how Gambas works internally:
In the IDE of Gambas applies to a Gambas project:
hans@linux:~$ gbc3 -ag path_to_project_folder OK hans@linux:~$ gba3 path_to_project_folder hans@linux:~$ gbx3 path_to_project_folder
A compiled Gambas archive can only be run with the program' gbr3', because' gbr3' is a symbolic link to gbx3, but behaves differently when called as' gbx3'.