Dear Juan,
Yes, the value of CastaliaBin is : /home/utar/Desktop/Castalia/CastaliaBin
Yes, I do agree very much with you that it may have mix entry point because there is no way it can execute Fuzzylite with CastaliaBin path. For the pathToCastaliaBin, ‘-f’, ‘omnetpp.tmp’, ‘-x’, ‘General’ with subproces.check_output, and I have verified that -f and -x options are actually used for Castalia.
By the way, I tried to compare the output of $PATH between the one excludes Fuzzylite and the one include Fuzzylite after executing Castalia. The outputs are same and are shown as follows:
/usr/local/cuda-8.0/bin:/usr/local/cuda-8.0/bin:/home/utar/bin:/home/utar/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/utar/Desktop/HY/fuzzylite-6.0/fuzzylite/:/home/utar/omnetpp-4.6/bin:/home/utar/Desktop/Castalia/bin
Does it mean the path for executing the bin file remains unchanged ? If so, how would it run into Fuzzylite ?
Regarding the rebuild, if I remove the main.cpp, it would fail to build with the build.sh under fuzzylite folder. So what should I do ?