Bug #11121 2007-05-18 12:03

cker

bugs with openwatcom 1.6 linker

when i download cb newest nightly-builds and openwatcom 1.6. 
I try to test a simple project. I found cb cannot link the objs .
I found the problem is the linker command is not correct.
so i try to modify it as follows: (win32 exe with single obj)
$linker $link_options  $libdirs libfile $link_objects name $exe_output $libs $link_resobjects
and the result is :
wlink.exe system nt_win LIBP C:\watcom\lib386 LIBP C:\watcom\lib386\nt libfile obj\Release\main.obj name bin\Release\test.exe library gdi32 library user32 library kernel32

everything is ok now. but when i add more source file into project, the bug comes again. all the reason is wink want a list of link objs with comma seperator.

wlink help is :
Open Watcom Linker Version 1.6
Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
usage: wlink {directive}

commands valid for all executable formats:

directive  ::= "File"        obj_spec{","obj_spec}
            | "Name"         exe_file
            | "OPtion"       option{","option}
            | "Library"      library_file{","library_file}
            | "OPTLIB"       library_file{","library_file}
            | "Path"         path_name{";"path_name}
            | "LIBPath"      path_name{";"path_name}
            | "LIBFile"      obj_file{","obj_file}
 ......
but i dont know how to setting the cb to generate the right objs list.
if you can the bug removes!
 it should be :
wlink   .... libfile main.obj,1.obj,2.obj............

Category

Compiler

Group

 

Status

Closed

Close date

2007-05-21 10:31

Assigned to

biplab