Thank you. I don't know any NNTP-based programming Microsoft group. If
anyone does know, please recommend me. I do have access to
gmane.io's
NNTP server, that is, a mail list would probably work too.
> You normally cannot really call cl.exe with a single .cpp and with no
> other arguments. In correct usage it has dozens of command line
> arguments, and you do not call cl.exe directly, but rather an IDE like
> Visual Studio does that, based on a project file which defines those
> dozens of arguments.
Thank you. That pointed me in the right direction. I managed to
compile it using msbuild.exe. The program nuget.exe downloaded the
libraries to the current directory and, inspecting BulkCopy.vcxproj, I
could see the place for them were ..\packages\:
--8<---------------cut here---------------start------------->8---
<ImportGroup Label="ExtensionTargets">
<Import Project="..\packages\wtl.10.0.9163\build\native\wtl.targets" Condition="Exists('..\packages\wtl.10.0.9163\build\native\wtl.targets')" />
<Import Project="..\packages\Microsoft.Windows.ImplementationLibrary.1.0.191107.2\build\native\Microsoft.Windows.ImplementationLibrary.targets" Condition="Exists('..\packages\Microsoft.Windows.ImplementationLibrary.1.0.191107.2\build\native\Microsoft.Windows.ImplementationLibrary.targets')" />
</ImportGroup>
--8<---------------cut here---------------end--------------->8---
> From the error messages it looks like at least /D_UNICODE and/or
> /DUNICODE are missing, but fixing this won't probably help you
> much. You should rather follow the build instructions provided by the
> original program. If there is a .vcxproj or a .sln file, most probably
> you are expected to open that in Visual Studio and build it there.
You're right. It did use /D _UNICODE and /D UNICODE.