realbasic-plugins
[Top] [All Lists]

Re: Incorporating existing C/C++ libraries into an RB Project. . .?

To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com>
Subject: Re: Incorporating existing C/C++ libraries into an RB Project. . .?
From: Norman Palardy <npalardy at great-white-software dot com>
Date: Mon, 30 Jul 2007 11:28:30 -0600
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-plugins at lists dot realsoftware dot com
References: <C2D3BCE5 dot B5A40%listmail1 at dsl dot pipex dot com> <A0EAE12C-55F9-4E67-B8AA-8F1DAE74235A at mgreg dot com> <EE292F6D-4328-4D65-BAD2-F73BAC2BAA39 at desuetude dot com> <7B48FC7D-ED05-42C8-B318-1639C5C3C7A2 at mgreg dot com>
On 30-Jul-07, at 11:16 AM, Michael Williams wrote:

> Gotcha,
>
> So you're recommending going the "dylib" route as opposed to the
> plugin route?  What kind of recommendations have you for actually
> distributing the "dylib"?  Someone mentioned actually placing the
> "dylib" in the RB package, I'm not terribly familiar with that
> process, nor how to reference a self-contained library.
>
> Michael


you can use a "special" name for a dylib in OS X that permits you to  
locate it relative to the actual executable

instead of

        Soft declare sub/function name lib "lib name" ....

use
         Soft Declare Sub/function name Lib "@executable_path/../ 
Frameworks/lib name" ....

and then in the OS X version you copy your dylib into the FrameWorks  
folder in the package

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>