on 7/27/07 4:35 PM, Michael Williams at lists at mgreg dot com wrote:
> Thanks Chris,
>
> That implementation makes a bit more sense. I was hoping to be able
> to port the entire library to RB, but I can see that that's a lot of
> work. Rather, I should simply port/reference the functionality I
> need currently and leave the rest for later.
It depends. If you're just wrapping a library from somewhere else it is
likely that the big hurdle will be getting that library to compile into the
plug-in. As well many of the functions you want to implement may have
structural similarities so you would want to implement them at the same
time.
> For instance, if I need a "FlipRight" method, I should port that and
> leave the "FlipLeft" for next time. Does that sound about right?
> It
> would really be nice if there were some sort of directport
> functionality that would automatically add the corresponding RB calls
> to existing C functions for creating plugins. Is anything like this
> in the works?
If what you have is a shared library (dylib, DLL, ...) with a C interface
then you can call it today with declares and you don't need a plug-in at
all. If you don't know much about declares I recommend Charles Yeoman's book
iDeclare at http://www.declaresub.com/. You need to use a plug-in when
either the interfacing becomes complicated or all you have is source code to
the library.
Chris
> On Jul 27, 2007, at 4:17 PM, Chris Little wrote:
>
>> I would start from Dave Addey's excellent Xcode template instead of
>> Thomas
>> Tempelman's since the latter is quite out of date. On Windows I
>> would use
>> Visual Studio if you have access to it. The plug-in SDK has example
>> projects
>> you can work from.
>>
>> As for integrating a C/C++ library into a plug-in take a look at the
>> PNGUtilities example in plug-in SDK. This a Mac plug-in that wraps
>> libpng
>> and it sounds similar to what you want to do.
>>
>> Chris
>>
>> on 7/27/07 3:08 PM, Didier CUGY at didier dot cugy at neuf dot fr wrote:
>>
>>> there is no problem to include a library in a plugin.
>>>
>>> the thomas tempelman example allow to understand how to write plugin.
>>>
>>> this is more difficult with Mach-O plugins but the SDK example work.
>>>
>>> the best way is to use XCODE for mach-o plugin (macintel and PPC)
>>>
>>> and code warrior for classic and windows. i prefer the 8.3 version.
>>>
>>> best regards
>>>
>>>
>>>
>>> Le 27 juil. 07 à 20:48, Michael Williams a écrit :
>>>
>>>> Note: This is a repost per Joe Strout's suggestion to post to the
>>>> "plugins" list. Joe has replied, but I'd also like to get the
>>>> list's
>>>> thoughts.
>>>>
>>>>
>>>>
>>>>
>>>> Hi All,
>>>>
>>>> I'm currently developing a program that requires the use of a few
>>>> odd
>>>> file formats (e.g. FITS, etc.). Obviously RB doesn't support opening
>>>> or manipulating this file format (does it?). Therefore I need to
>>>> incorporate the functionality of an existing C/C++ library (as a
>>>> plugin or otherwise) into my RB project.
>>>>
>>>> I need this to be cross-platform. Will I need to create separate
>>>> plugins for each? I'd prefer the MBS approach in having only one
>>>> plugin that is cross-platform. How, exactly, is this achieved?
>>>> Will I
>>>> need to map each and every function manually or is the plugin system
>>>> intuitive enough to expose functionality?
>>>>
>>>> I've been looking through the SDK documentation but it doesn't seem
>>>> very well organized or up to date.
>>>>
>>>> If possible, I'd appreciate a tutorial or some information that
>>>> provides direction from beginning to end in a *clear*, *concise*
>>>> manner on how to include an entire existing C/C++ library into an RB
>>>> project.
>>>>
>>>> Regards,
>>>> Michael
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|