In this article I'll try to give a small descriptive overview of how to install FBIde onto Linux from CVS sources. First you need few things installed onto your Linux machine. Such as GTK 2+. This library however is usually included with all modern distros. If not then I suggest you goto Google, for information on how to install/get GTK onto your machine. Because FBIde is based on wxGTK library wich is based on GTK. So first step is to get wxGTK and build it.

Installing wxGTK

First you need to download the package from wxWidget's webpage under download section: http://www.wxwidgets.org/dl_gtk.htm#stable It is prefered that you download 2.6.2 because this is the version we use in development, although it might work without problems with 2.4.2 as well.

After you downloaded wxGTK successfully you need to install it. INSTALL.txt file (which is located in the root of the wx directory) covers this aspect pretty well.

After this you need to also build stc library. Stc is provided with the wxGTK under the contrib folder. Configure script that you used to compile wxGTK also generates a makefile for STC, which is located in the configure directory /contrib/src/stc/  ( if you followed the instructions as in INSTALL.txt then makefile is located in wx root /buildgtk/contrib/src/stc/ ).

Open terminal and type:

make
make install
ldconfig

If everything went well then wxGTK is installed on your system and we can get to installing FBIde.

Getting FBIde sources from cvs

    First we need to get sources that we are going to build.  Most Linux distros come with CVS, so open a terminal, go to the directory where you want your sources to be downloaded and type the following command:

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/fbide co -P FBIde/FBIde0.4

This will hopefully retrieve the sources. Make sure you set permissions to modify/read/write and execute for the owner and read/execute for group and other users (or 755 if you going to use number to set the permissions).

Compiling FBIde

    Now that we have FBIde sources, and also wxGTK and STC installed let's build FBIde. Go to the FBIde0.4/ directory, open terminal and type:

make

Hopefully everything will go alright. Executable is generated into FBIde0.4/output/ Note that cvs sources and makefile will build a debug version of the IDE.

Running and finetuning FBIde

    Open output directory and type ./fbide This should run. Open view->settings->FreeBasic there's few possible options to change the behaviour. Like what to do when you hit compile or when you want to run the file. By default the run command is:

xterm -e 'cd <file_path>; ./<file_name> <param>'

   This is needed mostly for console applications, otherwise they will not showup when you try to run them. Since xterm is pretty ugly looking( but yet standard to all distros ) then you can change it to your favorite one. Here's the metacommand's that are supported:

<file> - full file name ( path + name )
<file_path> - only file path
<file_name> - only file name
<file_ext> - file extension
<param> - Parameters that are set in fbide
<terminal> - terminal name that is specified in [paths] section ( this can be set in output/IDE/prefs_linux.ini manually )

Conclusion

    We are interested in all kinds of feedback about FBIde -be it bug reprts or just questions or constructive criticism. You can reach us via email ( see Contacts ) or in FreeBasic forum under FBIde section

Hope you enjoy FBIde, VonGodric
Page edited by Jatos.