I've a quite big c++ project (not managed by eclcipse before), and i
used eclim's ProjectCreate on it with "-n c++" (the source files are
in two folder, like: "src1/moduleX/*", "src2/moduleY/* ....). The
projecet creation seemed to be ok, but after than i run
CProjectConfigs and i've got the following error (trunk is the name of
my project):
davidk@davidk-laptop:~/remote/trunk$ /usr/lib/eclipse/eclim -command
c_project_configs -p "trunk"
java.lang.NullPointerException
at
org.eclim.plugin.cdt.command.project.ConfigurationsCommand.execute(ConfigurationsCommand.java:
72)
at org.eclim.command.Main.main(Main.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
at java.lang.reflect.Method.invoke(Method.java:616)
at com.martiansoftware.nailgun.NGSession.run(NGSession.java:
334)
Can anyone help on this? or is there some workaround?
Best regards, David
I'm not sure off hand what would cause this, but of all the languages
that eclim supports, currently c/c++ project creation is the one that
I'm least confident in. While it works for all the cases I've tried,
the cdt api for initializing a new project is far from straight
forward. I'll see if I can reproduce this particular issue, but in
the meantime I'd suggest the following workaround (if you are using
eclimd inside of the eclipse gui then you can skip steps 2, 3, and 5):
1. delete the project (this will only delete the eclipse artifacts,
not any of your files): :ProjectDelete trunk
2. stop eclimd
3. start the eclipse gui
4. create your project from the gui
5. close the eclipse gui and then start eclimd
Using those steps should ensure that your project is setup properly.
Once that is done, then all the c/c++ commands provided by eclim
should work normally.
--
eric
Glad to hear that you got it fixed, and that it wasn't eclim's fault
;).
I've been increasingly disappointed with ubuntu's (debians?) eclipse
packages. I think the vast majority of issues reported are from users
using apt-get installed eclipse :( (though it could just be that the
majority of users are on ubuntu).
--
eric