Bug 814375 - allegro-config executable is not included into any of allegro5 packages.
allegro-config executable is not included into any of allegro5 packages.
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: allegro5 (Show other bugs)
16
Unspecified Linux
unspecified Severity medium
: ---
: ---
Assigned To: Brandon McCaig
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-19 13:48 EDT by Paul
Modified: 2012-04-19 15:49 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-19 15:15:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Result of yum whatprovides. (638 bytes, text/plain)
2012-04-19 13:48 EDT, Paul
no flags Details

  None (edit)
Description Paul 2012-04-19 13:48:05 EDT
Created attachment 578724 [details]
Result of yum whatprovides.

This command can't be found in neither in bash nor manually in the file system. The "yum whatprovides */allegro-config" command points only allegro-devel-4.4.x.x packages. It's confirmed on both F16 and F17.
Comment 1 Brandon McCaig 2012-04-19 15:15:12 EDT
The allegro-config tool is specific to Allegro 4. Allegro 5 no longer uses a custom tool to retrieve compiler and linker flags. Allegro 5 now uses pkg-config, which is a general purpose utility with a similar function.

This should get you started:

gcc -Wall main.c `pkg-config --cflags --libs allegro-5.0 allegro_image-5.0`
Comment 2 Paul 2012-04-19 15:49:05 EDT
I should have checked that first, but I was certain that I was referring to official manual for allegro 5. Sorry for mistake.

Note You need to log in before you can comment on or make changes to this bug.