<html><head>
<style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head>
<body><div>On Tue, 2026-01-13 at 15:56 +0000, Benjamin Bertrand via omniORB-list wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"></blockquote><div><br></div><div>[...]</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Maybe this issue is not related to the visual studio itself, just the command processor your are using?</div></blockquote><div><br></div><div><br></div><div>It could be. I’m compiling on conda-forge, so using a conda environment: <a href="https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1435250&view=logs&j=535b614b-9e28-51ef-eb67-d0aa83d01d61&t=f3b82646-01b4-574c-79b5-1561965b3e04">https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1435250&view=logs&j=535b614b-9e28-51ef-eb67-d0aa83d01d61&t=f3b82646-01b4-574c-79b5-1561965b3e04</a></div></blockquote><div><br></div><div>Looking at that output, it only includes a single backslash in the command that should be run in cygwin bash:</div><div><br></div><div>../../../bin/x86_win32/clwrapper -gnuwin32 -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. -I../../../include -D__WIN32__ -D_WIN32_WINNT=0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=4 -D_CRT_SECURE_NO_DEPRECATE=1 -Foshared/nt.o <b>-Fdshared\ nt.cc</b></div><div><br></div><div>That is given to clwrapper, which converts cygwin paths to Windows paths, and it sees the "-Fdshared\ nt.cc" as a single argument including a space, which it converts into a quoted argument with the space:</div><div><br></div><div><div><span class="line-area flex-center flex-row flex-grow justify-start" role="group"><span class="content"><span class="pl-plain"><span id="rowContent-1347">cl -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. -I..\..\..\include -D__WIN32__ -D_WIN32_WINNT=0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=4 -D_CRT_SECURE_NO_DEPRECATE=1 -Foshared\nt.o <b>"-Fdshared nt.cc" </b></span></span></span><span class="link" data-lsec="f3b82646-01b4-574c-79b5-1561965b3e04" data-line="1727"><span class="fluent-icons-enabled"><span aria-hidden="true" class="fontSizeM flex-noshrink fabric-icon ms-Icon--Link"></span></span></span></span></div></div><div><br></div><div><br></div><div>When I run it just with make inside a Visual Studio 2022 command prompt, it correctly has two backslashes:</div><div><br></div><div><br></div><div>../../../bin/x86_win32/clwrapper -gnuwin32 -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. -I../../../include -D__WIN32__ -D_WIN32_WINNT=0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=4 -D_CRT_SECURE_NO_DEPRECATE=1 -Foshared/nt.o <b>-Fdshared\\ nt.cc</b></div><div><br></div><div><br></div><div>The shell eats one backslash, so then the cl command generated by clwrapper is correct:</div><div><br></div><div>cl -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. -I..\..\..\include -D__WIN32__ -D_WIN32_WINNT=0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=4 -D_CRT_SECURE_NO_DEPRECATE=1 -Foshared\nt.o -Fdshared\ -Tpnt.cc</div><div><br></div><div><br></div><div><br></div><div>I have no idea what conda-forge is doing, so I don't know what thing has damaged the backslashes. I do see that earlier on in the build log some patches are applied to some make files. What do those patches do?</div><div><br></div><div><br></div><div>Duncan.</div><div><br></div><div><span><pre>-- <br></pre><pre>Duncan Grisby <duncan@grisby.org></pre></span></div></body></html>