How to compile OpenCV 3.4 with Visual Studio 15 2017 ARM for UWP?
I have been struggling to compile OpenCV 3.4 for a couple of days now.
Final target of the compile is ARM, since I am currently writing an UWP for Windows 10 IoT Core running on Raspberry Pi 3.
I started my journey from here:
https://developer.microsoft.com/en-us/windows/iot/samples/opencv
where Microsoft provides on GitHub an old OpenCV Version (3.0.0) with all the Visual Studio solutions already configured for ARM, x86 and x64.
x86/x64 compilation was very easy, in fact, and I could achieve it just by following this guide:
How to can I install/configure OpenCV3.2.0 with Visual Studio 2017?
My problem is now down to only ARM compiling - since CMake will return this nice error when used with "Visual Studio 15 2017 ARM" compilers:
By following a couple of posts here:
https://github.com/cppan/cppan/issues/23
I was able to ultimately manage to create a Visual Studio ARM solution. After using:
cmake -G "Visual Studio 15 2017 ARM" ..
with no luck, I tried:
cmake -G "Visual Studio 15 2017 ARM" -DCMAKE_SYSTEM_NAME=WindowsStore
-DCMAKE_SYSTEM_VERSION=10.0 ..
which, apparently, worked in creating a Visual Studio 2017 solution meant to be compiled for ARM.
Anyway, after a long compile time, this is what I got:
At this point, I have tried running the whole procedure again on different PCs and also by trying to repair Visual Studio, ultimately getting the very same outcome.
c++ visual-studio opencv arm windows-10-iot-core
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
add a comment |
I have been struggling to compile OpenCV 3.4 for a couple of days now.
Final target of the compile is ARM, since I am currently writing an UWP for Windows 10 IoT Core running on Raspberry Pi 3.
I started my journey from here:
https://developer.microsoft.com/en-us/windows/iot/samples/opencv
where Microsoft provides on GitHub an old OpenCV Version (3.0.0) with all the Visual Studio solutions already configured for ARM, x86 and x64.
x86/x64 compilation was very easy, in fact, and I could achieve it just by following this guide:
How to can I install/configure OpenCV3.2.0 with Visual Studio 2017?
My problem is now down to only ARM compiling - since CMake will return this nice error when used with "Visual Studio 15 2017 ARM" compilers:
By following a couple of posts here:
https://github.com/cppan/cppan/issues/23
I was able to ultimately manage to create a Visual Studio ARM solution. After using:
cmake -G "Visual Studio 15 2017 ARM" ..
with no luck, I tried:
cmake -G "Visual Studio 15 2017 ARM" -DCMAKE_SYSTEM_NAME=WindowsStore
-DCMAKE_SYSTEM_VERSION=10.0 ..
which, apparently, worked in creating a Visual Studio 2017 solution meant to be compiled for ARM.
Anyway, after a long compile time, this is what I got:
At this point, I have tried running the whole procedure again on different PCs and also by trying to repair Visual Studio, ultimately getting the very same outcome.
c++ visual-studio opencv arm windows-10-iot-core
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
1
look at the project file that MS provides for 3.0 and modify it for 3.4
– magicandre1981
Dec 30 '17 at 18:51
thanks for your input @magicandre1981 but I can't imagine doing what you are suggesting, since OpenCV 3.4 changed many dependencies and probably "manual rewire" is not the most efficient way - given how we'll soon get a new OpenCV version that's will surely add new features and so on
– Guido Magrin
Dec 30 '17 at 22:06
2
Note that compiling for Windows on ARM is not the same as compiling for UWP. If you successfully compile for ARM in the way you are attempting, it will run as a native binary on Windows on an ARM device, but will not be a UWP application. I am sorry that this is not more helpful. Your best bet, right now, is to either manually "rewire" the 3.0 solution that MS provides, or start a conversion for 3.4 manually, following the same basic steps that MS took to create their 3.0 solution.
– Naikrovek
Jan 2 '18 at 12:13
add a comment |
I have been struggling to compile OpenCV 3.4 for a couple of days now.
Final target of the compile is ARM, since I am currently writing an UWP for Windows 10 IoT Core running on Raspberry Pi 3.
I started my journey from here:
https://developer.microsoft.com/en-us/windows/iot/samples/opencv
where Microsoft provides on GitHub an old OpenCV Version (3.0.0) with all the Visual Studio solutions already configured for ARM, x86 and x64.
x86/x64 compilation was very easy, in fact, and I could achieve it just by following this guide:
How to can I install/configure OpenCV3.2.0 with Visual Studio 2017?
My problem is now down to only ARM compiling - since CMake will return this nice error when used with "Visual Studio 15 2017 ARM" compilers:
By following a couple of posts here:
https://github.com/cppan/cppan/issues/23
I was able to ultimately manage to create a Visual Studio ARM solution. After using:
cmake -G "Visual Studio 15 2017 ARM" ..
with no luck, I tried:
cmake -G "Visual Studio 15 2017 ARM" -DCMAKE_SYSTEM_NAME=WindowsStore
-DCMAKE_SYSTEM_VERSION=10.0 ..
which, apparently, worked in creating a Visual Studio 2017 solution meant to be compiled for ARM.
Anyway, after a long compile time, this is what I got:
At this point, I have tried running the whole procedure again on different PCs and also by trying to repair Visual Studio, ultimately getting the very same outcome.
c++ visual-studio opencv arm windows-10-iot-core
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
I have been struggling to compile OpenCV 3.4 for a couple of days now.
Final target of the compile is ARM, since I am currently writing an UWP for Windows 10 IoT Core running on Raspberry Pi 3.
I started my journey from here:
https://developer.microsoft.com/en-us/windows/iot/samples/opencv
where Microsoft provides on GitHub an old OpenCV Version (3.0.0) with all the Visual Studio solutions already configured for ARM, x86 and x64.
x86/x64 compilation was very easy, in fact, and I could achieve it just by following this guide:
How to can I install/configure OpenCV3.2.0 with Visual Studio 2017?
My problem is now down to only ARM compiling - since CMake will return this nice error when used with "Visual Studio 15 2017 ARM" compilers:
By following a couple of posts here:
https://github.com/cppan/cppan/issues/23
I was able to ultimately manage to create a Visual Studio ARM solution. After using:
cmake -G "Visual Studio 15 2017 ARM" ..
with no luck, I tried:
cmake -G "Visual Studio 15 2017 ARM" -DCMAKE_SYSTEM_NAME=WindowsStore
-DCMAKE_SYSTEM_VERSION=10.0 ..
which, apparently, worked in creating a Visual Studio 2017 solution meant to be compiled for ARM.
Anyway, after a long compile time, this is what I got:
At this point, I have tried running the whole procedure again on different PCs and also by trying to repair Visual Studio, ultimately getting the very same outcome.
c++ visual-studio opencv arm windows-10-iot-core
c++ visual-studio opencv arm windows-10-iot-core
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
edited Dec 30 '17 at 15:25
Guido Magrin
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
asked Dec 30 '17 at 15:08
Guido MagrinGuido Magrin
1712518
1712518
1
look at the project file that MS provides for 3.0 and modify it for 3.4
– magicandre1981
Dec 30 '17 at 18:51
thanks for your input @magicandre1981 but I can't imagine doing what you are suggesting, since OpenCV 3.4 changed many dependencies and probably "manual rewire" is not the most efficient way - given how we'll soon get a new OpenCV version that's will surely add new features and so on
– Guido Magrin
Dec 30 '17 at 22:06
2
Note that compiling for Windows on ARM is not the same as compiling for UWP. If you successfully compile for ARM in the way you are attempting, it will run as a native binary on Windows on an ARM device, but will not be a UWP application. I am sorry that this is not more helpful. Your best bet, right now, is to either manually "rewire" the 3.0 solution that MS provides, or start a conversion for 3.4 manually, following the same basic steps that MS took to create their 3.0 solution.
– Naikrovek
Jan 2 '18 at 12:13
add a comment |
1
look at the project file that MS provides for 3.0 and modify it for 3.4
– magicandre1981
Dec 30 '17 at 18:51
thanks for your input @magicandre1981 but I can't imagine doing what you are suggesting, since OpenCV 3.4 changed many dependencies and probably "manual rewire" is not the most efficient way - given how we'll soon get a new OpenCV version that's will surely add new features and so on
– Guido Magrin
Dec 30 '17 at 22:06
2
Note that compiling for Windows on ARM is not the same as compiling for UWP. If you successfully compile for ARM in the way you are attempting, it will run as a native binary on Windows on an ARM device, but will not be a UWP application. I am sorry that this is not more helpful. Your best bet, right now, is to either manually "rewire" the 3.0 solution that MS provides, or start a conversion for 3.4 manually, following the same basic steps that MS took to create their 3.0 solution.
– Naikrovek
Jan 2 '18 at 12:13
1
1
look at the project file that MS provides for 3.0 and modify it for 3.4
– magicandre1981
Dec 30 '17 at 18:51
look at the project file that MS provides for 3.0 and modify it for 3.4
– magicandre1981
Dec 30 '17 at 18:51
thanks for your input @magicandre1981 but I can't imagine doing what you are suggesting, since OpenCV 3.4 changed many dependencies and probably "manual rewire" is not the most efficient way - given how we'll soon get a new OpenCV version that's will surely add new features and so on
– Guido Magrin
Dec 30 '17 at 22:06
thanks for your input @magicandre1981 but I can't imagine doing what you are suggesting, since OpenCV 3.4 changed many dependencies and probably "manual rewire" is not the most efficient way - given how we'll soon get a new OpenCV version that's will surely add new features and so on
– Guido Magrin
Dec 30 '17 at 22:06
2
2
Note that compiling for Windows on ARM is not the same as compiling for UWP. If you successfully compile for ARM in the way you are attempting, it will run as a native binary on Windows on an ARM device, but will not be a UWP application. I am sorry that this is not more helpful. Your best bet, right now, is to either manually "rewire" the 3.0 solution that MS provides, or start a conversion for 3.4 manually, following the same basic steps that MS took to create their 3.0 solution.
– Naikrovek
Jan 2 '18 at 12:13
Note that compiling for Windows on ARM is not the same as compiling for UWP. If you successfully compile for ARM in the way you are attempting, it will run as a native binary on Windows on an ARM device, but will not be a UWP application. I am sorry that this is not more helpful. Your best bet, right now, is to either manually "rewire" the 3.0 solution that MS provides, or start a conversion for 3.4 manually, following the same basic steps that MS took to create their 3.0 solution.
– Naikrovek
Jan 2 '18 at 12:13
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48035118%2fhow-to-compile-opencv-3-4-with-visual-studio-15-2017-arm-for-uwp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48035118%2fhow-to-compile-opencv-3-4-with-visual-studio-15-2017-arm-for-uwp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
look at the project file that MS provides for 3.0 and modify it for 3.4
– magicandre1981
Dec 30 '17 at 18:51
thanks for your input @magicandre1981 but I can't imagine doing what you are suggesting, since OpenCV 3.4 changed many dependencies and probably "manual rewire" is not the most efficient way - given how we'll soon get a new OpenCV version that's will surely add new features and so on
– Guido Magrin
Dec 30 '17 at 22:06
2
Note that compiling for Windows on ARM is not the same as compiling for UWP. If you successfully compile for ARM in the way you are attempting, it will run as a native binary on Windows on an ARM device, but will not be a UWP application. I am sorry that this is not more helpful. Your best bet, right now, is to either manually "rewire" the 3.0 solution that MS provides, or start a conversion for 3.4 manually, following the same basic steps that MS took to create their 3.0 solution.
– Naikrovek
Jan 2 '18 at 12:13