-
Notifications
You must be signed in to change notification settings - Fork 8
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
Feature/omnet6 #16
base: master
Are you sure you want to change the base?
Feature/omnet6 #16
Conversation
Destructors of classes with virtual functions should be marked virtual or non-virtual and non-public. As the CAN buffers are not deleted through a pointer to the base buffer class we make the base buffer class destructor protected and non virtual but make the derived classes have virtual destructors. Use cancelAndDelete instead of raw deletes in the destructors.
Hello! |
I just tried a clean checkout and executed the following commands in the root folder:
Which resulted in a build of libFiCo4OMNeT.so in the I am running Fedora 37 with Clang 15.0.7 and a build of Omnet++ 6.0.1 Maybe you could share the errors you are getting and what platform you use? |
I am usining Omnest 6.0.1 on Windows 10. I tried using the "make makefiles" and "make" commands, but after running "make" the following errors appear:
Are there some limitations for Windows? |
I don't have access to a Windows installation but looking at the error code it seems it cannot find an implementation of the You could check the arguments |
Can you please tell me to what arguments you are referring to exactly? Or what are the expected arguments? |
I would assume that the fire function also exists in omnest as the difference is mainly a licensing difference. Maybe that some of the specific paths are different but here is an explanation of what is happening. So after compiling all the compiled object files are linked together in a shared object (dll on windows). But as you are using symbols (functions and objects) from an external library you need to provide a definition (implementation) of them to the linker. This is done by telling the linker to dynamically link the Omnet/Omnest libraries in which it can find the needed functions and objects such as the In the case of Fico4Omnet on my Linux installation this results in the following linker arguments in the output of
Of which the following are relevant |
Try including the cresultfilter header in |
I tried to include
What generates those files? |
Those are the build artifacts, i.e the library that you are trying to build. Since building fails for omnet6 you are missing those artifacts ;) Could you try building a release build instead of a debug build, I see now that for me it defaults to a release build which seems to work and for you it defaults to a debug build which fails. |
Thank you for your response! I also tried in release mode, but still the same result. Just FIY, maybe it helps in the further development of this library, I tried to run it in a virtual machine with Fedora 37 and it worked. So maybe there are some more limitations for Windows. |
This pull request: