Summary: | Add static library build to libgii | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pat Double <gentoo> |
Component: | New packages | Assignee: | Luca Barbato <lu_zero> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
libgii-0.9.0.ebuild.patch
libgii-0.9.0.ebuild.patch |
Description
Pat Double
2005-04-05 10:00:09 UTC
Created attachment 55376 [details, diff]
libgii-0.9.0.ebuild.patch
Adds static library supports based on the 'static' use flag.
Created attachment 55382 [details, diff]
libgii-0.9.0.ebuild.patch
Previous patch did not use 'static' use flag.
Chris, see my comment in libggi's bug which accelerator? The KQEMU accelerator. last time I checked it was a closed source kernel module. Please explain better I do not know exactly if it is the accelerator only or for also the 'qemu-fast' program. I do know when I tried to compile QEMU without the ebuild, including the KQEMU patches (which apply to the QEMU emulator to use the module besides the actual kernel module), I needed to have libgii and libggi static libraries. I had to roll my own libgii and libggi ebuilds to get the static libraries before I could continue compiling. This is just my particular need, but it seems reasonable that libraries that provide linking static versions in the upstream source build should also have that ability in the ebuild. DirectFB has similar support for building static libraries based on the 'static' use flag. you don't need libgii. get my ebuild for qemu-0.6.2_pre from my devspace |