Hi,
On Tue, November 14, 2006 12:28, LENHOF Jean-Yves said:
I saw on this page that there are about three ways to compile amaya
http://www.w3.org/Amaya/User/Autoconf.html
Compiling with GTK+ seems not so interesting because of the SVG
support...
AFAIK, SVG support is independant from the toolkit used.
But for now as I've seen on the debian rules file, amaya is compiled
with this option :
--with-wx --with-gl
Perhaps compiling with this option :
--with-wx
and choosing to link against mesa instead of opengl will make the
problem vanish...
What this option (or the lack of using it) actually does, is build the
whole Mesa in full software rendering mode and statically link against it.
It means the package would have to include the Mesa source code, which
would have to be rebuilt on every single arch.
I really don't plan to track bug and security fixes in a software as
tricky as Mesa, especially when it would be duplicated work, when the
source is a 2 year old snapshot, and I don't actually have time to do it.
Doing this would also mean that nobody would benefit from OpenGL hardware
acceleration at all.
So I'm not very inclined to go for this solution. I would rather link
statically against libgl1-mesa-swx11, which would give the same result,
with less code to maintain and build, but would only be slightly less bad,
as I would still have to track every important bug or security fix in Mesa
to trigger a rebuild of the package.
Regis
