Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[openmvg:x64-windows-static-md] build failure with static CRT linking. #13447

Closed
FishHe opened this issue Sep 10, 2020 · 6 comments
Closed

[openmvg:x64-windows-static-md] build failure with static CRT linking. #13447

FishHe opened this issue Sep 10, 2020 · 6 comments
Labels
category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. category:port-bug The issue is with a library, which is something the port should already support

Comments

@FishHe
Copy link

FishHe commented Sep 10, 2020

as it is mentioned in #12229

`

main_ComputeFeatures.cpp.obj : error LNK2019: unresolved external symbol __imp_vl_constructor referenced in function "public: __cdecl openMVG::features::SIFT_Image_describer::SIFT_Image_describer(struct openMVG::features::SIFT_Image_describer::Params const &,bool)" (??0SIFT_Image_describer@features@openMVG@@qeaa@AEBUParams@012@_N@Z)

`

I would like to use x64-windows-static-md to build openmvg[software].

@JackBoosY
Copy link
Contributor

@cenit Could you please take a look?

Thanks.

@JackBoosY JackBoosY changed the title [openmvg] build failure with static CRT linking. [openmvg:x64-windows-static-md] build failure with static CRT linking. Sep 10, 2020
@cenit
Copy link
Contributor

cenit commented Sep 10, 2020

It's an open issue that the software feature of openmvg does not build correctly with statically linked libs.
I will investigate it more and I hope it can be fixed soon

@JackBoosY JackBoosY added the category:port-bug The issue is with a library, which is something the port should already support label Sep 10, 2020
@JackBoosY JackBoosY added the category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. label Nov 3, 2020
@JackBoosY
Copy link
Contributor

Ping @cenit, any progress?

@cenit
Copy link
Contributor

cenit commented Jan 27, 2022

to be honest, i don't know.
I saw that openmvg was updated to v2.0 by others, maybe the update fixed the error? sorry i don't have much time

@FrankXie05
Copy link
Contributor

@FishHe Is this issue still exist?

@MonicaLiu0311
Copy link
Contributor

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

5 participants