realbasic-nug
[Top] [All Lists]

Re: Why does QUESA have to be dynamically linked in Windows/Linux?

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Why does QUESA have to be dynamically linked in Windows/Linux?
From: Frank Condello <developer at chaoticbox dot com>
Date: Fri, 14 Sep 2007 17:36:45 -0400
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <20070914201842 dot B79EF7C2411 at mail dot verex dot com> <46EAEE05 dot 9080501 at tolisgroup dot com> <04E31D2A-B646-44C1-946F-F09CCF260F98 at great-white-software dot com> <46EAFB24 dot 6070408 at tolisgroup dot com>
On 14-Sep-07, at 5:20 PM, Tim Jones wrote:

> Norman Palardy wrote:
>> On 14-Sep-07, at 2:24 PM, Tim Jones wrote:
>>
>>> I may be missing something, but if the Quesa libs are built in, why
>>> would you need declares?
>>
>> To get at the functions that are not exposed by the plugin
>
> Then why not just ignore the plugin and provide the dynamic library
> based on the code available at Sourceforge?  This would allow you  
> to do
> everything by declare and make sure that you always had the latest
> version for functions.

'Cause then you're using two copies of the same library (and your app  
will crash and burn).

> Or, convert the current library code to a plugin.

You'll have to recreate all of Rb3D for that to work. At that point  
it makes more sense to ignore Quesa and Rb3D and just start from  
scratch.

Frank.
<http://developer.chaoticbox.com/>



_______________________________________________
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>