open62541 | Open source implementation of OPC UA

To run Visual Studio on an .sln file means to open it in VS, then click on Build in the menu bar and then on Build solution. This was new for me, thanks everyone for hinting me in the right direction.

There is a sample code for a GDS from the OPC Foundation here. But it is only community maintained and managing devices via Pull and Push can be quite cumbersome with the GDS Client application. But it was used for a while in IOP Workshops and for V1.04 operation with RSA certs should still work according to standards. There are some commercial GDS offerings in the pipeline by different vendors, given security is in the play I recommend use rather commercial ones. For implementing and testing the GDS Pull/Push services for a UA server the sample server should be sufficient.

You can use SET() to set the compiler flags. Check the CMake documentation

You can set the CMAKE_CXX_FLAGS to the flags you want to pass to the compiler

Do i need to do my analysis on all files separately or is it possible to throw in the whole project like with cppcheck?

Frama-C can actually analyze the entire project in one go provided multiple files do not define the same symbols. See http://blog.frama-c.com/index.php?post/2018/01/25/Analysis-scripts%3A-helping-automate-case-studies, paragraph "Setting sources and testing parsing":

The list of source files to be given to Frama-C can be obtained from the compile_commands.json file. However, it is often the case that the software under analysis contains several binaries, each requiring a different set of sources. The JSON compilation database does not map the sources used to produce each binary, so it is not always possible to entirely automate the process.

The key point in your case is that the compilation_commands.json instructs Frama-C on how to parse each file, but you must still supply the files you want to see parsed yourself. With your current command-line, Frama-C tries to interpret /path/to/open62541/src/ as a file (and fails), and has no other file to parse. This is why you get the error User Error: cannot find entry point 'main'.

Thus, you must specify the files you want to parse on the command-line. This can be done in two ways:

• manually, by extracting the files referenced in compilation_commands.json
• automatically, using the frama-c-script helpers, described at http://blog.frama-c.com/index.php?post/2019/01/16/Setting-up-an-analysis-with-the-help-of-frama-c-script

I used the first approach, but I suggest you use the second, as frama-c-script is very helpful to start a first analysis.

Once you have done this listing step, you will encounter at least three more problems:

• Frama-C will choke on # include , because this file is not present in the standard C library bundled with Frama-C. Either remove this include in the source files, or add an empty sys/param.h somewhere
• some .c files refer to generated headers that are not present in the git repo of open62541. So you will need to compile the repo to get those headers before launching Frama-C.
• Frama-C will also choke on the definition of the macro UA_STATIC_ASSERT in architecture_definitions.h. I did not investigate whether one of the definitions was accepted, and I simply defined it to the empty macro.

After all this, you should be good to go.

I solve this problem myself

I tested other open62541 version.

It is work. Just changed open62541