Configure Paladin to work with Allegro

Forum thread started by fog76 on Mon, 2010-10-04 07:41

Hi boys,
i need a little help... I installed Allegro lib on Haiku (by LibPack) + Paladin. But i can not set Paladin to compile simple Allegro test. Paladin can not find the library, but allegro-config work fine.

How do I set the parameters of the project necessary to use the libraries (Allegro)?

Thanks,
fog76.

‹ News update WiFi Configuration tool, Drivers, and Dell Latitude 2100 ›

Comments

Re: Configure Paladin to work with Allegro

by humdinger - 2010-10-05 12:52

Hi fog76!
You can set additional libraries from Paladin's menu Project | Change System Libraries...
I think that should find all available libs on the system.

Regards,
Humdinger

Re: Configure Paladin to work with Allegro

by fog76 - 2010-10-07 14:19

Hi Humdinger,
i just set the libraries, and compile. But ld return this error:

/boot/develop/abi/x86/gcc2/tools/gcc-2.95.3-haiku-100420/i586-pc-haiku/bin/ld: cannot find -lalleg.so.4.4
collect2: ld returned 1 exit status

In systems Libraries i have selected liballeg.so.4.4.1, if i select liballeg.so.4.4, ld return: cannot find -lalleg.so.4

Regards,
fog76.

Re: Configure Paladin to work with Allegro

by kvdman - 2010-10-07 15:19

this may or may not work. make a symlink of liballeg.so.4.4 to the same directory, rename the symlink to lalleg.so.4

Re: Configure Paladin to work with Allegro

by humdinger - 2010-10-07 18:04

Sorry I can't help with that... Maybe you can contact the person doing the Allegro port. It seems like that port wasn't intended for the Haiku version you're running (revision x, with gcc2?, gcc4?, hybrid?) or it wasn't installed properly...

Regards,
Humdinger

Re: Configure Paladin to work with Allegro

by scottmc - 2010-10-08 00:04
There's now a gcc2 and a gcc4 build of allegro available: http://ports-space.haiku-files.org//?directory=./&search=allegro See if either of those fixes your problems.

Re: Configure Paladin to work with Allegro

by darkwyrm - 2010-10-08 23:50

You may also want to try running Paladin from the command line with the -d switch and then attempting a build. This enables debug output and may be of use to you in what it's doing. It would be a good way to rule out Paladin causing the trouble.