According to this guide: https://libiec61850.com/libiec61850/documentation/building-the-library/
I use CMake and the library (libiec61850-1.4.0); it creates the files in custom folders "builder/32" and "builder/64" when I finish with both I open them with VisualStudio 2019 (16.4.3) Community. The next step is to Build and for strange reasons I got the library and .dll files in folders: "builder\64\src\Debug" and "builder\32\src\Debug" instead of "iec61850-shared" folder. When I add the native dll to my System32 in Windows 10 1903 and open dotnet project I can't start any project inside. My first try was example1 and after installing native .dll, the error still holds: "Unable to find an entry point named ‘IedConnection_create’ in DLL ‘iec61850’".
What am I doing wrong? or What am I missing?
Also I tried to paste native .dll in bin/debug folder -in this case example1 withind dotnet folder- and the error is the same.
In addition to that, I tried with the renamed iec61850dotnet to iec61850 assembly and the same error occurs.
According to this guide: https://libiec61850.com/libiec61850/documentation/building-the-library/ I use CMake and the library (libiec61850-1.4.0); it creates the files in custom folders "builder/32" and "builder/64" when I finish with both I open them with VisualStudio 2019 (16.4.3) Community. The next step is to Build and for strange reasons I got the library and .dll files in folders: "builder\64\src\Debug" and "builder\32\src\Debug" instead of "iec61850-shared" folder. When I add the native dll to my System32 in Windows 10 1903 and open dotnet project I can't start any project inside. My first try was example1 and after installing native .dll, the error still holds: "Unable to find an entry point named ‘IedConnection_create’ in DLL ‘iec61850’". What am I doing wrong? or What am I missing? Also I tried to paste native .dll in bin/debug folder -in this case example1 withind dotnet folder- and the error is the same. In addition to that, I tried with the renamed iec61850dotnet to iec61850 assembly and the same error occurs.