Small C/C++ IDE needed

marquisor · 10-04-2010, 12:28 PM

hello everyone!

i'm learning C now, later C++. using DJGPP isn't so nice on MS-DOS yet, no LFNs etc. and other limitations that is only one terminal, no multitasking etc.

question:

is there a small IDE for linux console? (i'm using a celeron 333 atm). for C it would be sufficient i guess?
what i would need is a wide documentation, help on .h files, includes etc.
on MS-DOS i use RHIDE. something similar is appreciated.

later on i might use eclipse or code::blocks. read another thread about c/c++ IDE suggestions here yet, but that's too much i think for getting started.

thx for answers

regards
marquisor

PS: i don't like vi, elvis and other derivates. my favourite is jed. but if no way around, then i have to learn how to control vi *sigh*

w7hd · 10-04-2010, 12:35 PM

I use Anjuta. It has a very nice interface and is easy to use. It is a lot like RHIDE.

Tinkster · 10-04-2010, 12:37 PM

Quote:

Originally Posted by w7hd

I use Anjuta. It has a very nice interface and is easy to use. It is a lot like RHIDE.

Except for being tied tightly to Gnome, which makes
it rather fat IMNSHO.

Cheers,
Tink

P.S.: OP, I moved your thread to programming, and would like
to point you at the sticky at the top of this forum.

CapnStank · 10-04-2010, 12:38 PM

I personally found emacs easier to pick up if you're forced to run using the command line. Other than that eclipse is a bit heavier but definitely worth it since it helps along with dependencies and other things for new coders.

TobiSGD · 10-04-2010, 12:39 PM

Learning vi is not so difficult at all. But maybe this http://www.pegasoft.ca/tia.html is the right one for you. Besides other programming languages there is support for C and C++.

marquisor · 10-04-2010, 12:46 PM

i read much about emacs. how far is this a standard? other derivates, clones, editors with same controls, keyboard shortcuts, handling?
i don't wanna "try" vi, emacs, elvis, vim etc. alltogether.
what if i would have to stick to ONE of them, what is recommended for coding?
i think i'll swallow the bitter pill and get used to emacs. or is that going to be replaced by more modern, user-friendly editors soon?
what do i have to install exactly on slackware 13.1 to get an emacs IDE running on console?

@Tinkster: sorry didn't see the sticky thread there. good stuff. but also very much for a beginner

the gnome issue yes..

i read about kdevelop is dependent on kde stuff and so on. an ide without any dependencies would be best for me, as i want to have my code portable as possible, that mostly will be other windowmanagers?! MS-DOS, Windows and maybe 68k machines.

@TobiSGD: looks good, maybe i give it a go.

Sergei Steshenko · 10-04-2010, 12:59 PM

A nice lightweight editor is 'nano'.

Linux boxes allow to install manpages, so help on header files and standard functions is available through 'man' command. For example:

Code:

sergei@amdam2:~> man -k stdio.h
stdio.h (0p)         - standard buffered input/output

, so then

[CODE]sergei@amdam2:~> man stdio.h

Or:

Code:

sergei@amdam2:~> man printf
Man: find all matching manual pages
 * printf (1)
   printf (3)
   printf (1p)
   printf (3p)
Man: What manual page do you want?

, then choose 3 . If you do not know what to choose, try one by one.

The bottom line: why do you need an IDE in the first place ?

marquisor · 10-04-2010, 01:29 PM

Quote:

Originally Posted by Sergei Steshenko

A nice lightweight editor is 'nano'.

Linux boxes allow to install manpages, so help on header files and standard functions is available through 'man' command. For example:

Code:

sergei@amdam2:~> man -k stdio.h
stdio.h (0p)         - standard buffered input/output

...

The bottom line: why do you need an IDE in the first place ?

interesting! but where do i get those manpages? and how to install them?
are they part of some devel-packages?

ok, nano is on my slack here, but no syntax highlighting, integrated debugger which shows src-code line where the error is etc. therefore i want an IDE! or at least a capable editor with those features

ok wrote a small hello.c program in nano, saved, cc hello.c -o hello. and i'm done, yes...

TobiSGD · 10-04-2010, 01:38 PM

In Slackware you don't need devel-packages, development stuff is installed already with the "normal" packages. Manpages should also be installed if you install a package.

marquisor · 10-04-2010, 01:45 PM

Code:

root@slack333:~# man stdio.h
No manual entry for stdio.h

what packages are installed?
only have emacs:

Code:

root@slack333:~# slackpkg search emacs

Looking for emacs in package list. Please wait... DONE

The list below shows all packages with name matching "emacs".

[ installed ] - emacs-23.2-i486-1
[uninstalled] - emacspeak-ss-1.9.1-i386-1
[uninstalled] - emacspeak-32.0-i486-1

You can search specific files using "slackpkg file-search file".

GrapefruiTgirl · 10-04-2010, 01:49 PM

Code:

root@reactor: man -k stdio
DBD::Gofer::Transport::stream (3)  - DBD::Gofer transport for stdio streaming
DBD::Gofer::Transport::stream [] (3)  - DBD::Gofer transport for stdio streaming
__flbf []            (3)  - interfaces to stdio FILE structure
__fpending []        (3)  - interfaces to stdio FILE structure
__fpurge []          (3)  - interfaces to stdio FILE structure
__freadable []       (3)  - interfaces to stdio FILE structure
__freading []        (3)  - interfaces to stdio FILE structure
__fsetlocking []     (3)  - interfaces to stdio FILE structure
__fwritable []       (3)  - interfaces to stdio FILE structure
__fwriting []        (3)  - interfaces to stdio FILE structure
_fbufsize []         (3)  - interfaces to stdio FILE structure
_flushlbf []         (3)  - interfaces to stdio FILE structure
flockfile []         (3)  - lock FILE for stdio
ftrylockfile []      (3)  - lock FILE for stdio
funlockfile []       (3)  - lock FILE for stdio
getc_unlocked []     (3)  - non-locking stdio functions
getchar_unlocked []  (3)  - non-locking stdio functions
putc_unlocked []     (3)  - non-locking stdio functions
putchar_unlocked []  (3)  - non-locking stdio functions
stdio []             (3)  - standard input/output library functions
root@reactor:

Use man's -k (keyword) option to get all mentions of a particular keyword. The (3) indicates the page is in section (or chapter) 3 of the man pages. Most common pages are in section 8.

Try:

Code:

man stdio

Sergei Steshenko · 10-04-2010, 01:49 PM

Quote:

Originally Posted by marquisor

interesting! but where do i get those manpages? and how to install them?
...

It depends on your distro. It should have some kind of package manager, and the manager should have some kind of search function. Also, the website of your distro should have some info on packages.

One can run X on a 300MHz machine, and one can use in such a case some kind of light WEB browser, e.g. 'dillo'. The latter should be sufficient for simple sites like www.die.net - a lot manpages on it.

Sergei Steshenko · 10-04-2010, 01:53 PM

Quote:

Originally Posted by marquisor

... integrated debugger which shows src-code line where the error is etc. ...

Well, 'gdb' alone (at least, the last gdb-7.2) shows the source line with its number in case of segmentation fault.

Already mentioned Emacs (exists for both UNIXish OSes and Windows) has a pretty good integration with 'gdb', though I don't use Emacs.

marquisor · 10-04-2010, 02:09 PM

yes i think i stick with emacs. have to go to find some useful .pdfs for it to get into learning it...
some tips where/how should i startup with emacs? :/

rhide on ms-dos is very nice. i'm looking for sometehing similar for linux console. debug window, feature to evaluate expressions etc.

Tinkster · 10-04-2010, 05:00 PM

Silly question .. why don't you just use RHIDE under linux?
http://www.rhide.com/

Has Linux d/ls available.

Cheers,
Tink