How many more times will I have to complain about this? It is only one little `\` missing.
ntLib = ${ntTools}\lib/x64/
I found below definition. ntTools has been appended a slash already.
Hi Yongan.Fu,
Thanks for your quick response!
But mine definition also has a backslash at the end, because it is a shell variable and not a makefile variable.
NTTOOLS=C:\PROGRA~2\MIB055~1\2017\PROFES~1\VC\Tools\MSVC\1416~1.270\
Of course I could trick the system with a double or tripple slash or backslash. But IMHO `{}` stands for "cleaning up the path to avoid double or tripple slashes"
I suspect that the correct use of `{}` in Makefiles is as I have written here ce-u13-sdk-missing-slash-in-winntmdl-mki-fatal-error-lnk1181.Or am I mistaken, and the - in my eyes unclean - use of `\/` is the recommended procedure?
As a workaround it is of course a possibility. But of course, collateral damage can occur elsewhere.
Mit freundlichen Grüßen / Best regards Volker Hüfner
| AB_DATE Engineering Software | ab-date.de |
Hi Volker Hüfner,
Defect 1108605 has been filed to address consistency of ntTools in winntmdl.mki. I have requested this be corrected and included in the MSCE SDK U15 release. Although hopeful I cannot say with 100% certainty the fix will be addressed in that release.
HTH,BobRELATED:
Answer Verified By: Volker Hüfner
Hi Robert Hook,
Fortunately it is only an annoying mistake and not a critical one.
I hope your hope will come true, otherwise I "threaten" with a post "[CE U15 & CE U14 & U13 & U12 SDK] Still Missing slash in winntmdl.mki => fatal error LNK1181" :-)
Eureka, the slash is finally here. (#U15)
Thanks a lot!