. At runtime, it has to be in that same library, not
just somewhere in the linked higherarchy.
dan
--
Daniel Macks
dma...@netspace.org
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop
,
this caused more fallout than expected. Sorry about that.
How about calling it libvala-0.10 to emphasize that it's the *lib* not
vala itself?
dan
--
Daniel Macks
dma...@netspace.org
___
desktop-devel-list mailing list
desktop-devel-list
but doesn't specify direct link against it
and if there is a consensus on how other packages should handle it.
dan
--
Daniel Macks
dma...@netspace.org
http://www.netspace.org/~dmacks
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http
to make every official module with silent-rules by default.
Something like that, yeah. Feel free to write the Goal.
Sounds like http://live.gnome.org/GnomeGoals/NicerBuilds
dan
--
Daniel Macks
dma...@netspace.org
http://www.netspace.org/~dmacks
issued. Is there a way to hide
only the makefile portability warnings (rather than *all* portability
warnings)?
dan
--
Daniel Macks
dma...@netspace.org
http://www.netspace.org/~dmacks
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
many
shared libs is a packager nightmare.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list