Allegro project template for KDevelop

Allegro project template for KDevelop

HoHo

Member #4,534

April 2004

As I reported here I hacked together an Allegro project template for KDevelop.

Installation goes like this:
Put allegro.tar.gz and allegro.png into kdevappwizard/ (*)
allegro.kdevtemplate into kdevappwizard/templates

(*) It seems like this directory location might not be standard. Mine is in usr/share/apps/kdevappwizard but it might also be in $KDEDIR/share/apps/kdevappwizard/
It should also be possible to install them in $HOME/.kde/share/apps/kdevappwizard

I used this as a reference.

It still requires "#make distclean" when changing between build configurations. Also it needs "#libtoolize --copy --force" but I think this is a problem with my setup.

Any help is appreciated.

[edit]

Replaced the default generated main.c with slightly edited exhello.c (defaults to windowed mode) and added a new screenshot

[edit2]

Removed attatchment, see later posts for newer versions

__________
In theory, there is no difference between theory and practice. But, in practice, there is - Jan L.A. van de Snepscheut
MMORPG's...Many Men Online Role Playing Girls - Radagar
"Is Java REALLY slower? Does STL really bloat your exes? Find out with your friendly host, HoHo, and his benchmarking machine!" - Jakub Wasilewski

CGamesPlay

Member #2,559

July 2002

libtoolize --copy --force, I BELIEVE (not sure), simpyl creates some empty text files needed to have a "GNU-style" project. These are, for instance, NEWS, AUTHORS, and ChangeLog. make distclean is needed because you aren't settings a build dir properly -- that is, you are using the project as the build directory.

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

HoHo

Member #4,534

April 2004

Quote:

make distclean is needed because you aren't settings a build dir properly -- that is, you are using the project as the build directory.

Any ideas how to fix this? It was said in wiki that it is needed to be done.

[edit]

Quote:

libtoolize --copy --force, I BELIEVE (not sure), simpyl creates some empty text files needed to have a "GNU-style" project. These are, for instance, NEWS, AUTHORS, and ChangeLog.

Actually it does something different.

libtoolize --help said that it "Prepares a package to use libtool."

When checking the diff of two folders there are three files with big changes:
ltmain.sh
config.guess
config.sub

I think the problem comes from that kdevelop uses some older version of libtool(or autotoolset?) but in my system I have a later version.

In ltmain.sh I found this:
in default:

Constants.

PROGRAM=ltmain.sh
PACKAGE=libtool
VERSION=1.5a
TIMESTAMP=" (1.1240 2003/06/26 06:55:19)"

in libtoolized one:
PROGRAM=ltmain.sh
PACKAGE=libtool
VERSION=1.5.18
TIMESTAMP=" (1.1220.2.246 2005/05/16 10:00:18)"

[edit]
Updated the C template a little and added C++ template(attatched).
Installing is a little easier too. Just extract the given .tar.gz into kdevappwizard folder (e.g usr/share/apps/kdevappwizard).

CGamesPlay

Member #2,559

July 2002

Forgot about this thread

./configure --builddir=debug to use the debug directory for makefiles and object files
./configure --builddir=optimized for optimized for Makefiles and object files.

You can request a specific version of autotools be invoked. You most likely have 2 on your system. Just address it by its full name, including a version number. (major/minor, no revision)

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>