pcl
pcl copied to clipboard
[pcl:arm64-uwp] compilation build failure
Describe the error
We have a custom PCL project we're using in a web service that we would much rather run directly on a Hololens 2 within Unity for our healthcare research project. We have discovered that arm64-windows is not sufficient, and that we need an arm64-uwp build in order to include it in our Unity3d application.
I ran the following command:
.\vcpkg install pcl:arm64-uwp --allow-unsupported
Please see the following issue created on vcpkg repo for command line results/errors. https://github.com/microsoft/vcpkg/issues/31655
To Reproduce
Please see the following issue created on vcpkg repo to reproduce.
https://github.com/microsoft/vcpkg/issues/31655
Mainly, I used similar commands that were successful, such as
.\vcpkg install pcl:x64-windows
.\vcpkg install pcl:arm64-windows
There's a full command line output plus log file attached.
Your Environment (please complete the following information):
- OS: Windows 11 Pro x64
- Compiler: MSVC - Visual Studio 17.6.1
- PCL Version 1.13
- PCL Type: Installed with VCPKG
If PCL was compiled from source or failure in compiling PCL itself:
- GPU, Kinfu, CUDA enabled? Default settings only.
- List and Version of dependencies used. Default settings only. Installed current version of PCL as of a few days ago.
- Compilation flags are used. This was through the magic of the build button in Visual Studio.
If compiling against PCL:
- Checked Configuration Manager in Visual Studio and reference the vckpg installed folder. This was configured correctly as I was able to compile for x64-windows and arm64-windows using the same environment.
Possible Solution
I would be willing to help make this a supported build, but it's been many years since I've worked in C++, and I'm not that familiar yet with the particulars of PCL compilation build process. Some guidance and direction on first steps would be tremendously helpful.
See my post on vcpkg - it fails already with building PCLs dependencies and hence not PCL itself. Though that will probably come, since we don't build for arm at all 😢
It succeeds for arm64-windows. It fails for arm64-uwp. Sounds like a lost cause then.
On Wed, May 31, 2023 at 12:51 AM Lars Glud @.***> wrote:
See my post on vcpkg - it fails already with building PCLs dependencies and hence not PCL itself. Though that will probably come, since we don't build for arm at all 😢
— Reply to this email directly, view it on GitHub https://github.com/PointCloudLibrary/pcl/issues/5732#issuecomment-1569491705, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOLLQL4JTHI6TY4T5DBMALXI3E53ANCNFSM6AAAAAAYUNSEFU . You are receiving this because you authored the thread.Message ID: @.***>
--
Andrew Conklin https://linkedin.com/in/adconk 202-288-5595 <(202)%20288-5595>
@adconk You could try to create a custom build of PCL while removing boost-filesystem as a dependency. boost-filesystem is mainly used in the modules apps, io, outofcore, tools, and visualization. If you disable the affected modules and/or rewrite the code that uses boost-filesystem to use std::filesystem (C++17) instead, you might be able to build without boost-filesystem.