home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!usc!cs.utexas.edu!sun-barr!ames!pacbell.com!well!johnrp
- From: johnrp@well.sf.ca.us (John Panzer)
- Subject: Re: Linking OWL as a DLL?
- Message-ID: <Bt6505.Myv@well.sf.ca.us>
- Sender: news@well.sf.ca.us
- Organization: Whole Earth 'Lectronic Link
- References: <c24mPB1w165w@pdaxs.techbook.com>
- Date: Tue, 18 Aug 1992 07:33:41 GMT
- Lines: 35
-
- In article <c24mPB1w165w@pdaxs.techbook.com> nsilva@pdaxs.techbook.com (nsilva) writes:
- >
- >What is the proper way to link my TCW application with OWL.DLL?
- >
- >I've followed the directions in the Fine Manual: (a) define _CLASSDLL,
- >(b) link in the large memory model, (c) use smart callbacks, and
- >(d) add OWL.LIB, TCLASSDLL.LIB, and CRTLDLL.LIB to the project file.
- >But I end up with dozens of undefined symbols, such as:
- >
- >Linker Error: Undefined symbol TWindow::TWindow(TWindowsObject...
- >Linker Error: Undefined symbol Object::operator new(unsigned i...
- >Linker Error: Undefined symbol TWindow::GetWindowClass(tagWNDC...
- >Linker Error: Undefined symbol TApplication::~TApplication() i...
- >etc.
- >etc.
- >etc.
- >
- >
- >BTW, I'm using TCW 3.0, and Windows 3.1 (yes, I'm going to upgrade
- >soon).
- >
- >Nate
- >nsilva@pdaxs.techbook.com
-
- You might want to try #defining _RTLDLL as well (I _know_ this is
- required if you want to link in Borland's regular run-time DLL
- library). It might be needed for linking in the OWL DLL as well.
-
- I'm posting this because it took a call to Borland to find out
- about _RTLDLL; it's documented only in the chapter on the IDE.
- Hopefully this will save somebody else some time and stress.
-
- John Panzer
- johnrp@well.sf.ca.us
-
-