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
Link error when build with cmake #2
Comments
Hi @AlexandreMunsch , @jeanpierrefortune May i know whether you are able to reproduce this error? thanks! BR |
Hi @AnnnSt I will have a look today. Best regards, |
Hi Alex Thanks again for your reply. error_log.txt BR |
May i know whether you are able to reproduce the error or any solutions ? Thanks a lot for your help. BR |
Hi @AnnnSt, I finally found some time to work on your issue and the good news is that I was able to reproduce it. Now I need some more time to understand what's going on. I'll keep you posted. Best regards, |
Hi @AlexandreMunsch, Thanks again for the update, looking forward for the solution. Any ideas for the below issue as well ? BR
|
Hi @AnnnSt To reproduce your issue yesterday I had to bypass the TOOLCHAIN_FILE definition check in the main CMakeLists.txt file. As soon as I fixed that, by properly settings the CMAKE_TOOLCHAIN_FILE variable in my VSCode build, it all compiled just fine. Any chance you did something similar? If not, I might need more information to help you further like VSCode config files, Windows Kit installed, full log file, etc... Best regards, Note: I'll have a look at your 0.9 issue a bit later on. I'll open an issue on the dedicated repos if a follow up is required. |
Thanks again for your response, Regarding issue 2 on keyple v0.9 Really appreciate your effort on reopening the topic. BR |
As a first step, you can try adding
It's not really a fix. It's more of a local setting related to your environment (IDE, toolchain, dev kits installed, etc...). Everyone's different so I can't commit a fix for that. At least I don't think so...
I think I only went down to GCC 6+ at the time. I'll try 4.6 as soon as I can. Best regards, |
Thanks again for your support , I have included the toolchain file in the cmakelists.txt
Please refer to the logfile from my CMAKE build output as i still got the error: Besides, may i know when the official release date of keyple c++ v2.0 library ? Thanks again BR |
Hi @AnnnSt,
I had a very hard time trying to setup a working version of GCC 4.6 on my laptop but succeeded with GCC 4.7, which I suppose is close enough. Keyple 0.9 is almost compatible with this version. I only had 3 issues (related to the STD lib in fact):
Item 3 is straightforward. Items 1 and 2 should be relatively easy to workaround. Best regards, |
Hi @AnnnSt,
Can you pull the latest version and try again? I think I fixed that problem yesterday.
You can already fetch the existing tags. Though I will release new packages in a very short while (couple of weeks top). Best regards, |
Hi Alex
|
I have tried to fetch the latest code and rebuild again but unfortunately the error still exist , from the error log the unresolved external symbol is from keyple-plugin-stub-cpp-lib , may i know if you built from keyple-cpp-meta repository you will see the same error ? |
Hi Keyple team
I am trying to fetch the keyple-cpp-meta repository and build in my local machine with windowns x86 environment using VSCode, but i face several linking error during the compilation of the cpp examples. Below is an example:
Error LNK2019 unresolved external symbol "__declspec(dllimport) public: __thiscall keyple::plugin::stub::StubPluginFactoryBuilder::Builder::~Builder(void)" (_imp??1Builder@StubPluginFactoryBuilder@stub@plugin@keyple@@QAE@XZ) referenced in function "public: void * __thiscall keyple::plugin::stub::StubPluginFactoryBuilder::Builder::`scalar deleting destructor'(unsigned int)" (??_GBuilder@StubPluginFactoryBuilder@stub@plugin@keyple@@QAEPAXI@Z) under project : UseCase1_ExplicitSelectionAid_Stub and file :Main_ExplicitSelectionAid_Stub.obj
the keyplepluginstubcpplib.lib has exported under build\externals\keyple-plugin-stub-cpp-lib\src\main\Debug, thus i may seek your help regarding the linking error.
Best regards
Ann
The text was updated successfully, but these errors were encountered: