Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

porting link and .def files to open watcom

11 views
Skip to first unread message

Bill Silverstein

unread,
Mar 18, 2007, 3:11:11 AM3/18/07
to
Is there an easy way to port the .lnk and .def files to open watcom?

From my read of the documentation, is that you add the "Option" and the
.def file entries into the .lnk file.

Thanks.


Hans-Bernhard Bröker

unread,
Mar 18, 2007, 11:36:55 AM3/18/07
to
Bill Silverstein wrote:
> Is there an easy way to port the .lnk and .def files to open watcom?

Port them --- from where?

And what parts of them do you have to re-use?

Last I checked, OW did accept .def files as-is, for those few cases that
really need them.

Bill Silverstein

unread,
Mar 18, 2007, 1:37:33 PM3/18/07
to

From VAC++. The MS2WLINK documents say that it handles os2 .def files,
but it does not seem too.

I mean even something simple like:

LIBRARY COMPOSE INITINSTANCE TERMINSTANCE
PROTMODE
DATA MULTIPLE NONSHARED READWRITE LOADONCALL
CODE LOADONCALL

EXPORTS ComposeWindow
HandleRotate13

Thanks.


Michal Necasek

unread,
Mar 18, 2007, 4:10:44 PM3/18/07
to
Bill Silverstein wrote:
>
> From VAC++. The MS2WLINK documents say that it handles os2 .def files,
> but it does not seem too.
>
Sure it does. But it's called MS2WLINK for a reason - it supports .def
files intended for the *Microsoft* OS/2 linker (LINK.EXE), ie. for
16-bit OS/2.


Michal

Michael Greene

unread,
Mar 18, 2007, 8:54:21 PM3/18/07
to


Kind of like this:

--------- in makefile -----

dw.dll: $(DWOJS)
$(LD) NAME dw @dw.lnk $(LDFLAGES) FILE {$(DWOJS)}


--------- dw.lnk ----------

SYSTEM os2v2_dll initinstance terminstance
OPTION manyautodata
OPTION DESCRIPTION 'Dynamic Windows for OS/2'

EXPORT dw_init.10
EXPORT dw_main.11
EXPORT dw_exit.12
EXPORT dw_beep.13

--- many more exports

0 new messages