When can a DLL not be found? (When using Google Protobuffer)

Question

question

Lucas Z asked Mar 28, '22 Lucas Z edited Apr 4, '22

When can a DLL not be found? (When using Google Protobuffer)

In our model, we would like to communicatie with an external model where certain decisions are optimised. We call a DLL from Flexsim, this DLL calls then calls the external model and takes care of the rest.

Initial tests using the DLL were working well, except that we want to use Goolgle protobuffers to communicate from the DLL to the model, which includes some extra headers and a .cc file into the dll project. After including them, Flexsim cannot find the DLL anymore, everything else remaining the same. (exception: Dll Error : could not connect to exported dll function for /Tools/UserCommands/CallDll/code. Windows Error Code: 126)

When removing the additional files, Flexsim can find the DLL again. Currently we are not passing any parameters to the DLL function. What could be the cause for this to happen? Any help would be appreciated!

Software Version:

FlexSim 22.0.1

dll dll maker

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2022-03-28T16:22:33Z

Phil BoBo answered Mar 28, '22 Phil BoBo edited Mar 28, '22

This isn't really a FlexSim question. This is a Google Protobuffers question.

Make sure you are using the appropriate platform (64-bit, not 32-bit) version of the libprotobuf library.

Make sure you are statically linking the protobuf library into your DLL. See "DLLs vs. static linking" section of protobuf/README.md at master · protocolbuffers/protobuf · GitHub

Based on what is happening, it sounds like you are dynamically linking the protobuf library, so when FlexSim tries to load your DLL, it then tries to load the dependency DLLs for that library (probably libprotobuf.dll or libprotoc.dll), and since it can't find them, it can't load your DLL.

Google Protobuffers is not just a simple C++ cc file and some header files. It's a large library of code that is required for those files to work. You need to actually embed all that code into your DLL for those generated C++ files to work.

question