Description

Optlink doesn't always create the executable correctly if the linker options are on a separate line (after the .res file)

e.g. the ksp file created looks like this
 
foo.obj
foo.exe
foo.map
kernel32.lib+user32.lib
foo.def
foo.res
/noi/map
 
for Optlink to form the executable correctly it need to look like this
 
foo.obj
foo.exe
foo.map
kernel32.lib+user32.lib
foo.def
foo.res/noi/map

I have 1 project where the problem doesn't occur and another (much larger) where it does.