-
Notifications
You must be signed in to change notification settings - Fork 27
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
Run OPC DA server with C++ #14
Comments
Hi there, Captain here:
Regards! |
TBC = OPC ToolKit C++ API (TBC actually means [OPC] ToolBox for C++... the first name of the C++ API) Please mind the paths. And yes, both the release and the debug versions of the TBC use the OTBd for importing symbols (debug version). In order to correctly build the TBC, you would need to first build the TK CORE. The ToolKit CORE (OTB) API is C++, so there's no preference for the Visual Studio you use. Only make sure you use a Visual Studio that supports 64-bit compiling if you would like to build the TBC on 64-bit as well. Rule of thumb for the linker (32-bit example below): Please read the help file, there are sections in how to build the TK CORE (OTB), TK aPI (TBC/TBN) and samples. Compile it with SandCastle - maybe https://github.com/EWSoftware/SHFB works. Mind x64 vs x86 when registering C++ OPC servers and the systems preference in case the same server name is registered for both x64 and x86. NEVER EVER EVER EVER use JIT-architecture switching (AnyCPU) for .NET OPC servers. |
Hello @HovoApoyan , can you please update us on your progress? |
Hi @ro0ter, I stopped working on this project. Thanks for some help. |
I have some questions about the OPC DA server.
I'm build OPCToolbox_VS2019.sln, get the corresponding .libs for DemoServer, then I try to open DemoServer_VS2017.vcxproj and run it, I'm set the already built files to the project linker (path and dependencies).
![image](https://user-images.githubusercontent.com/85103881/189895451-1a39e887-3093-4994-b564-1d99e3d26197.png)
![image](https://user-images.githubusercontent.com/85103881/189895540-895826be-70ab-42da-a489-33bf52622b6f.png)
but I get a linker error
The text was updated successfully, but these errors were encountered: