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 bundle from mac_util::MainAppBundle()
since r28262.
If you put the dylibs in the framework and they depend on one another,
you may need to switch them to refer to each other using @loader_path
instead of @executable_path.
Mark
scherkus wrote:
> On Wed, Oct 7, 2009 at 12:17 PM, Mark Mentovai <m...@chromium.org> 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 list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
