FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

build 3.9 for vs2022 error when build jasper · Issue #3574 · arrayfire/arrayfire · GitHub

Repository navigation

build 3.9 for vs2022 error when build jasper #3574

Description

build error when build jasper .

Description

I check the out file all error such as:
vcruntime_c11_stdatomic.h(36): error C2061: 语法错误: 标识符“atomic_bool”
I found answer,
microsoft/vcpkg#36192.
But how can I modify the jasper's CMakeLists.txt
It always do
-- Cleaning sources...
-- Extracting source...

Error Log

CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j25

Build Environment
Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe

Activity

  1. edwinsolisf commented on Aug 5, 2024

    Contributor

    This is likely an upstream problem with vcpkg. I was not able to replicate it with ArrayFire 3.9.0. Try git pull with vcpkg to update the packages before using vcpkg toolchain to build ArrayFire. I'm closing this issue, feel free to reopen it if you find the issue is coming from ArrayFire.

  2. jacobgrass commented on Aug 16, 2024

    I had this same issue trying to build AF on windows. It was mitigated by removing the vcpkg baseline. However, I have been unable to build AF. Are there any updated build instructions?

  3. edwinsolisf commented on Aug 16, 2024

    Contributor

    To build ArrayFire with vcpkg you may run cmake configure with the following command:

    cmake -B build -DCMAKE_TOOLCHAIN_FILE="VCPKG_ROOT_DIR/scripts/buildsystems/vcpkg.cmake" ...

    where VCPKG_ROOT_DIR is the path to the vcpkg root folder. You may also specify other ArrayFire options which backends to build, include tests, Forge, etc.
    Then you run cmake again to build. For example,

    cmake --build build --config RelWithDebInfo -j8

    Let me know if you still experience the vcpkg issue with the above cmake configure command

  4. jacobgrass commented on Aug 16, 2024

    Thanks for the reply Edwin!

    I followed the build instructions here, are they outdated? I have been working on building the source all of this week, to no avail unfortunately. I did end up getting a project to generate by changing the built in baseline in the vcpkg.json to:

    "builtin-baseline": "9a6da16845eca8d6ed70be416c1acbd206894c7f"

    However, the generated project was unable to build with many linker issues. I think following the steps in the build instructions have confused the linker with different versions?

    Switching back to v3.9, the build command you listed fails with

    Installing 137/149 jasper[core,default-features,opengl]:x64-windows@4.0.0#2...
    Building jasper[core,default-features,opengl]:x64-windows@4.0.0#2...
    D:\admin\source\repos\arrayfire\CMakeModules\vcpkg\vcpkg-triplets\x64-windows.cmake: info: loaded overlay triplet from here
    D:\vcpkg\buildtrees\versioning_\versions\jasper\d7f51c26899ba9433a5a3ab92fc5b5887d5c764c: info: installing overlay port from here
    -- Using cached jasper-software-jasper-402d096b39f4f618ad9e6ff2b4fc1b5eb260a2e4.tar.gz.
    -- Cleaning sources at D:/vcpkg/buildtrees/jasper/src/5eb260a2e4-ca02e25be6.clean. Use --editable to skip cleaning for the packages you specify.
    -- Extracting source D:/vcpkg/downloads/jasper-software-jasper-402d096b39f4f618ad9e6ff2b4fc1b5eb260a2e4.tar.gz
    -- Applying patch no_stdc_check.patch
    -- Applying patch fix-library-name.patch
    -- Using source at D:/vcpkg/buildtrees/jasper/src/5eb260a2e4-ca02e25be6.clean
    -- Configuring x64-windows
    -- Building x64-windows-dbg
    CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
        Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j29
        Working Directory: D:/vcpkg/buildtrees/jasper/x64-windows-dbg
        See logs for more information:
          D:\vcpkg\buildtrees\jasper\install-x64-windows-dbg-out.log
    
    Call Stack (most recent call first):
      D:/admin/source/repos/arrayfire/build/build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
      D:/admin/source/repos/arrayfire/build/build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
      buildtrees/versioning_/versions/jasper/d7f51c26899ba9433a5a3ab92fc5b5887d5c764c/portfile.cmake:38 (vcpkg_cmake_install)
      scripts/ports.cmake:192 (include)
    
    
    error: building jasper:x64-windows failed with: BUILD_FAILED
    See https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
    Elapsed time to handle jasper:x64-windows: 12 s
    Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
    Then check for known issues at:
      https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+jasper
    You can submit a new issue at:
      https://github.com/microsoft/vcpkg/issues/new?title=[jasper]+Build+error+on+x64-windows&body=Copy+issue+body+from+D%3A%2Fadmin%2Fsource%2Frepos%2Farrayfire%2Fbuild%2Fbuild%2Fvcpkg_installed%2Fvcpkg%2Fissue_body.md
    
    -- Running vcpkg install - failed
    CMake Error at D:/vcpkg/scripts/buildsystems/vcpkg.cmake:904 (message):
      vcpkg install failed.  See logs for more information:
      D:\admin\source\repos\arrayfire\build\build\vcpkg-manifest-install.log
    Call Stack (most recent call first):
      C:/Program Files/CMake/share/cmake-3.30/Modules/CMakeDetermineSystem.cmake:146 (include)
      CMakeLists.txt:18 (project)
    
    
    -- Configuring incomplete, errors occurred!
    
  5. edwinsolisf commented on Aug 16, 2024

    Contributor

    This confirms that it an issue upstream with vcpkg and jasper. Try looking at previous issues over there or post a new one related to this. In the meantime, could you post the log in D:\vcpkg\buildtrees\jasper\install-x64-windows-dbg-out.log that it produced?

  6. jacobgrass commented on Aug 16, 2024

    I changed the built in baseline because of this issue:
    microsoft/vcpkg#38192

    Unfortunately I just cleared vcpkg. I was planning to remove the manually installed dependencies and rebuild. I also noticed I have CUDA 12.6. Do I need to downgrade?

  7. edwinsolisf commented on Aug 16, 2024

    Contributor

    Regarding the CUDA 12.6, you may apply this pull request and it should work

  8. jacobgrass commented on Aug 16, 2024

    Thanks Edwin! I think I will try to build in linux instead for now.

  9. edwinsolisf commented on Aug 23, 2024

    Contributor

    @jacobgrass @wududu123 I have posted a fix for the jasper build problem. If you are able to test it, let me know if you find any issues with it still.

  10. self-assigned this
    on Aug 23, 2024
  11. brfire commented on Oct 28, 2024

    Thanks for fixing this, I had gotten stuck on it a couple times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


    Back | FazBrowse Home | New Git URL