Summary: | configure --with-drivers=x11,x11alpha fails to build | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Russ Cox <rsc> |
Component: | Build Process | Assignee: | Chris Liddell (chrisl) <chris.liddell> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | htl10 |
Priority: | P4 | Keywords: | bountiable |
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- |
Description
Russ Cox
2007-11-03 08:55:59 UTC
Bug #1: There is a conflict between the two systems here. The output devices that depend on third party library support enable themselves if the libraries are available, and this list isn't merged/clipped with the list of devices requested by --with-drivers. Bug #2 should just be fixed by duplicating the colour mapping code inside gdevomni.c. Hmm, ./configure seems to have been totally re-worked. Now --with-drivers=x11,x11alpha seems to be ignored and just build to every device. Grabbing a Ralph's bugs. With r11461, ./configure --with-drivers=x11,x11alpha finishes building, bin/gs -h bbox cups ijs nullpage png16 png16m png256 png48 pngalpha pnggray pngmono svg x11 x11 x11alpha x11alpha x11cmyk x11cmyk2 x11cmyk4 x11cmyk8 x11gray2 x11gray4 x11mono x11rg16x x11rg32x bbox, nullpage are fairly essential and always there; We provide --disable-cups and --without-ijs so cups and ijs are probably considered "enabled by default" unless requested otherwise. Therefore the remaining issue is why svg and the png* devices are built, and whether they should. i.e. either document or hint that they are enabled by default, or disable them when not explicitly/implicitly requested. Re-assigning bugs which still have work to do. Both problems fixed in r12025. |