Vcomponents in Mach-O Package

[Ruslan Zasukhin]

On 12/21/05 12:07 AM, "Dave Addey" <listmail1 at dsl.pipex.com> wrote:

Hi Dave,

>> Well, it is not hard, we have script for this..
> 
> It would be very nice if the MACHO version of the components could be a true
> Framework.  This seems to be the recommended way to bundle together all of
> the elements of something like VComponents.  The VComponents.framework could
> then live in the application bundle, for example:
> 
> /Contents/Frameworks/VComponents.framework

No it is as:

    /Contents/VComponents


> A development computer could also have the framework installed in
> /Library/Frameworks/ to make it available to all applications.

Instead we go into /usr/local/lib



> If the MACHO build *isn't* a true Framework, the Vcomponent files should
> still go in /Contents/Frameworks/ when they are included in the application
> bundle.  I'd suggest that the @executable_path linker fix should *always*
> look in this location first.

    /Contents/VComponents


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]