home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!vnet.ibm.com
- From: francis@vnet.ibm.com (Tim Francis)
- Message-ID: <19930124.185441.75@almaden.ibm.com>
- Date: Sun, 24 Jan 93 21:54:22 EST
- Subject: Watcom C/386 9.1d and the WorkFrame -> Help!
- Newsgroups: comp.os.os2.programmer
- References: <C1DzxK.J6n@undergrad.math.waterloo.edu>
- Reply-To: francis@vnet.ibm.com
- Organization: IBM Canada Lab, WorkFrame/2 development
- Disclaimer: This posting represents the poster's views, not those of IBM
- Lines: 30
-
- In article <C1DzxK.J6n@undergrad.math.waterloo.edu>,
- scdrye@napier.uwaterloo.ca (Stephen Drye) writes:
- >
- >Hi!
- >
- >I just got the WorkFrame off of the November PDK, so I've been trying
- >to set up WTC/386 with it.
- >
- >I've run into two problems:
- >- When you choose the 386 as your target processor, the compiler options
- >dll passes garbage on the end of the string "/3r" which causes the compile
- >to fail.
-
- I've never heard of this problem; you may want to contact Watcom
- directly, and see if they know about/have a fix.
-
- >- When I try to use the makefile generator, it complains about being
- >unable to open the compiler options dll (error 127), although the dll
- >is in a directory ref'd in my libpath (also, I'm able to use it
- >at all other times). So, I can't generate a makefile.
-
- The makefile creation utility works by calling the compiler options
- DLL (provided by Watcom) to parse the source files, and return a
- list of dependency information. It's my understanding that Watcom
- chose not to implement this particular entry point. Again, your
- best approach is probably to contact them, and make them aware of
- your request. -tim
-
- >Thanks,
- >Stephen Drye
-