My bmake file containing the following line...
#---------------------------------------------------------------------- # Compile the Windows resource files for the DLM #---------------------------------------------------------------------- $(o)$(appName).res : $(baseDir)$(appName).rc $(baseDir)resource.h
The rule recognises that I want to create a binary resource (*.res) from a resource source file (*.rc). It's standard Win32 resource stuff. With CONNECT Update 4 and earlier that line built as expected.
With CONNECT Update 5 that rule fails with this message:
[== Building G:\PROGRA~1\Bentley\MICROS~2\SDK\objects\AreaAnnotator.res, (Q:\AreaAnnotator\CONNECT\AreaAnnotator.rc) ==] rc -d -dVARIETY= -dUSER="\"CONNECT on CELERATRIX64\"" -d_X64_ -dwinNT -r -foG:\PROGRA~1\Bentley\MICROS~2\SDK\objects\AreaAnnotator.res Q:\AreaAnnotator\CONNECT\AreaAnnotator.rc 'rc' is not recognized as an internal or external command, operable program or batch file.
I've attached a modified DialogBoxDemo example. I've added a Windows version resource to the project and the line to build that resource in DialogBoxDemo.mke. It demonstrates the same failure. What's gone wrong?
0844.DialogBoxDemo.zip
Unknown said:[== Building G:\PROGRA~1\Bentley\MICROS~2\SDK\objects\AreaAnnotator.res, (Q:\AreaAnnotator\CONNECT\AreaAnnotator.rc) ==] rc -d -dVARIETY= -dUSER="\"CONNECT on CELERATRIX64\"" -d_X64_ -dwinNT -r -foG:\PROGRA~1\Bentley\MICROS~2\SDK\objects\AreaAnnotator.res Q:\AreaAnnotator\CONNECT\AreaAnnotator.rc 'rc' is not recognized as an internal or external command, operable program or batch file.
Other than some minor spacing (and obvious user/computer/path) differences between our output all other syntax appears to be correct.
I compared full ..\mki source directories between U4 and U5 and only 3 mki files changed, but nothing close to being related to the .rc.res dependency rule was impacted. Copyrights, updated default VS compiler change (DefaultToolSet.mki), DotFuscator updates (mkcsharp.mki), and a few modified/stricter CCompOpts added - in winntmdl.mki - where the .rc.res dependency rules exist and are maintained.
I had no issues compiling the sample you provided and I attached my full build output (+avilC) that can be used for comparison. If you post your build output I can look in parallel if you like.
If the build output comparison does not yield the critical information needed, my fallback would be to use Microsoft Process Monitor (procmon) to review the build process. Even though hundreds of thousands or slightly over a million lines of logging are generated, you can use procmon's filtering system and Details property to look at the buffer (read) offset for each Write line related to your full build output log to quickly target within milliseconds of logging where your environment is attempting to locate the tools or not finding files/folders, or not having sufficient permissions, etc.
As a side note on my build output past the failure point you are encountering, I did notice a build tool output (XLIFF language translation) message as follows that I will look into to see what may need to be modified to silence or properly resolve if you don't have or need XLIFF resource translation.
ExtractLangPackInfo C:\PROGRA~1\Bentley\MICROS~1\MICROS~1\mdlapps\dlogdemo.ma C:\Users\ROBERT~1.HOO\AppData\Local\Temp\Bentley\MicroStationSDK\rscobj\dlogdemo.ma.mui.xliff Translatable data file created - C:\Users\ROBERT~1.HOO\AppData\Local\Temp\Bentley\MicroStationSDK\rscobj\dlogdemo.ma.mui.xliff Could Not Find C:\PROGRA~1\Bentley\MICROS~1\MICROS~1\mdlapps\en\dlogdemo.ma.mui GenerateLangPack C:\PROGRA~1\Bentley\MICROS~1\MICROS~1\mdlapps\dlogdemo.ma C:\Users\ROBERT~1.HOO\AppData\Local\Temp\Bentley\MicroStationSDK\rscobj\dlogdemo.ma.mui.xliff C:\PROGRA~1\Bentley\MICROS~1\MICROS~1\mdlapps\en\dlogdemo.ma.mui
HTH,Bob
buildoutput.zip
Unknown said:I will look into to see what may need to be modified to silence or properly resolve if you don't have or need XLIFF resource translation
I have no idea what XLIFF resource translation means, nor what an .mui file is!
Regards, Jon Summers LA Solutions
Unknown said:Windows and Web Development > Universal Windows App Development Tools > Windows 10 SDK
I'm pleased to report that installing that additional Viz Studio 2015 component has solved my problem. The app. now builds to completion. However, I have no idea why that solved the problem!
Answer Verified By: Jon Summers