Posted to tcl by mjanssen at Tue Feb 02 10:52:40 GMT 2021view raw

  1. c:\Users\Mark\Src\tcl-act\example>act build manifests\manifest.txt --vcpkg c:\Bin\vcpkg
  2. -- Building for: Visual Studio 16 2019
  3. -- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.19042.
  4. -- The CXX compiler identification is MSVC 19.28.29336.0
  5. -- Detecting CXX compiler ABI info
  6. -- Detecting CXX compiler ABI info - done
  7. -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/BuildTools/VC/Tools/MSVC/14.28.29333/bin/Hostx64/x64/cl.exe - skipped
  8. -- Detecting CXX compile features
  9. -- Detecting CXX compile features - done
  10. CMake Error at CMakeLists.txt:29 (find_package):
  11. Could not find a package configuration file provided by "unofficial-sodium"
  12. with any of the following names:
  13.  
  14. unofficial-sodiumConfig.cmake
  15. unofficial-sodium-config.cmake
  16.  
  17. Add the installation prefix of "unofficial-sodium" to CMAKE_PREFIX_PATH or
  18. set "unofficial-sodium_DIR" to a directory containing one of the above
  19. files. If "unofficial-sodium" provides a separate development package or
  20. SDK, be sure it has been installed.
  21.  
  22.  
  23. -- Configuring incomplete, errors occurred!
  24. See also "C:/Users/Mark/Src/tcl-act/example/build/CMakeFiles/CMakeOutput.log".
  25. Microsoft (R) Build Engine version 16.8.3+39993bd9d for .NET Framework
  26. Copyright (C) Microsoft Corporation. All rights reserved.
  27.  
  28. MSBUILD : error MSB1009: Project file does not exist.
  29. Switch: ALL_BUILD.vcxproj
  30. ERROR: could not find example_cutil library in build/ build/Release
  31.  
  32. c:\Users\Mark\Src\tcl-act\example>

Comments

Posted by anticrisis at Tue Feb 02 17:38:09 GMT 2021 [text] [code]

Thank you for testing this! This is caused by your vcpkg being in an unusual place -- The --vcpkg option makes it sound like that's all you have to do, but it isn't. The CMakeLists.txt file is dependent on finding your vcpkg installation. It only looks in two standard places, the parent directory of the project, and the parent's parent. There are many ways to make this more robust, but I do not transmit the --vcpkg option to CMake. Right now, you have to edit the top the CMakeLists.txt to suit your own installation.

Posted by anticrisis at Tue Feb 02 17:41:30 GMT 2021 [text] [code]

One more thing to note: On Windows CMake will also complain about how libsodium is packaged, using an 'unofficial-sodium' name. It notes that the warning is intended for project developers, and can be ignored.