undefined reference to `virtual thunk to veins::TraCIScenarioManagerLaunchd::finish()'

[a-huk]

When using the veins_inet project on windows omnetpp, I get this error. On linux it is fine.

[sommer]

Using The INET Framework as a basis of other projects works reliably on Linux, but (as of INET 4.2.3) less so on Windows. If you use INET 4.2.4 and the current master version of Veins (which adds support for this version) things should work on OMNeT++ 5.6.2

[a-huk]

Cheers, will try it.

[sommer]

I am assuming using INET 4.2.4 and b14411eb9aaff0a475899c925015be1f844af505 on OMNeT++ 5.6.2 fixed this. Please add a comment here if it did not.

[shriyaBhat1]

undefined reference to `virtual thunk to veins::TraCIScenarioManagerLaunchd::finish()'

Hello Sir Have you resolved this error? Even I'm also getting the same problem so help me.

[Thilaga22]

I am using Veins current version , OMNEST 5.6.2 and inet-4.2.5-e0c1741924 version, windows 10. I am still getting the same error. Any help on this?

[imssuthar]

undefined reference to `virtual thunk to veins::TraCIScenarioManagerLaunchd::finish()'

Hello Sir Have you resolved this error? Even I'm also getting the same problem so help me.

@shriyaBhat1 did you get solution for this?

[zenobertesina]

I'm using the 5.6.2 version of Omnet++ and when I try to run the veins_inet subproject on windows 10 I get the following error. I have tried multiple versions of inet (4.2.1, 4.2.2, 4.2.5) with veins 5.1, but the error is still there. I also tried to use the inet-master and veins-master versions, because they work on the on the computer of a collegue, but the situation still doesn't change. I also try to use different versions of SUMO (1.8.0, 1.10.0). The interesting thing is that Inet and Veins work well separately, but when I try to connect them the simulation crashes. Do you have any solution for this problem?

Thanks, Zeno Bertesina

[sommer]

The patch mentioned in the issue is now merged into Veins 5.2 (see https://github.com/sommer/veins/releases/tag/veins-5.2)

[sommer]

I have tried multiple versions of inet (4.2.1, 4.2.2, 4.2.5) [and] different versions of SUMO (1.8.0, 1.10.0). The interesting thing is that Inet and Veins work well separately, but when I try to connect them the simulation crashes.

If you can consider switching to Veins 5.2, there is a table of tested combinations of OMNeT++ + INET + SUMO + Veins available on http://veins.car2x.org/download/.

[zenobertesina]

I have followed your suggestion (Veins 5.2, Inet 4.2.5, Sumo 1.10.0), but the problem is still there.

[sommer]

I can only recommend giving Instant Veins a try. This should work out of the box.

[nawroooz]

I have the same problem and I tried to import inet-4.2.4 but still facing the same issue please can you help me?

[tania0011]

I'm using the 5.6.2 version of Omnet++ and when I try to run the veins_inet subproject on windows 10 I get the following error. I have tried multiple versions of inet (4.2.1, 4.2.2, 4.2.5) with veins 5.1, but the error is still there. I also tried to use the inet-master and veins-master versions, because they work on the on the computer of a collegue, but the situation still doesn't change. I also try to use different versions of SUMO (1.8.0, 1.10.0). The interesting thing is that Inet and Veins work well separately, but when I try to connect them the simulation crashes. Do you have any solution for this problem?

Thanks, Zeno Bertesina

hiii i have the same problem please how did you fix it

[nawroooz]

Actually I just switched to the version of omnet which is build in on virtual box since it comes with whole package of frameworks together without need for individual installation.