Re: [SPAM] Re: How to create a self contained GTK+ Application for Linux
Michael Ekstrand wrote: You might want to take a look at what the autopackage folks are doing. At the very least, they have a lot of documentation on what's required to prepare relocatable, portable binary packages. Anyway the GTK hardcoded path are not a good thing IMHO. With some care and the use of -rpath linker option and LD_LIBRARY_PATH you can ship linux binaries using a wide library range. I've shipped a commercial game with ogre, cegui, sdl, devil, boost, libjpeg/png/tiff, libstdc++ and other stuff, but the installer (loki) that use GTK, should stay compatibile with gtk 2.0.x and gtk 1.2.x (there are two versions) cause there is no reliable way to ship gtk statically linked or in a particular path (for the installer for instance a CDROM relative path). Having relative paths in the gtk core libraries what problem could cause? In windows paths are relative so I suppose this could work also on linux, maybe there will be some rework in the autoconf/make scripts at most :) Eg make libgtk-2.0.so try to load: ./gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so Instead of: /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so Bye, Gabry ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: [SPAM] Re: How to create a self contained GTK+ Application for Linux
On Wed, May 23, 2007 at 06:36:09PM +0200, Gabriele Greco wrote: Michael Ekstrand wrote: You might want to take a look at what the autopackage folks are doing. At the very least, they have a lot of documentation on what's required to prepare relocatable, portable binary packages. Anyway the GTK hardcoded path are not a good thing IMHO. Well, Pango for instance uses environment variables to tell it where config files telling it where other files specifing where its modules reside. Isn't it enough? Having relative paths in the gtk core libraries what problem could cause? AFAIK you can relocate a Gtk+ installation using a combination of environment variables and config files. This way you can also relocate different things into different places. Not that I ever found any use for it... Eg make libgtk-2.0.so try to load: ./gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so Instead of: /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so And the dot is exactly what? The current directory? Does the library know the directory it was loaded from? Should libraries break when symlinked? Yeti -- http://gwyddion.net/ ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: [SPAM] Re: How to create a self contained GTK+ Application for Linux
On Wed, 2007-05-23 at 19:31 +0200, David Nečas (Yeti) wrote: And the dot is exactly what? The current directory? Yes Does the library know the directory it was loaded from? It should, yes. If it really does, I have no idea. Should libraries break when symlinked? No. Why would and should they? One of the few advantages that GTK on windows has over linux is that the entire GTK installation can be self-contained and moved around. Everything is found relative to the dlls automagically. Is this even possible to do in Linux? Yeti -- http://gwyddion.net/ ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
