Skip to Content.
Sympa Menu

freetds - RE: [freetds] FreeTDS and WINE?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'freetds AT lists.ibiblio.org'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] FreeTDS and WINE?
  • Date: Mon, 3 Feb 2003 16:17:09 -0500

> From: Craig Davison [mailto:cd AT securityfocus.com]
> Sent: February 3, 2003 4:00 PM
>
> On Mon, Feb 03, 2003 at 12:53:36PM -0500, Lowden, James K wrote:
> > Libraries built with with cygwin don't require cygwin to be
> installed at
> > runtime; you just need cygwin's runtime dll. That would be
> a good bet for
> > you, because it would bypass WINE completely, is known to
> work, and we
> > intend to keep it working as long as people find it useful.
>
> ? cygwin is still layered overtop of WINE as any other DLL
> would be.

Ah, silly of me. Quite so.

The more I think about this, the easier it seems. Just a bit of metacoding,
really, writing a .spec file and running the existing code through
"winebuild" to produce a "non-native DLL" -- something that behaves as a DLL
to the application but uses the OS's system calls.

http://www.winehq.com/Docs/wine-devel/architecture.shtml

In my spare time....

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page