Re: [gtk-osx-users] [gtk-mac-bundler] gtk3-demo oudated?
- From: Paolo Borelli <paolo borelli gmail com>
- To: John Ralls <jralls ceridwen us>
- Cc: gtk-osx-users-list gnome org, Nacho <nacho resa gmail com>
- Subject: Re: [gtk-osx-users] [gtk-mac-bundler] gtk3-demo oudated?
- Date: Sun, 16 Sep 2012 10:57:54 +0200
Just fyi we followed your advice of moving the helper binary to the
MacOS dir for now and things are working.
We also sent a github pull request for the modifications we made to the
bundler.
Ciao
Paolo
On Wed, 2012-09-12 at 08:37 +0200, Paolo Borelli wrote:
> On Tue, 2012-09-11 at 14:53 -0700, John Ralls wrote:
> > Where does it say that @executable_path is deprecated? It doesn't say anything about that in the dyld man page on Mountain Lion.
>
> Sorry, as I said I am new to osx, I found some forum post saying that it
> was deprecated, but now I cannot find a reliable page stating the same.
>
> Anyway my problem is that I have a main binary in
>
> /Contents/MacOS/myapp
>
> and a helper app that is spawned programmatically in
>
> /Contents/Resources/lib/helperapp
>
> and they both use gtk. If @executable_path is used in a configuration
> file like gdk-pixbuf.loaders then it cannot work for both those
> binaries, because it is relative to the executables and they are in
> different directories. If the file was relative to the gdk-pixbuf
> library itself the file wold be always correct.
>
>
> This is also where my tangential pointer to the win32 port came from: if
> the the pixbuf loaders were loaded from a path relative to the
> gdk-pixbuf.dylib binary, then the gdk-pixbuf.loaders file would not be
> needed at all, removing the issue at the origin.
>
>
> Ciao
> Paolo
>
>
>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]