On Wednesday 11 December 2002 00:16, Cserna Zsolt wrote: > Hi! > > I'm writting because I cannot compile my libggi using application > statically. > > The compile command was: > gcc -Wall -static -o mpointexample mpointexample.c -L/usr/lib -lggi > -I/usr/include -lm -v > > (-lm for math) > > The error message: > /usr/bin/ld: cannot find -lggi > > This means no libggi.a was found in /usr/lib. But the debian package > doesn't contains "libggi.a".. > > (sorry for my english :) > > Thanks, > > Zsolt Cserna > > ps: I'm using debian sid (last year's "edition", from cd.. :)
Also hi, my english isn't better ... ;-) Currently there is no provision whatsoever to use any libggi(/any GGI library?) as a static library, sorry. This is an open issue, that should generally be solved but it isn't yet. In general it seems at first glance quite pointless to even try to use libggi statically. Libgg and libggi would actually be linked into your binary, but every other module like display targets, etc. will be loaded at runtime. Besides verifying your interface to libgg and libggi there is no gain to be had when linking static for debugging purposes. There are other scenarios where it would actually be helpful to be able to build binaries that include the libraries and the modules used. Debian has other requirements to demand statically linkable libraries, currently libggi breaks this rule deliberately and as a consequence has to deal with a sticky 'Release-critical' bug report. Please tell the GGI Project why you need that, may be it will get them going ;-) I Cc'd this mail to [EMAIL PROTECTED], the mailing list of the GGI project. Try to return matters of general interest to them, but i assume that you must be a member of the list to write to it. Feel free to mail me, you're welcome. Thanks, martin
