Package Details: omnetpp-preview 6.0rc1-1

Git Clone URL: (read-only, click to copy)
Package Base: omnetpp-preview
Description: OMNeT++ Discrete Event Simulator. OMNeT++ is an extensible, modular, component-based C++ simulation library and framework, primarily for building network simulators: preview version
Upstream URL:
Keywords: networks omnet++ omnetpp simulation veins
Licenses: custom
Conflicts: omnetpp
Provides: omnetpp
Replaces: omnetpp-qt
Submitter: a36233
Maintainer: a36233 (ekkelett)
Last Packager: ekkelett
Votes: 9
Popularity: 0.000000
First Submitted: 2020-05-26 21:02 (UTC)
Last Updated: 2022-02-22 10:11 (UTC)

Latest Comments

1 2 3 Next › Last »

ekkelett commented on 2022-02-22 10:12 (UTC)

Updated to release candidate one. Please let me know how the package performs as I have not verified it myself.

ekkelett commented on 2021-11-08 07:39 (UTC) (edited on 2021-11-10 19:40 (UTC) by ekkelett)

Thanks @mazen, that's a good catch. I'll add the sourcing of the setenv file.

EDIT: What am I talking about! @a36233 sorted that out. :)

mazen commented on 2021-10-19 21:23 (UTC) (edited on 2021-10-20 14:23 (UTC) by mazen)

Hello @ekkelett, you need to run source setenv before running configure in order for the python error to not occur. I edited the PKGBUILD to do that, and also updated it to the new version, and it worked for me.

ekkelett commented on 2021-06-29 22:35 (UTC)

Hi @itsclobberintime, the Python module should be available from /opt/omnetpp/python (see the folder omnetpp). In which context are you trying to use it, from within the IDE?

itsclobberintime commented on 2021-06-29 06:02 (UTC)

configure: error: Some Python modules required by the IDE were not found: omnetpp pip doesnt have this module(pip3 install omnetpp) and i dont know how to install.

ekkelett commented on 2020-05-23 11:42 (UTC)

I've updated this package to 6.0pre8 at

I've also removed some of the dependencies as they are not in use when we build with the current configuration.

Secondly, I'd like to suggest splitting this package into multiple OMNeT++ packages as long as there is a stable and preview branch. There are plenty of users tied to OMNeT++ 5.X, as it is the latest stable. With that, I'd suggest renaming two parts of the name. Firstly, the TkEnv is deprecated, and as such, I believe we can remove that from the package name. Secondly, we can rename this package to omnetpp-preview or omnetpp-pre, while creating a new package omnetpp with pkgver 5.6.2.

On the note of INET: while the Eclipse-based IDE suggests that you compile INET on start-up, it does this by creating a new project for INET. I'm not sure there are overall benefits to creating a PKGBUILD for a project used as a dependency by a multitude of frameworks (such as RINASim). Still, I could very well be failing to understand the context in which you'd have a PKGBUILD for INET.

blueman commented on 2020-01-07 16:15 (UTC) (edited on 2020-01-07 16:16 (UTC) by blueman)

Hi, the blt dependency is no longer needed since OMNeT++ 4.5 (June 2014). See here:

Rucikir commented on 2019-11-28 22:26 (UTC)

I feel like it could be useful to have a separate package for the inet framework and have this package depend on it, because OMNET++ downloads and compiles inet at startup. A package would allow more tweaks during the compilation. I'm not sure if OMNET++ and inet are very independent, though.

Rucikir commented on 2019-11-28 12:52 (UTC) (edited on 2019-11-28 12:53 (UTC) by Rucikir)

You can find here a patch for 6.0pre5.
- update to 6.0pre5,
- update jdk8-openjdk to jdk-openjdk,
- improve the download url,
- clean trailing whitespaces in PKGBUILD.

a36233 commented on 2019-11-07 11:54 (UTC)

Updated to 6.0pre4 and change default download server to github