On Wed, 2007-05-23 at 15:12 -0700, Daniel Yek wrote:
> (Sorry for being busy-body here...; and keep in mind that I might have not
> read up the thread messages in details.)
No more than the rest of us. :)
>
> If it is to the executable path, it is easier -- by reading the symbolic
> link targe
On Wed, 2007-05-23 at 23:44 +0200, David Nečas (Yeti) wrote:
> The current [working] directory is what getwd() returns.
> At least that's what everyone else seems to mean by the
> current directory.
Well obviously getpwd is not good enough, then. What would be needed is
the directory the .so file
At 02:44 PM 5/23/2007, David =?iso-8859-2?B?TmXoYXMgKFlldGkp?= wrote:
>On Wed, May 23, 2007 at 03:12:54PM -0600, Michael L Torrie wrote:
> > The current directory as defined by the
> > directory the gtk dlls are in, yes.
>
>The current [working] directory is what getwd() returns.
>At least that's
On Wed, May 23, 2007 at 03:12:54PM -0600, Michael L Torrie wrote:
>
> Typical unix pedantic response.
I asked specifically what you meant because it sounded
ridiculous.
> The current directory as defined by the
> directory the gtk dlls are in, yes.
The current [working] directory is what getwd(
On Wed, 2007-05-23 at 23:07 +0200, David Nečas (Yeti) wrote:
> The current directory can be anything. Particularly
> anything unrelated to the location to the components of the
> application. Do you really think it's a good idea to make
> programs work or break depending on something so arbitrary
On Wed, May 23, 2007 at 02:08:35PM -0600, Michael L Torrie wrote:
> On Wed, 2007-05-23 at 19:31 +0200, David Nečas (Yeti) wrote:
> > And the dot is exactly what? The current directory?
>
> Yes
The current directory can be anything. Particularly
anything unrelated to the location to the componen
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 shou
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.
> >
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
On Wed, 2007-05-23 at 15:07 +, Jeremy Roberson wrote:
> Hardcoded paths might be okay initially but I need to come up with a more
> dynamic solution but, I'm not sure there is one.
You might want to take a look at what the autopackage folks are doing.
At the very least, they have a lot of docu
David Nečas (Yeti physics.muni.cz> writes:
>This can probably work for simple scripts,
> but don't try it with Gtk+ unless you have a very good idea
> what to put to the RUBYSCRIPT2EXE.* variables (which
> essentially amounts to manual packaging).
>
> And of course Tor's point about hardcoded pa
Tor Lillqvist iki.fi> writes:
>
> Off the top of my head, one obvious thing that will depend on run-time
> opening of files is the gdk-pixbuf loaders. Plus message catalogs, of
> course, but maybe American English is enough for all your users?
>
> --tml
>
Ya, I just realized that when I could
On Wed, May 23, 2007 at 12:52:23PM +0300, Alan Lake wrote:
> 1. I write in Ruby, so I am able to use RubyScript2exe.rb to create
> a self-contained GTK+ application.
RubyScript2Exe monitors the execution of your application.
This is done by running your application with a special
librar
Here are a couple of off-beat suggestions:
1. I write in Ruby, so I am able to use RubyScript2exe.rb to create
a self-contained GTK+ application.
2. If your users can run virtual machines such as VMware, you can
give them your app in a virtual machine that runs a later version of Linux.
On Tue, 2007-05-22 at 20:29 +, Jeremy Roberson wrote:
> The majority of our clients are using custom Linux Distributions and they are
> using older versions of GTK+. Our application depends on features available
> in
> GTK+ >= 2.10 so, I need to figure out how to distribute the application wi
Hey Jeremy,
On Wed, 23 May 2007 06:54:14 +0300 Tor Lillqvist wrote:
> Jeremy Roberson writes:
> > So, I copied all of the shared libraries into a sub directory of
> > the application directory called "lib/" for testing.
>
> But GTK+ and Pango also look for various other files at run-time. It's
Jeremy Roberson writes:
> So, I copied all of the shared libraries into a sub directory of
> the application directory called "lib/" for testing.
But GTK+ and Pango also look for various other files at run-time. It's
not just the shared libraries that are needed.
The pathnames of these other fi
Tristan Van Berkom gnome.org> writes:
>
> On Tue, 2007-05-22 at 20:29 +, Jeremy Roberson wrote:
> [...]
> > And I get a segmentation fault. I then tried ldd and gdb
and I get an instant
> > segmentation fault. If I unset the LD_LIBRARY_PATH
variable and then try ldd
> > and gdb, they wor
Tristan Van Berkom gnome.org> writes:
>
> On Tue, 2007-05-22 at 20:29 +, Jeremy Roberson wrote:
> [...]
> > And I get a segmentation fault. I then tried ldd and gdb and I
get an instant
> > segmentation fault. If I unset the LD_LIBRARY_PATH variable and
then try ldd
> > and gdb, they wor
On 5/22/07, Jeremy Roberson <[EMAIL PROTECTED]> wrote:
> The majority of our clients are using custom Linux Distributions and they are
> using older versions of GTK+. Our application depends on features available
> in
> GTK+ >= 2.10 so, I need to figure out how to distribute the application with
On Tue, 2007-05-22 at 20:29 +, Jeremy Roberson wrote:
[...]
> And I get a segmentation fault. I then tried ldd and gdb and I get an instant
> segmentation fault. If I unset the LD_LIBRARY_PATH variable and then try ldd
> and gdb, they work but the application fails because it's linking agains
The majority of our clients are using custom Linux Distributions and they are
using older versions of GTK+. Our application depends on features available in
GTK+ >= 2.10 so, I need to figure out how to distribute the application with all
of its dependencies.
So, I used ldd to determine all of t
22 matches
Mail list logo