| 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: | Tim Jones <tjmac at tolisgroup dot com> |
| Date: | Fri, 14 Sep 2007 13:24:37 -0700 |
| Delivered-to: | listarchive at realsoftware dot com |
| Delivered-to: | realbasic-nug at lists dot realsoftware dot com |
| Organization: | TOLIS Group, Inc. |
| References: | <20070914201842 dot B79EF7C2411 at mail dot verex dot com> |
joe at strout dot net wrote: > On Sep 14, 2007, at 20:08 UTC, Tim Jones wrote: > > >>> Or just have 2 plugins ? >>> >>> >> Or better still, since Quesa is released under the BSD license, why >> not simply incorporate the functionality into REALbasic directly? >> > > That's not better still; that's essentially what they've done, on > Windows and Linux, and is exactly the problem. Declares to Quesa don't > work when there is no Quesa library to declare to. > I may be missing something, but if the Quesa libs are built in, why would you need declares? Tim _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html> |
| Previous by Date: | Re: Why does QUESA have to be dynamically linked in Windows/Linux?, Norman Palardy |
|---|---|
| Next by Date: | Re: Linux hosting that will run RB apps, Robert Fang |
| Previous by Thread: | Re: Why does QUESA have to be dynamically linked in Windows/Linux?, Norman Palardy |
| Next by Thread: | Re: Why does QUESA have to be dynamically linked in Windows/Linux?, Norman Palardy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |