Albert J. Wong wrote:
> What is @loader_path relative off of?
@loader_path is the directory that contains whatever is being loaded.
While loading the main executable, @loader_path is equivalent to
@executable_path.
If your three dylibs refer to one another and are always in the same
directory,
http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man1/dyld.1.html
sorta "relative to the thing loading this"
TVL
On Wed, Oct 7, 2009 at 3:52 PM, Albert J. Wong (王重傑) wrote:
> What is @loader_path relative off of?
>
>
> On Wed, Oct 7, 2009 at 12:35 PM, Mark Mentovai
What is @loader_path relative off of?
On Wed, Oct 7, 2009 at 12:35 PM, Mark Mentovai wrote:
> My preference would be to place them inside Chromium
> Framework.framework, then. If you need to, you can put them inside
> Chromium Helper.app/Contents/MacOS instead, but I'm trying really hard
> to m
My preference would be to place them inside Chromium
Framework.framework, then. If you need to, you can put them inside
Chromium Helper.app/Contents/MacOS instead, but I'm trying really hard
to minimize the amount of "stuff" inside the app and the helper app.
You can get the framework as a bundl
On Wed, Oct 7, 2009 at 12:17 PM, Mark Mentovai wrote:
>
> Which processes need to load these libraries?
>
Render process.
> Are these libraries loaded at launch time or by dlopen?
>
dlopen()
>
> Mark
>
> >
>
--~--~-~--~~~---~--~~
Chromium Developers mailing
Which processes need to load these libraries?
Are these libraries loaded at launch time or by dlopen?
Mark
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://grou
Mark is probably the one to best answer a suggestion here. I'm assuming
they also need to be handled in a version fashion with the app, yes?
TVL
On Wed, Oct 7, 2009 at 2:36 PM, Andrew Scherkus wrote:
> On Wed, Oct 7, 2009 at 11:34 AM, Albert J. Wong (王重傑) > wrote:
>
>> We just noticed that the
On Wed, Oct 7, 2009 at 11:36 AM, Andrew Scherkus wrote:
> On Wed, Oct 7, 2009 at 11:34 AM, Albert J. Wong (王重傑) > wrote:
>
>> We just noticed that the Chromium Helper.app cannot locate the ffmpeg
>> binaries (libav*.dylib) in Mac Chromium. This leads to the video feature
>> being disabled. :(
>>
On Wed, Oct 7, 2009 at 11:34 AM, Albert J. Wong (王重傑)
wrote:
> We just noticed that the Chromium Helper.app cannot locate the ffmpeg
> binaries (libav*.dylib) in Mac Chromium. This leads to the video feature
> being disabled. :(
> Where should the ffmpeg binaries go? Should they be put alongside
