Configure RInside with Veins and OMNET++ on WindowsHow to set up Eclipse + StatET + Rcpp on WindowsIs it possible to use RInside in omnet++/Veins project to benefit from rich R featuresImplementing different stages in Veins Omnet++Veins LTE Omnet++ Errorworking with Region of interest in Omnet++ ( veins)How to run veins simulation on omnet++?Understanding visuals in VEINS and Omnet++Veins Omnet++ building errorerror while building omnet++ veinsIs it possible to use RInside in omnet++/Veins project to benefit from rich R featuresOmnet++ sumo and veinsOMNET++: importing Simulte “PGWstandard” into veins
Is it logically or scientifically possible to artificially send energy to the body?
Bullying boss launched a smear campaign and made me unemployable
How to prevent "they're falling in love" trope
I would say: "You are another teacher", but she is a woman and I am a man
Can compressed videos be decoded back to their uncompresed original format?
What is a romance in Latin?
Do UK voters know if their MP will be the Speaker of the House?
Can a virus destroy the BIOS of a modern computer?
Is it inappropriate for a student to attend their mentor's dissertation defense?
ssTTsSTtRrriinInnnnNNNIiinngg
Could the museum Saturn V's be refitted for one more flight?
How badly should I try to prevent a user from XSSing themselves?
What killed these X2 caps?
What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?
Why can't we play rap on piano?
Expand and Contract
Is "remove commented out code" correct English?
Solving a recurrence relation (poker chips)
Can I run a new neutral wire to repair a broken circuit?
Why doesn't using multiple commands with a || or && conditional work?
Why would the Red Woman birth a shadow if she worshipped the Lord of the Light?
Forgetting the musical notes while performing in concert
Avoiding direct proof while writing proof by induction
How do I handle a potential work/personal life conflict as the manager of one of my friends?
Configure RInside with Veins and OMNET++ on Windows
How to set up Eclipse + StatET + Rcpp on WindowsIs it possible to use RInside in omnet++/Veins project to benefit from rich R featuresImplementing different stages in Veins Omnet++Veins LTE Omnet++ Errorworking with Region of interest in Omnet++ ( veins)How to run veins simulation on omnet++?Understanding visuals in VEINS and Omnet++Veins Omnet++ building errorerror while building omnet++ veinsIs it possible to use RInside in omnet++/Veins project to benefit from rich R featuresOmnet++ sumo and veinsOMNET++: importing Simulte “PGWstandard” into veins
I have been trying to configure RInside with Veins and OMNET++, but finding some issues.
After going through the discussion in Is it possible to use RInside in omnet++/Veins project to benefit from rich R features and How to set up Eclipse + StatET + Rcpp on Windows, I created a new project (shared type) in omnet++ and tried to configure RInside it. I am experiencing some errors ("undefined reference to RInside::operator[]", "undefined reference to RInside::parseEvalQ")
.
I know that this is a linking error. I am fairly new to C++ configurations and eclipse based IDEs so struggling to figure out what's wrong. I am attaching the screenshots of the configurations as well. I would really appreciate if someone can help.
Update (after successfully building RInside and making sure that the tool chain is right)
Here is the makefrag file
#
# on windows we have to link with the ws2_32 (winsock2) library as it is no longer added to the omnetpp system libraries by default (as of OMNeT++ 5.1)
# copied from INET Framework (inet-3.6.0) makefrag
#
ifeq ($(PLATFORM),win32.x86_64)
LIBS += -lws2_32
DEFINES += -DINET_EXPORT
ENABLE_AUTO_IMPORT=-Wl,--enable-auto-import
LDFLAGS := $(filter-out $(ENABLE_AUTO_IMPORT), $(LDFLAGS))
R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")
R_ARCH := --arch $(shell echo 'cat(.Platform$$r_arch)' | R --vanilla --slave)
sources := $(wildcard *.cpp)
programs := $(sources:.cpp=)
## include headers and libraries for R
RCPPFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config LAPACK_LIBS)
## include headers and libraries for Rcpp interface classes
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
## include headers and libraries for RInside embedding classes
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
#DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
#LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
endif
omnet++ veins rinside
add a comment |
I have been trying to configure RInside with Veins and OMNET++, but finding some issues.
After going through the discussion in Is it possible to use RInside in omnet++/Veins project to benefit from rich R features and How to set up Eclipse + StatET + Rcpp on Windows, I created a new project (shared type) in omnet++ and tried to configure RInside it. I am experiencing some errors ("undefined reference to RInside::operator[]", "undefined reference to RInside::parseEvalQ")
.
I know that this is a linking error. I am fairly new to C++ configurations and eclipse based IDEs so struggling to figure out what's wrong. I am attaching the screenshots of the configurations as well. I would really appreciate if someone can help.
Update (after successfully building RInside and making sure that the tool chain is right)
Here is the makefrag file
#
# on windows we have to link with the ws2_32 (winsock2) library as it is no longer added to the omnetpp system libraries by default (as of OMNeT++ 5.1)
# copied from INET Framework (inet-3.6.0) makefrag
#
ifeq ($(PLATFORM),win32.x86_64)
LIBS += -lws2_32
DEFINES += -DINET_EXPORT
ENABLE_AUTO_IMPORT=-Wl,--enable-auto-import
LDFLAGS := $(filter-out $(ENABLE_AUTO_IMPORT), $(LDFLAGS))
R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")
R_ARCH := --arch $(shell echo 'cat(.Platform$$r_arch)' | R --vanilla --slave)
sources := $(wildcard *.cpp)
programs := $(sources:.cpp=)
## include headers and libraries for R
RCPPFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config LAPACK_LIBS)
## include headers and libraries for Rcpp interface classes
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
## include headers and libraries for RInside embedding classes
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
#DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
#LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
endif
omnet++ veins rinside
1
My recommendation is to start trying to build (some of) the supplied examples to validate your local toolchain. If that works, try 'porting' to Eclipse, CMake, ... At some point in the past the contributed CMakefiles worked but I don;t if a) they every worked on Windows or b) if they are current. I use the standard R tools...
– Dirk Eddelbuettel
Mar 7 at 22:44
1
OMNeT++ simulations are traditionally built via opp_makemake, which creates GNU Makefiles. An easy way to tweak these Makefiles to use custom include paths and libraries is the use of a makefrag file, which contains a fragment of code that will be inserted into the created Makefile. Try building Veins, check the created Makefile in src/, compare this with the makefrag file in src/ and try to take code from RInside's sample Makefiles, e.g., github.com/eddelbuettel/rinside/blob/6699d52/inst/examples/…
– Christoph Sommer
Mar 8 at 0:12
Thanks Dirk and Christoph! Really appreciate your suggestions. I will post my findings around these.
– user8561039
Mar 8 at 6:20
add a comment |
I have been trying to configure RInside with Veins and OMNET++, but finding some issues.
After going through the discussion in Is it possible to use RInside in omnet++/Veins project to benefit from rich R features and How to set up Eclipse + StatET + Rcpp on Windows, I created a new project (shared type) in omnet++ and tried to configure RInside it. I am experiencing some errors ("undefined reference to RInside::operator[]", "undefined reference to RInside::parseEvalQ")
.
I know that this is a linking error. I am fairly new to C++ configurations and eclipse based IDEs so struggling to figure out what's wrong. I am attaching the screenshots of the configurations as well. I would really appreciate if someone can help.
Update (after successfully building RInside and making sure that the tool chain is right)
Here is the makefrag file
#
# on windows we have to link with the ws2_32 (winsock2) library as it is no longer added to the omnetpp system libraries by default (as of OMNeT++ 5.1)
# copied from INET Framework (inet-3.6.0) makefrag
#
ifeq ($(PLATFORM),win32.x86_64)
LIBS += -lws2_32
DEFINES += -DINET_EXPORT
ENABLE_AUTO_IMPORT=-Wl,--enable-auto-import
LDFLAGS := $(filter-out $(ENABLE_AUTO_IMPORT), $(LDFLAGS))
R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")
R_ARCH := --arch $(shell echo 'cat(.Platform$$r_arch)' | R --vanilla --slave)
sources := $(wildcard *.cpp)
programs := $(sources:.cpp=)
## include headers and libraries for R
RCPPFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config LAPACK_LIBS)
## include headers and libraries for Rcpp interface classes
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
## include headers and libraries for RInside embedding classes
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
#DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
#LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
endif
omnet++ veins rinside
I have been trying to configure RInside with Veins and OMNET++, but finding some issues.
After going through the discussion in Is it possible to use RInside in omnet++/Veins project to benefit from rich R features and How to set up Eclipse + StatET + Rcpp on Windows, I created a new project (shared type) in omnet++ and tried to configure RInside it. I am experiencing some errors ("undefined reference to RInside::operator[]", "undefined reference to RInside::parseEvalQ")
.
I know that this is a linking error. I am fairly new to C++ configurations and eclipse based IDEs so struggling to figure out what's wrong. I am attaching the screenshots of the configurations as well. I would really appreciate if someone can help.
Update (after successfully building RInside and making sure that the tool chain is right)
Here is the makefrag file
#
# on windows we have to link with the ws2_32 (winsock2) library as it is no longer added to the omnetpp system libraries by default (as of OMNeT++ 5.1)
# copied from INET Framework (inet-3.6.0) makefrag
#
ifeq ($(PLATFORM),win32.x86_64)
LIBS += -lws2_32
DEFINES += -DINET_EXPORT
ENABLE_AUTO_IMPORT=-Wl,--enable-auto-import
LDFLAGS := $(filter-out $(ENABLE_AUTO_IMPORT), $(LDFLAGS))
R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")
R_ARCH := --arch $(shell echo 'cat(.Platform$$r_arch)' | R --vanilla --slave)
sources := $(wildcard *.cpp)
programs := $(sources:.cpp=)
## include headers and libraries for R
RCPPFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R $(R_ARCH) CMD config LAPACK_LIBS)
## include headers and libraries for Rcpp interface classes
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
## include headers and libraries for RInside embedding classes
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R $(R_ARCH) --vanilla --slave)
#DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
#LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
endif
omnet++ veins rinside
omnet++ veins rinside
edited Mar 13 at 4:10
user8561039
asked Mar 7 at 22:41
user8561039user8561039
467
467
1
My recommendation is to start trying to build (some of) the supplied examples to validate your local toolchain. If that works, try 'porting' to Eclipse, CMake, ... At some point in the past the contributed CMakefiles worked but I don;t if a) they every worked on Windows or b) if they are current. I use the standard R tools...
– Dirk Eddelbuettel
Mar 7 at 22:44
1
OMNeT++ simulations are traditionally built via opp_makemake, which creates GNU Makefiles. An easy way to tweak these Makefiles to use custom include paths and libraries is the use of a makefrag file, which contains a fragment of code that will be inserted into the created Makefile. Try building Veins, check the created Makefile in src/, compare this with the makefrag file in src/ and try to take code from RInside's sample Makefiles, e.g., github.com/eddelbuettel/rinside/blob/6699d52/inst/examples/…
– Christoph Sommer
Mar 8 at 0:12
Thanks Dirk and Christoph! Really appreciate your suggestions. I will post my findings around these.
– user8561039
Mar 8 at 6:20
add a comment |
1
My recommendation is to start trying to build (some of) the supplied examples to validate your local toolchain. If that works, try 'porting' to Eclipse, CMake, ... At some point in the past the contributed CMakefiles worked but I don;t if a) they every worked on Windows or b) if they are current. I use the standard R tools...
– Dirk Eddelbuettel
Mar 7 at 22:44
1
OMNeT++ simulations are traditionally built via opp_makemake, which creates GNU Makefiles. An easy way to tweak these Makefiles to use custom include paths and libraries is the use of a makefrag file, which contains a fragment of code that will be inserted into the created Makefile. Try building Veins, check the created Makefile in src/, compare this with the makefrag file in src/ and try to take code from RInside's sample Makefiles, e.g., github.com/eddelbuettel/rinside/blob/6699d52/inst/examples/…
– Christoph Sommer
Mar 8 at 0:12
Thanks Dirk and Christoph! Really appreciate your suggestions. I will post my findings around these.
– user8561039
Mar 8 at 6:20
1
1
My recommendation is to start trying to build (some of) the supplied examples to validate your local toolchain. If that works, try 'porting' to Eclipse, CMake, ... At some point in the past the contributed CMakefiles worked but I don;t if a) they every worked on Windows or b) if they are current. I use the standard R tools...
– Dirk Eddelbuettel
Mar 7 at 22:44
My recommendation is to start trying to build (some of) the supplied examples to validate your local toolchain. If that works, try 'porting' to Eclipse, CMake, ... At some point in the past the contributed CMakefiles worked but I don;t if a) they every worked on Windows or b) if they are current. I use the standard R tools...
– Dirk Eddelbuettel
Mar 7 at 22:44
1
1
OMNeT++ simulations are traditionally built via opp_makemake, which creates GNU Makefiles. An easy way to tweak these Makefiles to use custom include paths and libraries is the use of a makefrag file, which contains a fragment of code that will be inserted into the created Makefile. Try building Veins, check the created Makefile in src/, compare this with the makefrag file in src/ and try to take code from RInside's sample Makefiles, e.g., github.com/eddelbuettel/rinside/blob/6699d52/inst/examples/…
– Christoph Sommer
Mar 8 at 0:12
OMNeT++ simulations are traditionally built via opp_makemake, which creates GNU Makefiles. An easy way to tweak these Makefiles to use custom include paths and libraries is the use of a makefrag file, which contains a fragment of code that will be inserted into the created Makefile. Try building Veins, check the created Makefile in src/, compare this with the makefrag file in src/ and try to take code from RInside's sample Makefiles, e.g., github.com/eddelbuettel/rinside/blob/6699d52/inst/examples/…
– Christoph Sommer
Mar 8 at 0:12
Thanks Dirk and Christoph! Really appreciate your suggestions. I will post my findings around these.
– user8561039
Mar 8 at 6:20
Thanks Dirk and Christoph! Really appreciate your suggestions. I will post my findings around these.
– user8561039
Mar 8 at 6:20
add a comment |
1 Answer
1
active
oldest
votes
I gave integrating RInside and Veins (version 5 alpha 1) a quick try and can report success.
I installed RInside by running R and executing install.packages('RInside')
.
I then amended the following lines (mostly copied from the RInside examples GNUMakefile) to the Veins src/makefrag
file:
# determine flags for RInside
R_HOME := $(shell R RHOME)
RCPPFLAGS := $(shell $(R_HOME)/bin/R CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R CMD config LAPACK_LIBS)
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
# feed to opp_makemake
DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
After that, I could use R inside Veins. I tried this by copying code from RInside rinside_sample0.cpp
to Veins BaseConnectionManager.cc
as follows:
diff --git a/src/veins/base/connectionManager/BaseConnectionManager.cc b/src/veins/base/connectionManager/BaseConnectionManager.cc
index 879e90d244..8e9eba10e8 100644
--- a/src/veins/base/connectionManager/BaseConnectionManager.cc
+++ b/src/veins/base/connectionManager/BaseConnectionManager.cc
@@ -1,3 +1,5 @@
+#include <RInside.h>
+
#include "veins/base/connectionManager/BaseConnectionManager.h"
#include "veins/base/connectionManager/NicEntryDebug.h"
@@ -42,6 +44,12 @@ void BaseConnectionManager::initialize(int stage)
// BaseModule::initialize(stage);
if (stage == 0) {
+
+ // Hello R!
+ RInside R;
+ R["txt"] = "Hello, world!n";
+ R.parseEvalQ("cat(txt)");
+
drawMIR = hasPar("drawMaxIntfDist") ? par("drawMaxIntfDist").boolValue() : false;
EV_TRACE << "initializing BaseConnectionManagern";
Compiling Veins (./configure
followed by make
) and running the tutorial example (cd examples/veins
followed by ./run -u Cmdenv
) produced the desired output:
OMNeT++ Discrete Event Simulation (C) 1992-2018 Andras Varga, OpenSim Ltd.
Version: 5.4.1, build: 180629-5e28390, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer
Setting up Cmdenv...
Loading NED files from ../../src/veins: 41
Loading NED files from .: 1
Loading NED files from /Users/sommer/src/veins/examples/veins: 1
Preparing for running configuration General, run #0...
Assigned runID=General-0-20190308-18:16:24-23603
Setting up network "RSUExampleScenario"...
Initializing...
Hello, world!
Running simulation...
(Note the Hello, world!
output during initialization of the simulation.)
Building on Windows will likely mean copying lines from the RInside examples Makefile.win file instead.
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Sure! updated the question.
– user8561039
Mar 13 at 0:44
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55053980%2fconfigure-rinside-with-veins-and-omnet-on-windows%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I gave integrating RInside and Veins (version 5 alpha 1) a quick try and can report success.
I installed RInside by running R and executing install.packages('RInside')
.
I then amended the following lines (mostly copied from the RInside examples GNUMakefile) to the Veins src/makefrag
file:
# determine flags for RInside
R_HOME := $(shell R RHOME)
RCPPFLAGS := $(shell $(R_HOME)/bin/R CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R CMD config LAPACK_LIBS)
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
# feed to opp_makemake
DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
After that, I could use R inside Veins. I tried this by copying code from RInside rinside_sample0.cpp
to Veins BaseConnectionManager.cc
as follows:
diff --git a/src/veins/base/connectionManager/BaseConnectionManager.cc b/src/veins/base/connectionManager/BaseConnectionManager.cc
index 879e90d244..8e9eba10e8 100644
--- a/src/veins/base/connectionManager/BaseConnectionManager.cc
+++ b/src/veins/base/connectionManager/BaseConnectionManager.cc
@@ -1,3 +1,5 @@
+#include <RInside.h>
+
#include "veins/base/connectionManager/BaseConnectionManager.h"
#include "veins/base/connectionManager/NicEntryDebug.h"
@@ -42,6 +44,12 @@ void BaseConnectionManager::initialize(int stage)
// BaseModule::initialize(stage);
if (stage == 0) {
+
+ // Hello R!
+ RInside R;
+ R["txt"] = "Hello, world!n";
+ R.parseEvalQ("cat(txt)");
+
drawMIR = hasPar("drawMaxIntfDist") ? par("drawMaxIntfDist").boolValue() : false;
EV_TRACE << "initializing BaseConnectionManagern";
Compiling Veins (./configure
followed by make
) and running the tutorial example (cd examples/veins
followed by ./run -u Cmdenv
) produced the desired output:
OMNeT++ Discrete Event Simulation (C) 1992-2018 Andras Varga, OpenSim Ltd.
Version: 5.4.1, build: 180629-5e28390, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer
Setting up Cmdenv...
Loading NED files from ../../src/veins: 41
Loading NED files from .: 1
Loading NED files from /Users/sommer/src/veins/examples/veins: 1
Preparing for running configuration General, run #0...
Assigned runID=General-0-20190308-18:16:24-23603
Setting up network "RSUExampleScenario"...
Initializing...
Hello, world!
Running simulation...
(Note the Hello, world!
output during initialization of the simulation.)
Building on Windows will likely mean copying lines from the RInside examples Makefile.win file instead.
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Sure! updated the question.
– user8561039
Mar 13 at 0:44
add a comment |
I gave integrating RInside and Veins (version 5 alpha 1) a quick try and can report success.
I installed RInside by running R and executing install.packages('RInside')
.
I then amended the following lines (mostly copied from the RInside examples GNUMakefile) to the Veins src/makefrag
file:
# determine flags for RInside
R_HOME := $(shell R RHOME)
RCPPFLAGS := $(shell $(R_HOME)/bin/R CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R CMD config LAPACK_LIBS)
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
# feed to opp_makemake
DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
After that, I could use R inside Veins. I tried this by copying code from RInside rinside_sample0.cpp
to Veins BaseConnectionManager.cc
as follows:
diff --git a/src/veins/base/connectionManager/BaseConnectionManager.cc b/src/veins/base/connectionManager/BaseConnectionManager.cc
index 879e90d244..8e9eba10e8 100644
--- a/src/veins/base/connectionManager/BaseConnectionManager.cc
+++ b/src/veins/base/connectionManager/BaseConnectionManager.cc
@@ -1,3 +1,5 @@
+#include <RInside.h>
+
#include "veins/base/connectionManager/BaseConnectionManager.h"
#include "veins/base/connectionManager/NicEntryDebug.h"
@@ -42,6 +44,12 @@ void BaseConnectionManager::initialize(int stage)
// BaseModule::initialize(stage);
if (stage == 0) {
+
+ // Hello R!
+ RInside R;
+ R["txt"] = "Hello, world!n";
+ R.parseEvalQ("cat(txt)");
+
drawMIR = hasPar("drawMaxIntfDist") ? par("drawMaxIntfDist").boolValue() : false;
EV_TRACE << "initializing BaseConnectionManagern";
Compiling Veins (./configure
followed by make
) and running the tutorial example (cd examples/veins
followed by ./run -u Cmdenv
) produced the desired output:
OMNeT++ Discrete Event Simulation (C) 1992-2018 Andras Varga, OpenSim Ltd.
Version: 5.4.1, build: 180629-5e28390, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer
Setting up Cmdenv...
Loading NED files from ../../src/veins: 41
Loading NED files from .: 1
Loading NED files from /Users/sommer/src/veins/examples/veins: 1
Preparing for running configuration General, run #0...
Assigned runID=General-0-20190308-18:16:24-23603
Setting up network "RSUExampleScenario"...
Initializing...
Hello, world!
Running simulation...
(Note the Hello, world!
output during initialization of the simulation.)
Building on Windows will likely mean copying lines from the RInside examples Makefile.win file instead.
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Sure! updated the question.
– user8561039
Mar 13 at 0:44
add a comment |
I gave integrating RInside and Veins (version 5 alpha 1) a quick try and can report success.
I installed RInside by running R and executing install.packages('RInside')
.
I then amended the following lines (mostly copied from the RInside examples GNUMakefile) to the Veins src/makefrag
file:
# determine flags for RInside
R_HOME := $(shell R RHOME)
RCPPFLAGS := $(shell $(R_HOME)/bin/R CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R CMD config LAPACK_LIBS)
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
# feed to opp_makemake
DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
After that, I could use R inside Veins. I tried this by copying code from RInside rinside_sample0.cpp
to Veins BaseConnectionManager.cc
as follows:
diff --git a/src/veins/base/connectionManager/BaseConnectionManager.cc b/src/veins/base/connectionManager/BaseConnectionManager.cc
index 879e90d244..8e9eba10e8 100644
--- a/src/veins/base/connectionManager/BaseConnectionManager.cc
+++ b/src/veins/base/connectionManager/BaseConnectionManager.cc
@@ -1,3 +1,5 @@
+#include <RInside.h>
+
#include "veins/base/connectionManager/BaseConnectionManager.h"
#include "veins/base/connectionManager/NicEntryDebug.h"
@@ -42,6 +44,12 @@ void BaseConnectionManager::initialize(int stage)
// BaseModule::initialize(stage);
if (stage == 0) {
+
+ // Hello R!
+ RInside R;
+ R["txt"] = "Hello, world!n";
+ R.parseEvalQ("cat(txt)");
+
drawMIR = hasPar("drawMaxIntfDist") ? par("drawMaxIntfDist").boolValue() : false;
EV_TRACE << "initializing BaseConnectionManagern";
Compiling Veins (./configure
followed by make
) and running the tutorial example (cd examples/veins
followed by ./run -u Cmdenv
) produced the desired output:
OMNeT++ Discrete Event Simulation (C) 1992-2018 Andras Varga, OpenSim Ltd.
Version: 5.4.1, build: 180629-5e28390, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer
Setting up Cmdenv...
Loading NED files from ../../src/veins: 41
Loading NED files from .: 1
Loading NED files from /Users/sommer/src/veins/examples/veins: 1
Preparing for running configuration General, run #0...
Assigned runID=General-0-20190308-18:16:24-23603
Setting up network "RSUExampleScenario"...
Initializing...
Hello, world!
Running simulation...
(Note the Hello, world!
output during initialization of the simulation.)
Building on Windows will likely mean copying lines from the RInside examples Makefile.win file instead.
I gave integrating RInside and Veins (version 5 alpha 1) a quick try and can report success.
I installed RInside by running R and executing install.packages('RInside')
.
I then amended the following lines (mostly copied from the RInside examples GNUMakefile) to the Veins src/makefrag
file:
# determine flags for RInside
R_HOME := $(shell R RHOME)
RCPPFLAGS := $(shell $(R_HOME)/bin/R CMD config --cppflags)
RLDFLAGS := $(shell $(R_HOME)/bin/R CMD config --ldflags)
RBLAS := $(shell $(R_HOME)/bin/R CMD config BLAS_LIBS)
RLAPACK := $(shell $(R_HOME)/bin/R CMD config LAPACK_LIBS)
RCPPINCL := $(shell echo 'Rcpp:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RCPPLIBS := $(shell echo 'Rcpp:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDEINCL := $(shell echo 'RInside:::CxxFlags()' | $(R_HOME)/bin/R --vanilla --slave)
RINSIDELIBS := $(shell echo 'RInside:::LdFlags()' | $(R_HOME)/bin/R --vanilla --slave)
# feed to opp_makemake
DEFINES += $(RCPPFLAGS) $(RCPPINCL) $(RINSIDEINCL) $(shell $(R_HOME)/bin/R CMD config CPPFLAGS) $(shell $(R_HOME)/bin/R CMD config CXXFLAGS)
LIBS += $(RLDFLAGS) $(RRPATH) $(RBLAS) $(RLAPACK) $(RCPPLIBS) $(RINSIDELIBS)
After that, I could use R inside Veins. I tried this by copying code from RInside rinside_sample0.cpp
to Veins BaseConnectionManager.cc
as follows:
diff --git a/src/veins/base/connectionManager/BaseConnectionManager.cc b/src/veins/base/connectionManager/BaseConnectionManager.cc
index 879e90d244..8e9eba10e8 100644
--- a/src/veins/base/connectionManager/BaseConnectionManager.cc
+++ b/src/veins/base/connectionManager/BaseConnectionManager.cc
@@ -1,3 +1,5 @@
+#include <RInside.h>
+
#include "veins/base/connectionManager/BaseConnectionManager.h"
#include "veins/base/connectionManager/NicEntryDebug.h"
@@ -42,6 +44,12 @@ void BaseConnectionManager::initialize(int stage)
// BaseModule::initialize(stage);
if (stage == 0) {
+
+ // Hello R!
+ RInside R;
+ R["txt"] = "Hello, world!n";
+ R.parseEvalQ("cat(txt)");
+
drawMIR = hasPar("drawMaxIntfDist") ? par("drawMaxIntfDist").boolValue() : false;
EV_TRACE << "initializing BaseConnectionManagern";
Compiling Veins (./configure
followed by make
) and running the tutorial example (cd examples/veins
followed by ./run -u Cmdenv
) produced the desired output:
OMNeT++ Discrete Event Simulation (C) 1992-2018 Andras Varga, OpenSim Ltd.
Version: 5.4.1, build: 180629-5e28390, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer
Setting up Cmdenv...
Loading NED files from ../../src/veins: 41
Loading NED files from .: 1
Loading NED files from /Users/sommer/src/veins/examples/veins: 1
Preparing for running configuration General, run #0...
Assigned runID=General-0-20190308-18:16:24-23603
Setting up network "RSUExampleScenario"...
Initializing...
Hello, world!
Running simulation...
(Note the Hello, world!
output during initialization of the simulation.)
Building on Windows will likely mean copying lines from the RInside examples Makefile.win file instead.
edited Mar 11 at 6:28
answered Mar 8 at 17:17
Christoph SommerChristoph Sommer
4,80911232
4,80911232
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Sure! updated the question.
– user8561039
Mar 13 at 0:44
add a comment |
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Sure! updated the question.
– user8561039
Mar 13 at 0:44
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
Thanks a lot! I edited makefrag file and built the project, but ended up having "make[1]: /bin/R: Command not found". I ran 'R RHOME' command on the command line and got the path correctly as 'C:R-3.5.2'. Still could not figure out why..
– user8561039
Mar 11 at 5:18
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
My bad - I forgot to mention that I did this by copying from the RInside examples GNUMakefile (the file used for building the examples on macOS, Linux, etc) - not from its Makefile.win (the file used for building on Windows)
– Christoph Sommer
Mar 11 at 6:30
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
All good! I built RInside examples as Dirk has mentioned and it worked fine. Then as you did I copied the relevant content from Makefile.win to makefrag file in Veins and built. I am still getting "/bin/sh: R: command not found" and "make[1]: /bin/R: Command not found". I think the line "R_HOME := $(shell R RHOME | sed -e "s|\\|/|g")" doesn't pick up the path correctly. Any thoughts on this and how to correct it?
– user8561039
Mar 12 at 23:04
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Are you able to edit your question to amend it with what you have in your makefrag so far?
– Christoph Sommer
Mar 12 at 23:54
Sure! updated the question.
– user8561039
Mar 13 at 0:44
Sure! updated the question.
– user8561039
Mar 13 at 0:44
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55053980%2fconfigure-rinside-with-veins-and-omnet-on-windows%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
My recommendation is to start trying to build (some of) the supplied examples to validate your local toolchain. If that works, try 'porting' to Eclipse, CMake, ... At some point in the past the contributed CMakefiles worked but I don;t if a) they every worked on Windows or b) if they are current. I use the standard R tools...
– Dirk Eddelbuettel
Mar 7 at 22:44
1
OMNeT++ simulations are traditionally built via opp_makemake, which creates GNU Makefiles. An easy way to tweak these Makefiles to use custom include paths and libraries is the use of a makefrag file, which contains a fragment of code that will be inserted into the created Makefile. Try building Veins, check the created Makefile in src/, compare this with the makefrag file in src/ and try to take code from RInside's sample Makefiles, e.g., github.com/eddelbuettel/rinside/blob/6699d52/inst/examples/…
– Christoph Sommer
Mar 8 at 0:12
Thanks Dirk and Christoph! Really appreciate your suggestions. I will post my findings around these.
– user8561039
Mar 8 at 6:20