When building C++ examples for the update 12 SDK it fails with the following error:
-MANIFESTFILE:C:\Users\doug\AppData\Local\Temp\Bentley\MicroStationSDK\objects\ModelExample.dll.ManifestC:\Users\doug\AppData\Local\Temp\Bentley\MicroStationSDK\objects\ModelExample.obj C:\Users\doug\AppData\Local\Temp\Bentley\MicroStationSDK\objects\ModelExampleHelper.obj B:\Apps\Bentley\library\bentley.lib B:\Apps\Bentley\library\BentleyAllocator.lib B:\Apps\Bentley\library\mdlbltin.lib B:\Apps\Bentley\library\RmgrTools.lib B:\Apps\Bentley\library\BentleyGeom.lib B:\Apps\Bentley\library\DgnPlatform.lib B:\Apps\Bentley\library\ECObjects.lib B:\Apps\Bentley\library\dgnview.lib gdi32.lib user32.lib kernel32.lib C:\PROGRA~2\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\lib\x64\msvcrt.libB:\Apps\Bentley\library\mdlbltin.libLINK : fatal error LNK1181: cannot open input file 'C:\PROGRA~2\Microsoft.obj'BMAKE: call trace line: 414, B:\Apps\Bentley\mki\dlmlink.mki line: 106, B:\Apps\Bentley\examples\Model\ModelExample\ModelExample.mkeMon Nov 04 23:23:11 2019, elapsed time: 0:00
Clearly the space in the path:
C:\PROGRA~2\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\lib\x64\msvcrt.lib
Is causing problems. I'm guessing it needs to be quoted somewhere, but I have been unable to locate where it is specified.
Douglas Wood said:the space in the path: C:\PROGRA~2\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\lib\x64\msvcrt.lib Is causing problems. I'm guessing it needs to be quoted somewhere, but I have been unable to locate where it is specified. BMAKE: call trace line: 414, B:\Apps\Bentley\mki\dlmlink.mki
the space in the path:
BMAKE: call trace line: 414, B:\Apps\Bentley\mki\dlmlink.mki
Look in the MDL Include file dlmlink.mki. It fails at line 414. Do not even think about editing that file!
dlmlink.mki
Those of us who have been doing this for a while have accommodated ourselves to bmake's foibles. For example, you might think about reinstalling Viz Studio to a location without spaces in folder names.
Jan Šlegr said:Maybe on you C (system) volume, the 8.3 naming is not enabled?
Good point! But why has Program Files(x86) been converted to PROGRA~2 but Microsoft Visual Studio remains unshortened?
Program Files(x86)
PROGRA~2
Microsoft Visual Studio
Regards, Jon Summers LA Solutions
Jon Summers said:But why has Program Files(x86) been converted to PROGRA~2 but Microsoft Visual Studio remains unshortened?
That's very good question :-)
I do not know too much about how 8.3 naming works, but I remember it was mentioned in some discussion that the naming enable/disable does not mean that all names are affected immediately, but they are generated when created. So maybe it's because it was enabled/disabled before/after Visual Studio was installed?
System administrator should provide first insight how Windows are configured. Also to use fsutil tool can help to obtain more information about used configuration..
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point