| 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: | Norman Palardy <npalardy at great-white-software dot com> |
| Date: | Fri, 14 Sep 2007 14:24:24 -0600 |
| 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> |
On 14-Sep-07, at 2:18 PM, joe at strout dot net wrote: > 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. Can you hack things and declare into your own program since it has those entry points in it ? Dunno of that works _______________________________________________ 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: Linux hosting that will run RB apps, Alan Sawyer |
|---|---|
| Next by Date: | Re: Why does QUESA have to be dynamically linked in Windows/Linux?, Tim Jones |
| Previous by Thread: | Re: Why does QUESA have to be dynamically linked in Windows/Linux?, Frank Condello |
| Next by Thread: | Re: Why does QUESA have to be dynamically linked in Windows/Linux?, Tim Jones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |