Re: Issue compiling with Microsoft Visual Studio 2022
Duncan Grisby via omniORB-list <[email protected]> Wed, 14 Jan 2026 11:02:38 +0000
| Newsgroups | gmane.comp.corba.omniorb.user |
|---|---|
| Message-ID | <[email protected]> |
--===============0198674068401105132== Content-Type: multipart/alternative; boundary="=-WwkYaLdDkPPU7tFJojZp" --=-WwkYaLdDkPPU7tFJojZp Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2026-01-13 at 15:56 +0000, Benjamin Bertrand via omniORB-list wrote: [...] > > Maybe this issue is not related to the visual studio itself, just > > the command processor your are using? >=20 >=20 > It could be. I=E2=80=99m compiling on conda-forge, so using a conda > environment: > https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId= =3D1435250&view=3Dlogs&j=3D535b614b-9e28-51ef-eb67-d0aa83d01d61&t=3Df3b8264= 6-01b4-574c-79b5-1561965b3e04 Looking at that output, it only includes a single backslash in the command that should be run in cygwin bash: ../../../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=3D0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=3D4 - D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared/nt.o -Fdshared\ nt.cc 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: cl -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. - I..\..\..\include -D__WIN32__ -D_WIN32_WINNT=3D0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=3D4 -D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared\nt.o "- Fdshared nt.cc"=C2=A0 When I run it just with make inside a Visual Studio 2022 command prompt, it correctly has two backslashes: ../../../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=3D0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=3D4 - D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared/nt.o -Fdshared\\ nt.cc The shell eats one backslash, so then the cl command generated by clwrapper is correct: cl -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. - I..\..\..\include -D__WIN32__ -D_WIN32_WINNT=3D0x0501 -D__x86__ -D__NT__ -D__OSVERSION__=3D4 -D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared\nt.o - Fdshared\ -Tpnt.cc 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? Duncan. --=20 Duncan Grisby <[email protected]> --=-WwkYaLdDkPPU7tFJojZp Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <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=3D"cite" style=3D"margin:0 0 0 .8ex; bor= der-left:2px #729fcf solid;padding-left:1ex"></blockquote><div><br></div><d= iv>[...]</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-= left:2px #729fcf solid;padding-left:1ex"><blockquote type=3D"cite" style=3D= "margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Ma= ybe 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=E2=80=99m compiling on conda-forge, so using a conda en= vironment: <a href=3D"https://dev.azure.com/conda-forge/feedstock-builds/_b= uild/results?buildId=3D1435250&view=3Dlogs&j=3D535b614b-9e28-51ef-e= b67-d0aa83d01d61&t=3Df3b82646-01b4-574c-79b5-1561965b3e04">https://dev.= azure.com/conda-forge/feedstock-builds/_build/results?buildId=3D1435250&= ;view=3Dlogs&j=3D535b614b-9e28-51ef-eb67-d0aa83d01d61&t=3Df3b82646-= 01b4-574c-79b5-1561965b3e04</a></div></blockquote><div><br></div><div>Looki= ng 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_win= 32/clwrapper -gnuwin32 -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREA= D_DLL -I. -I. -I../../../include -D__WIN32__ -D_WIN32_WINNT=3D0x0501 -D__x= 86__ -D__NT__ -D__OSVERSION__=3D4 -D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared/= nt.o <b>-Fdshared\ nt.cc</b></div><div><br></div><div>That is given to clwr= apper, which converts cygwin paths to Windows paths, and it sees the "-Fdsh= ared\ 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 clas= s=3D"line-area flex-center flex-row flex-grow justify-start" role=3D"group"= ><span class=3D"content"><span class=3D"pl-plain"><span id=3D"rowContent-13= 47">cl -c -O2 -FS -MD -EHs -GS -GR -Zi -nologo -D_OMNITHREAD_DLL -I. -I. -I= ..\..\..\include -D__WIN32__ -D_WIN32_WINNT=3D0x0501 -D__x86__ -D__NT__ -D_= _OSVERSION__=3D4 -D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared\nt.o <b>"-Fdshare= d nt.cc" </b></span></span></span><span class=3D"link" data-lsec=3D"f3= b82646-01b4-574c-79b5-1561965b3e04" data-line=3D"1727"><span class=3D"fluen= t-icons-enabled"><span aria-hidden=3D"true" class=3D"fontSizeM flex-noshrin= k 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 S= tudio 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../../../inc= lude -D__WIN32__ -D_WIN32_WINNT=3D0x0501 -D__x86__ -D__NT__ -D__OSVERSION__= =3D4 -D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared/nt.o <b>-Fdshared\\ nt.cc</b>= </div><div><br></div><div><br></div><div>The shell eats one backslash, so t= hen 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=3D0x0501 -D__x86__ -D__NT__ -D_= _OSVERSION__=3D4 -D_CRT_SECURE_NO_DEPRECATE=3D1 -Foshared\nt.o -Fdshared\ -= Tpnt.cc</div><div><br></div><div><br></div><div><br></div><div>I have no id= ea what conda-forge is doing, so I don't know what thing has damaged the ba= ckslashes. I do see that earlier on in the build log some patches are appli= ed 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 <[email protected]></pre></span></div></body></html> --=-WwkYaLdDkPPU7tFJojZp-- --===============0198674068401105132== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ omniORB-list mailing list [email protected] https://www.omniorb-support.com/mailman/listinfo/omniorb-list --===============0198674068401105132==--