| Summary: | Allegro 4.2.0 released! | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael Färber <01mf02> |
| Component: | [OLD] Games | Assignee: | Gentoo Games <games> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | millimillenary, siarhei.siamashka |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Allegro 4.2.0 Ebuild
Updated ebuild. default to use shared library, even when USE=static. |
||
|
Description
Michael Färber
2005-11-08 10:40:51 UTC
Created attachment 72459 [details]
Allegro 4.2.0 Ebuild
I have one question: There is a line
# $Header: /var/cvsroot/gentoo-x86/media-libs/allegro/allegro-4.1.18.ebuild,v
1ld,v 1.4 2005/08/29 03:28:47 mr_bones_ Exp $
Do I have to modify this line or do I have to add a new line, or what shall I
do with this?
Created attachment 72473 [details]
Updated ebuild.
Hi,
I've just added a few use flags to the previous ebuild: debug, profile, conly.
The 'debug' and 'profile' flags only compile the debug and profiling versions
of the library, and not the example programs.
What's a bit annoying is that you need to add FEATURES=nostrip for the
debugging library, causing the normal library to not be stripped.
The 'conly' flag disables the use of asm code. I made it this way so that asm
was enabled by default, but this makes its a little ugly.
Cool! Now my question is - when will this be introduced to the official Portage tree? Oh, I didn't want to be rude, I just feared that nobody was interested in this because in the Bugzilla system of other projects there usually were comments from developers that somebody would have a look at this, but this doesn't seem to be the case here ... Anyway, I will not ask for a date anymore ;-) Over here, if we don't RESOLVED-WONTFIX, RESOLVED-CANTFIX, or RESOLVED-LATER it, then it means we'll eventually get to it. The main thing is interest and manpower. Created attachment 72913 [details, diff]
default to use shared library, even when USE=static.
I found that when you compile with "USE=static", which compiles both shared and
static libraries, programs are linked to the static library by default due line
50: $(use_enable static staticprog).
I think that normally the shared library should be used, and when it comes to
distributing something statically linked, you link your project with
`allegro-config --libs --static` yourself.
Alternatively, we could add another use flag and let the user select their
preferred behaviour.
I prefer the 1st option, which is what the patch does.
version bumped a while ago. Thanks for report Shared library comment applyed, Thanks for solution |
