Hello everyone,
I’m encountering this error in one of my projects that I can’t fully understand the cause and I suspect that it has something to do with the compiler used for compilation, so I shared the relevant images below, I would be very grateful if you can help me how to solve it.
My first thought is that there are problems compiling one or more of the libraries in your project. It looks like you have some custom C or C++ libraries. Unfortunately, compile errors in this case often don’t tell you exactly what the problem is in a helpful way.
If you enable the Messages filter in the output window, it may tell you the last thing the compiler was doing before an error occurred. Does this point to any specific library or directory?
Another idea, have you verified that each of your libraries builds in Automation Studio? If you’re unsure which one is causing the issue, you could import each one on its own (plus its dependencies) into a blank project to see if that project builds.
Sometimes these errors can be caused by the way Automation Studio handles C and C++ programs. There are limitations and other special considerations when using C or C++ so it’s possible one of your libraries is doing something the compiler doesn’t understand.
One other thing that came to mind is that these errors remind me of errors I’ve seen when trying to use a library compiled for one target on another target (i.e. I compiled a library for an Intel CPU, exported it, and then tried using it on a C50 which has an ARM processor). Without the original source code, the binary library was not usable because it could not be compiled for an ARM target. However, it looks like the libraries in your project are mostly B&R libraries which should work with any target.
I know it’s not an exact answer, but I hope these tips help. Let us know if you get more information!
I would like to try these solutions, but i wanted to delete and reinstall the program, thinking that I could find a quicker solution to the problem. This time, I am unable to reinstall the program. Unfortunately, I would still like to hear from anyone who has a permanent solution to this problem.
