You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Richard Straus <ri...@kofax.com.INVALID> on 2023/02/08 16:48:56 UTC

Win32 build architecture

Hi,

We have had no issues creating and building a Win32 architecture on an x64 machine with Qpit Proton 0.33. However, since the changes introduced to the CMakeLists.txt file for version 0.34, the Win32 architecture fails.

cmake .. -G "Visual Studio 17 2022" -A Win32

I suspect that the issue is an error shown below which possibly indicates that it is trying to identify a win32 python installation for which only an x64 version is installed:

C:\u\Projects\3rdParty\qpid-proton\build32>cmake .. -G "Visual Studio 17 2022" -A Win32
-- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.17763.
-- The C compiler identification is MSVC 19.34.31935.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.34.31933/bin/Hostx64/x86/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found OpenSSL: C:/Program Files (x86)/OpenSSL/lib/libcrypto.lib (found version "1.1.1i")
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - not found
-- Found Threads: TRUE
-- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
-- Found PkgConfig: C:/usr/bin/Strawberry/perl/bin/pkg-config.bat (found version "0.26")
-- Could NOT find CyrusSASL (missing: CyrusSASL_LIBRARY CyrusSASL_INCLUDE_DIR)
CMake Error at C:/Program Files/CMake/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Python (missing: Python_EXECUTABLE Interpreter) (found
  suitable version "3.11.1", minimum required is "3.6")

      Reason given by package:
          Interpreter: Wrong architecture for the interpreter "C:/Users/richard_straus/AppData/Local/Programs/Python/Python311/python.exe"

Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files/CMake/share/cmake-3.25/Modules/FindPython/Support.cmake:3245 (find_package_handle_standard_args)
  C:/Program Files/CMake/share/cmake-3.25/Modules/FindPython.cmake:519 (include)
  tools/cmake/Modules/FindPython.cmake:56 (include)
  CMakeLists.txt:45 (find_package)


-- Configuring incomplete, errors occurred!
See also "C:/u/Projects/3rdParty/qpid-proton/build32/CMakeFiles/CMakeOutput.log".
See also "C:/u/Projects/3rdParty/qpid-proton/build32/CMakeFiles/CMakeError.log".

We have an x64 build node that has x64 Python 3.11.1 and VS 2022.

The x64 form of the CMAKE command runs fine:

cmake .. -G "Visual Studio 17 2022" -A x64

As a quick test, I reverted the 0.38 version of CMakeLists.txt to the version distributed with 0.33. Although the NMAKE commands fail, the resulting builds fail. I have no experience with CMAKE or Python so I am seeking help with getting a version of Qpid Proton to compile under a win32 architecture.

Regards,

Richard


Richard Straus
Senior Software Developer
Kofax, Inc.
[cid:image001.png@01D93BB1.95E34510]
Toronto, ON
Canada
Tel: +1 (857) 214-6694
richard.straus@kofax.com<ma...@kofax.com>


Richard Straus
Sr. Software Developer

[cid:Kofax_ab6d7362-d88f-454c-a5e0-9fbdacd27b9c.jpg]

Kofax Canada, ULC
460 Phillip Street
Waterloo, ON N2L 5J2

Tel: +1 519 880 7421
richard.straus@kofax.com

 [cid:WorkLikeTomorrow_5b748fe4-9e86-42f8-b5af-b79a2d6ee254.jpg]

______________________________________________________________________________________________________________________________________________________________

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.