omnetpp 4.2.1 Indexer not working
117 views
Skip to first unread message
Bastian H.
Jan 27, 2012, 6:35:44 AM1/27/12
to omnetpp
Hello everyone,
I am trying to setup a working omnetpp installation for 2 weeks now,
but without success. The problem is the indexer which doesn't work.
The indexer doesn't recognize references to the c++ library (or some
other functions).
I tried deleting, adding/importing projects, but even with a complete
fresh ubuntu 11.10 install and omnetpp build from scratch, everything
works - except the indexer. Adding various include files to the
include paths in the properties section works for some references, but
not for all. I used the aloha test project and the default workspace
settings.
I hope you have a solution, because this behavior occurred on two
different computers and is driving me crazy :/
Thanks!
I am trying to setup a working omnetpp installation for 2 weeks now,
but without success. The problem is the indexer which doesn't work.
The indexer doesn't recognize references to the c++ library (or some
other functions).
I tried deleting, adding/importing projects, but even with a complete
fresh ubuntu 11.10 install and omnetpp build from scratch, everything
works - except the indexer. Adding various include files to the
include paths in the properties section works for some references, but
not for all. I used the aloha test project and the default workspace
settings.
I hope you have a solution, because this behavior occurred on two
different computers and is driving me crazy :/
Thanks!
Rudolf Hornig
Jan 27, 2012, 6:47:32 AM1/27/12
to omn...@googlegroups.com
Could you please send us the exact steps to reproduce the issue.
(starting from a fresh omnet isntallation).
i.e. what you have added to the aloha project and what you excpect to happen and what is happening in reality.
RUdolf
--
Sent from the OMNeT++ mailing list. To configure your membership,
visit http://groups.google.com/group/omnetpp
Bastian H.
Jan 27, 2012, 6:54:13 AM1/27/12
to omnetpp
Hello Rudolf,
no problem:
1) Install ubuntu
2) DL omnetpp4.2.1
3) Install all packages according to omnetpp installation guide
4) Build omnetpp
5) Run omnetpp for first time
6) Select the default workspace
7) Open project aloha
8) Build project
9) Run project (--> works as expected)
10) Open host.cc
11) Notice the indexer showing multiple errors (--> I expect no errors
as the programm builds and launches correctly)
I hope this helps!
On Jan 27, 12:47 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> Could you please send us the exact steps to reproduce the issue.
> (starting from a fresh omnet isntallation).
>
> i.e. what you have added to the aloha project and what you excpect to
> happen and what is happening in reality.
>
> RUdolf
>
no problem:
1) Install ubuntu
2) DL omnetpp4.2.1
3) Install all packages according to omnetpp installation guide
4) Build omnetpp
5) Run omnetpp for first time
6) Select the default workspace
7) Open project aloha
8) Build project
9) Run project (--> works as expected)
10) Open host.cc
11) Notice the indexer showing multiple errors (--> I expect no errors
as the programm builds and launches correctly)
I hope this helps!
On Jan 27, 12:47 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> Could you please send us the exact steps to reproduce the issue.
> (starting from a fresh omnet isntallation).
>
> i.e. what you have added to the aloha project and what you excpect to
> happen and what is happening in reality.
>
> RUdolf
>
Rudolf Hornig
Jan 27, 2012, 8:29:53 AM1/27/12
to omn...@googlegroups.com
I'm unable to reproduce this. For me everything is error free.
Could you please write down (or make a screenshot) of the problems view and also attach the .log file from the <workspace>/.metadata
You can send it directly to me instead of the mailing list.
Rudolf
Bastian H.
Jan 27, 2012, 8:36:15 AM1/27/12
to omnetpp
If you believe it or not - I just found the solution 30 seconds ago:
My .bashrc looked like this:
export PATH=${OMNETDIR}/lib:$PATH
And this caused all my problems!
Actually is has to look like this:
export PATH=$PATH:${OMNETDIR}/lib
I assume the reason is the folder gcc contained in omnetpp/lib! If
this folder gets searched first by gcc, gcc messes everything up.
If gcc finds it normal include folders first, and the omnetpp/lib/gcc
folder last, everything works.
In the InstallGuide.pdf the order is correct - but I used a custom
install guide from my university which has this little differences
that causes all problems...
Sorry for any inconvenience I might have caused !
On Jan 27, 2:29 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> I'm unable to reproduce this. For me everything is error free.
>
> Could you please write down (or make a screenshot) of the problems view and
> also attach the .log file from the <workspace>/.metadata
>
> You can send it directly to me instead of the mailing list.
> Rudolf
>
My .bashrc looked like this:
export PATH=${OMNETDIR}/lib:$PATH
And this caused all my problems!
Actually is has to look like this:
export PATH=$PATH:${OMNETDIR}/lib
I assume the reason is the folder gcc contained in omnetpp/lib! If
this folder gets searched first by gcc, gcc messes everything up.
If gcc finds it normal include folders first, and the omnetpp/lib/gcc
folder last, everything works.
In the InstallGuide.pdf the order is correct - but I used a custom
install guide from my university which has this little differences
that causes all problems...
Sorry for any inconvenience I might have caused !
On Jan 27, 2:29 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> I'm unable to reproduce this. For me everything is error free.
>
> Could you please write down (or make a screenshot) of the problems view and
> also attach the .log file from the <workspace>/.metadata
>
> You can send it directly to me instead of the mailing list.
> Rudolf
>
Rudolf Hornig
Jan 27, 2012, 8:52:48 AM1/27/12
to omn...@googlegroups.com
No problem, but the below line should not affect the given behavior.
First, the line
export PATH=$PATH:${OMNETDIR}/lib
is completely unnecessary. There is NO reason why the PATH should contain the lib directory. You do not need that. You need ${OMNETDIR}/bin there. Also you must check whether the PATH already contains a reference to an other omnetpp (possibly older) installation. That should be also removed if present.
The indexer is NOT using gcc and completely implemented in java, so the path settings should not affect it either.
Generally, I think the problem was somewhere else. If you ran into it again, please try to nail down and contect us...
Rudolf
Bastian H.
Jan 27, 2012, 9:48:08 AM1/27/12
to omnetpp
Just swapping the path order solved the problem (reproducible) on 2
computers.
Of course I have the bin folder in my path, too.
There are no other omnet installations on my path (as I installed
ubuntu in a VM from scratch).
I really thing the indexer problem was caused by this line in
my .bashrc. But perhaps we'll never know for sure ;)
On Jan 27, 2:52 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> No problem, but the below line should not affect the given behavior.
>
> First, the line
> export PATH=$PATH:${OMNETDIR}/lib
>
> is completely unnecessary. There is NO reason why the PATH should contain
> the lib directory. You do not need that. You need ${OMNETDIR}/*bin* there.
computers.
Of course I have the bin folder in my path, too.
There are no other omnet installations on my path (as I installed
ubuntu in a VM from scratch).
I really thing the indexer problem was caused by this line in
my .bashrc. But perhaps we'll never know for sure ;)
On Jan 27, 2:52 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> No problem, but the below line should not affect the given behavior.
>
> First, the line
> export PATH=$PATH:${OMNETDIR}/lib
>
> is completely unnecessary. There is NO reason why the PATH should contain
> Also you must check whether the PATH already contains a reference to an
> other omnetpp (possibly older) installation. That should be also removed if
> present.
>
> The indexer is NOT using gcc and completely implemented in java, so the
> path settings should not affect it either.
>
> Generally, I think the problem was somewhere else. If you ran into it
> again, please try to nail down and contect us...
>
> Rudolf
>
> other omnetpp (possibly older) installation. That should be also removed if
> present.
>
> The indexer is NOT using gcc and completely implemented in java, so the
> path settings should not affect it either.
>
> Generally, I think the problem was somewhere else. If you ran into it
> again, please try to nail down and contect us...
>
> Rudolf
>
Reply all
Reply to author
Forward
0 new messages