To clarify I will tell you my steps that I took:
* I installed Visual Studio 2022
* I Installed the PLCnext_Toolchain_2024.0-LTS. I added the Visual studio for C++ with the toolchain.
* I installed the AXC_F_2152_SDK_2024_6 for windows. I zipped that folder but didn’t zipped the axcf2152-mingw_sdk-2024.6.0-24.6.0.81.tar folder.
* I extracted the SDK.I installed the SDK to visual studio
Now when I create a new PLM C++ project I get the following error when I add the target.
I could afterwards add the SDK to the project:
Now I have the following problems with the Arp library that can’t find the path’s. I have a feeling that I’m doing something wrong with the SDK but don’t know what.
The project does everything succesfull when using those in the terminal: I do this in the terminal in VS Studio. I found it strange that it build succesfull even when it doesn’t reconise Arp library.
So if you build the project in Visual Studio, using the Build → Build Solution menu item, does the build succeed?
Is this just a problem with the intellisense feature in Visual Studio?
When closing the files and build again I now got only 2 errors. But I still got 1 error from another project (Testjoep) outside of the current solution (PLCnextPLMProject1).
That’s weird … Visual Studio just calls the same plcncli commands that you executed in the command window, so the result should be the same.
I’m wondering if there might be multiple versions of the plcncli (Toolchain) installed on your machine, and maybe Visual Studio is using a different one that doesn’t have the SDK installed.
Maybe try opening a command window somewhere else, maybe at C:\, and checking plcncli get sdks ?
Is there an entry to a plcncli installation directory in your windows PATH ?
Sorry for the previous comments. After I rebuilded it completed teh build succesfull. It’s probably something in the intelisence indeed that you were talking about.
No problem, I’m glad it worked in the end. I’m not sure what the problem was in this case. The lack of intellisense shouldn’t cause build errors, it’s just a display thing. But probably a symptom of the problem that was causing the build errors.