Hmm, This certainly is supposed to work. It's very suspicious that your build fails trying to link pthreads.dll - that isn't expected to be linked in windows at all.
Is it possible that you have openssl detected and linked? That might force pthreads. Currently the TLS support for windows is provided by the windows schannel implementation not openssl. If this is the case then you should be able to force the schannel TLS impl rather than the openssl impl using cmake -DSSL_IMPL=schannel Sorry it's taken so long to get back to you - I've been rather preoccupied with family matters in the past few weeks. Andrew On Tue, Feb 7, 2023 at 3:10 PM Richard Straus <richard.str...@kofax.com.invalid> wrote: > Hi, > > > > I’m using Qpid.Proton 0.33 for C++, using Win32 and x64 build > configurations. I would like to upgrade to the latest version 0.38, > unfortunately the CMAKE request aborts. > > > > cmake .. -G "Visual Studio 17 2022" -A Win32 > > > > It appears that this CMAKE command only works successfully on version 0.33 > and stopped working with version 0.34. Does anyone have a workaround in > order to achieve a successful Win32 construction? > > > > An x64 build architecture works fine. (cmake .. -G "Visual Studio 17 2022" > -A x64) > > The error logs look identical between the win32 and x64 up to the point > where the win32 build log stops logging, which is here: > > > > -- > > Determining if the function pthread_create exists in the pthread failed > with the following output: > > Change Dir: > C:/u/Projects/3rdParty/qpid-proton-0.34.0/build32/CMakeFiles/CmakeScratch/TryCompile-yekssr > > > > Run Build Command(s):C:/Program Files/Microsoft Visual > Studio/2022/Professional/MSBuild/Current/Bin/amd64/MSBuild.exe > cmTC_1ce46.vcxproj /p:Configuration=Debug /p:Platform=Win32 > /p:VisualStudioVersion=17.0 /v:m && MSBuild version 17.4.0+18d5aef85 for > .NET Framework > > > > Microsoft © C/C++ Optimizing Compiler Version 19.34.31935 for x86 > > > > Copyright © Microsoft Corporation. All rights reserved. > > > > CheckFunctionExists.c > > > > cl /c /Zi /W3 /WX- /diagnostics:column /Od /Ob0 /Oy- /D _MBCS /D WIN32 > /D _*WINDOWS /D CHECK_FUNCTION_EXISTS=pthread_create /D > “CMAKE_INTDIR=\”Debug\”” /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t > /Zc:forScope /Zc:inline /Fo”cmTC_1ce46.dir\Debug\\” > /Fd”cmTC*_1ce46.dir\Debug\vc143.pdb” > /external:W3 /Gd /TC /analyze- /errorReport:queue > “C:\u\Projects\3rdParty\qpid-proton-0.34.0\build32\CmakeFiles\CmakeScratch\TryCompile-yekssr\CheckFunctionExists.c” > > > > LINK : fatal error LNK1104: cannot open file ‘pthread.lib’ > [C:\u\Projects\3rdParty\qpid-proton-0.34.0\build32\CmakeFiles\CmakeScratch\TryCompile-yekssr\cmTC_1ce46.vcxproj] > > -- > > Specifically, the x64 CMAKE log also shows the same error, but continues > execution. > > > > This is the last entry in the CmakeOutpout.log file: > > -- > > CMakeCCompilerABI.c > > > > cl /c /Zi /W3 /WX- /diagnostics:column /Od /Ob0 /Oy- /D _MBCS /D WIN32 > /D _*WINDOWS /D “CMAKE_INTDIR=\”Debug\”” /Gm- /RTC1 /MDd /GS /fp:precise > /Zc:wchar_t /Zc:forScope /Zc:inline /Fo”cmTC_33642.dir\Debug\\” > /Fd”cmTC*_33642.dir\Debug\vc143.pdb” > /external:W3 /Gd /TC /analyze- /errorReport:queue “C:\Program > Files\Cmake\share\cmake-3.25\Modules\CMakeCCompilerABI.c” > > > > cmTC_33642.vcxproj -> > C:\u\Projects\3rdParty\qpid-proton-0.34.0\build32\CmakeFiles\CmakeScratch\TryCompile-4du5h9\Debug\cmTC_33642.exe > > -- > > > > > > > > *Richard Straus* > Senior Software Developer > *Kofax, Inc.* > > Toronto, ON > Canada > > Tel: +1 (857) 214-6694 > > richard.str...@kofax.com > > > > *Richard Straus* > Sr. Software Developer > > > > > *Kofax Canada, ULC*460 Phillip Street > Waterloo, ON N2L 5J2 > > Tel: +1 519 880 7421 > richard.str...@kofax.com > > > > > ______________________________________________________________________________________________________________________________________________________________ > > This communication is only for the use of the intended recipient. It may > contain confidential or proprietary information. If you are not the > intended recipient or have received this communication in error, please > notify the sender via phone and destroy this communication immediately. > > >
