Under Windows, OPTLINK (8.00.2) gets confused when an object file has a compound extension with than one '.' in the name, as in foo.d.o. For such files, OPTLINK reports "Error 2: File Not Found foo.d". Cmake always generates object files with a compound extension.  I'm already asking cmake people, but a work-around may not be forthcoming.

What is the right way to get OPTLINK fixed?

-steve

Hello SK,

> Under Windows, OPTLINK (8.00.2) gets confused when an object file has
> a compound extension with than one '.' in the name, as in foo.d.o. For
> such files, OPTLINK reports "Error 2: File Not Found foo.d". Cmake
> always generates object files with a compound extension.  I'm already
> asking cmake people, but a work-around may not be forthcoming.
> 
> What is the right way to get OPTLINK fixed?
> 

Wait. Optlink is written in ASM and is in he process of being converted to C. Until that happens, don't expect any bug fixes. OTOH a wrapper that copies files and munges names wouldn't be that hard to write.


> -steve
> 
-- 
... <IXOYE><