[DeveloperX]

Ok, I absolutely hate this f**king piece of software!
To make a measly 'Simple KDE Application' displaying a "Hello World" string on a window, this damn program took 45 minutes to build the project, and then 2 minutes to execute the built project executable.
I checked the project directory, and its 7MB!!!!!! 98 Files for a f**king hello world program!

Is there a better linux project development tool out there? Or is there a way to make KDevelop ONLY generate the files I want? (*.cpp, *.h, executable binary)

Please, someone out there who builds anything on a linux platform has to know something I don't here, please offer up your advice. (No flamewars about this post, please.)

I cannot afford to waste 45 minutes to build a hello world project, much less waste 7MB of harddrive space on a test-application.
Thank GOD I didnt tell it to build a full-blown application framework project.....I dread that thought.

Anyone know any linux game programming tutorials? And how DO you get allegro up and running on linux?? I cannot seem to get it working..I installed an rpm for allegro, and tried to compile a simple test, using gcc.......noluck. :\

Bjorn, I know you're a linux user, share your secrets of success, please.
_________________
Principal Software Architect
Rambling Indie Games, LLC

See my professional portfolio

[DrunkenCoder]

I belive code::blocks is available else Anjuta is quite nice.
_________________
If there's life after death there is no death, if there's no death we never live. | ENTP

[LeoDraco]

I am a little confused about exactly what you want; are you attempting to write some sort of console based application? (I don't think this is what you are attempting, but...) If that is the case, a simple text editor and a console is all you need. Open Vi/Emacs (whatever your preference) and write your c++ source; then, in another tab/editor/etc. write a Makefile to automate your build instructions. This will be (relatively) hairy at first, but you will fast loose interest in IDEs after a few goes at it. Then, from your console, simply type "make" in the directory containing your source/Makefile, and you should be in business.

As I don't use Allegro, I cannot be entirely helpful; however, are you sure you are linking in the library correctly? When linking libraries with gcc (assuming that the library binary is installed in the paths that gcc checks), you would simply have to include the flag "-llibname"; this would probably be something like "-lallegro". (But, as I don't use Allegro, it might be more difficult than that...)

Edit: Also, keep in mind that most applications in Linux come with man/info pages, which are actually quite helpful for figuring out how to use the systems. For the more graphical applications, I'm pretty sure the distro's/maintainers do a fair job of including good documentation. Consulting the help files, man/info pages, etc. is always a good idea...
_________________
"...LeoDraco is a pompus git..." -- Mandrake

[DeveloperX]

[LeoDraco]

When you installed the allegro rpm, did you just install the allegro rpm, or did you also install the allegro-devel rpm? Many libraries packaged in rpm separate the .so's from the development files, which, obviously, would be packaged in the *-devel rpms. So, if you have not done that, my suggestion would be to attempt it. (I bring this up as the download page for the allegro sourceforge site lists separate packages. This is probably not an issue if you got a source rpm.)

edit: also! unless you grabbed the rpm from your distro's package management app (something like yum; I'm not familiar with SUSE, but maybe YaST?), you might have aquired an rpm that was not built intentionally for your distro. While this might not (always) be a problem, not all rpm-based distro's have the same directory hierarchy nor the same naming conventions.

edit2: After another brief search, I came across these notes regarding the linux version of allegro. They might be helpful to you.
_________________
"...LeoDraco is a pompus git..." -- Mandrake

[Rainer Deyke]

How to install just about anything on Linux or any other UNIX-like environment:

• Grab the source distro and unpack it somewhere.
  
• Enter the directory where you unpacked the source.
  
• Run ./configure.
  
• Run make.
  
• Run make install as root.
  
• Optionally delete the unpacked directory, as it is no longer needed.

[Bjorn]

[Mandrake]

Open up a terminal shell. Type in GCC. Lookie there! It's the exact same C/C++ you were probably using on Windows (if you were using MingW or Dev-Cpp) and it's the HEART of the Linux OS.

You don't need anything else.

Make is simple and efficient. But, if you can't handle a command line, you should stop using Linux. Hell, you should stop programming all together. A programmer should be familiar with his compiler, in fact, he should know his compiler inside and out. He should make love to his compiler, and never cheat on it. And, if he gets into a fight with his compiler, he should go cool off and have a smoke, becuase, after all, a compiler doesn't make mistakes.

End rant.

But yeah, if you want to make an allegro game, ignore KDevelop. Check to see if the right stuff is in the usr/local/bin and usr/local /includes. Make sure you have the LATEST bleeding edge WIP for that platform. Don't use RPM's, just use the classic tar.gz, unzip and untar it and then just do make install like you did on windows.

If you did the RPM, uninstall whatever it setup <before> you untar and unzip. I've only used the zip distros, and never had a problem with them installing properly. Note of warning, some allegro add-on libraries aren't too Linux (or OSX either) compatible. Another word of warning- Most Linux users don't have Allegro installed, so anyone that uses a program you make will have to go through extra steps to install it. Some Linux users hate this, and perfer to only use what comes with their distro.

I would suggest (if you want a system that will create one binary that can move across multiple OS's, rather than recompiling on each OS wondering if it will even work) to either use Java or target an emulator (like GBA, GBC, NES, SNES TG-16, etc).

Also, learn how to use make or a make like tool (like jam). It's a nice little idea that completely automates what you need.
_________________
"Well, last time I flicked on a lighter, I'm pretty sure I didn't create a black hole."-
Xmark

http://pauljessup.com

[DeveloperX]

[Mandrake]

There is a problem with the allegro RPM- it doesn't create a proper symlink for the .so file.
_________________
"Well, last time I flicked on a lighter, I'm pretty sure I didn't create a black hole."-
Xmark

http://pauljessup.com

[DeveloperX]

[DeveloperX]

[DeveloperX]

[Mandrake]

[DeveloperX]