[pcl:arm64-uwp] compilation build failure
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Start by reviewing the linked vcpkg issue 31655, its command output, and the attached log for the arm64-uwp failure. Trace the reported build failure from the vcpkg reproduction and verify completion when .\vcpkg install pcl:arm64-uwp --allow-unsupported succeeds.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C++
- Stars
- 11.2k
- Forks
- 4.7k
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PointCloudLibrary/pcl
-
kind: bug status: triage
Difficulty 1/5 Under an hour Newbie friendliness 82/100
PointCloudLibrary/pcl#6536 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
PointCloudLibrary/pcl#6509 · 1 comment ·
Maintainers usually reply within 3 days
-
kind: bug status: triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PointCloudLibrary/pcl#6537 ·
Maintainers usually reply within 3 days
-
[cmake] QHULL/FLANN dll missing when linking single modulePossibly taken @SIDDARTHAREDDY8 claimed this 6 days ago. Openkind: bug module: cmake
Difficulty 3/5 Half a day Newbie friendliness 50/100
PointCloudLibrary/pcl#6522 · 1 comment ·
Maintainers usually reply within 3 days
-
kind: bug status: triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PointCloudLibrary/pcl#6395 ·
Maintainers usually reply within 3 days
All issues in PointCloudLibrary/pcl
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nextcloud/passman-android#214 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
feature wsl2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
microsoft/WSL#42306 · 3 comments ·
Maintainers usually reply within 1 day
-
2026.11.0 fails to install on Intel macOS: requirements.txt pins cryptography==50.0.2 for Darwin x86_64May be free again A pull request for this issue was closed without being merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 87/100
esphome/esphome#22892 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day