Yuku free message boards

There are two ways of installing programs: compiling them from the sources, or installing precompiled packages (similar to installers in the Windows world, only they install at a predefined place and therefore, you usually don't have to edit your PATH).
Fortunately, Windows, MacOS X, most (GNU/)Linux distributions and (Open)Solaris favor the second way.

Obviously, for you, the first way is hardly feasible, all the more you'd have to install at least the KDE/Qt development libraries for KTIGCC, and maybe something for TIGCC too.
It would be a good way to learn, but it's a bit too much to chew in one chunk... and there are programs simpler than TIGCC to start with.

(On a side note, it's even harder to compile from the sources on Windows, because you'd first have to install a C/C++ compiler + development libraries - none are provided out of the box - and for TIGCC, a Delphi compiler+development library to compile the IDE)


So that leaves us with precompiled packages.
There are more than 20000 precompiled packages for Debian and the Ubuntu family, in the official repositories... but TIGCC and KTIGCC are not among them.
Of course, there are many unofficial repositories. The one for TIGCC and KTIGCC is repo.calcforge.org/ , which provides packages for Debian, Fedora and CentOS.
However, given that the Ubuntu family has mild compatibility with Debian, I'm definitely not sure that the precompiled Debian packages would work on a distro of the Ubuntu family.
Try it, but if that doesn't work (missing dependencies, etc.), then one of us will have to compile the program for you, on the same Xubuntu as you have (version 8.04 ?)...


(oh, and BTW, we need to contact Romain: the KTIGCC deb has disappeared from the Calcforge Debian repository !)

Yes, you have to edit the PATH because TIGCC installs itself in a non-standard location, and doesn't put a symbolic link (roughly, shortcut in the Windows world) in /usr/local/bin.
Put
"
export TIGCC=/usr/local/tigcc
export PATH=$PATH:$TIGCC/bin
"
in your ~/.bashrc ( /home/[whateverusernameyouchose]/.bashrc) file, so that these lines are automatically executed


> I like to have the interface to be able to edit stuff with.
For editing, there are plenty of syntax-coloring text editors. I don't know what Xubuntu provides by default (maybe the limited Gedit ?), but I use SciTE and KWrite/Kate.
But syntax-coloring text editors won't build a project or transfer the file to the calculator in a single click / keypress...


In the package manager (or whatever its name in the XFCE menus), which is usually Synaptic (at least, that's what the Ubuntu 7.10 users at work use), you have to enable the repo.calcforge.org repository.
I've put a screenshot for Synaptic (the most user-friendly one, IMO) at img126.imageshack.us/my.p...ccovb2.png :
* the URI is a base in the filesystem of the repo.calcforge.org repository;
* the distribution is "stable", i.e. the packages are intended to be used with Debian stable (Debian 4.0 currently);
* the categories are main and non-free, to indicate different licensing schemes (the packages in non-free have less permissive licenses than the packages in main).


[EDIT: forgot the link]

Compiling KTIGCC requires a number of KDE/Qt development packages (and their transitive dependencies). qt3-dev-tools, libqt3-headers, libqt3-mt-dev are a good list to start with, but probably incomplete.
In any case, having the build-essential package won't hurt.

> This starting of programs from the terminal is interesting, something I'm definitely not used to at least.
Although it's (perhaps counter-intuitively) often faster starting the program from a terminal than going through the menus, you definitely don't _have to_ start programs from the terminal.
If the packages don't provide menu entries (many do), you should send feature requests to the developers

For more than a year, I've been used to starting, in the same Konsole window, as many terminals as can fit on the screen without scrolling the terminal list - that is, 9 on my older computer and 10 on this one.
I don't use all of them everyday, but most of them point to the folders I'm currently using for a longer period of time. The couple spare sessions are used for temporary work in other folders.

> I don't understand a lot about it other than searching and installing
Well, most of the time, there's little else you need to worry about

> the ./configure command is saying that I have got an error in the configure file and that's quite strange
You should post the error, we could help you more easily this way