changed oF/addons to a C project for eclipse

[fx-lange]

addons is still no C project for eclipse. this way it isn't possible to rebuild the index or to use code completion, call hierarchy or symbol following in its full capacity.
(for example try to jump from ofxSlider.h to ofxBaseGui via F3 in line 7)

I always import from "existing code as makefile project" instead of "existing projects ..." when it comes to oF/addons. I'm using the Linux GCC Toolchain for the indexer.

for me it works fine but I have to rebuild the indexer from time to time.

[bilderbuchi]

that sounds good. that always annoyed me, but I never kenw how to fix it.
what about the libs/.project project, does that have to be converted to a .cproject, too?

pinging @arturoc

[fx-lange]

I'm not sure right now - never stumbled over this. perhaps I never digged that deep and because libs/openFrameworks is itself a C project.

for example I find AbstractPriorityDelegate in the resources (Strg + Shift + O) but can't jump to it from ofDelegate.h.

[arturoc]

i've been lately just importing the addons i use as linked folders in the projects, it's a little bit more work but it works well. not sure about the libs project, since OF is inside libs it can be problematic but haven't really tried

[bilderbuchi]

@fx-lange @arturoc can you build without issue with this new addons project? when I build the openframeworks project in eclipse, I get an error/problem report about the addons project: make: *** No rule to make targetall'. Stop.` (which seems logical, as you can't "build" the addons project"). how did you solve this?

[fx-lange]

@bilderbuchi, sorry for the late reply. For me - I just ignored the error. There is this run anyway dialogue - and I checked it as default. Compared to other eclipse+oF problems before this was just a minor issue for me.

One option would be to create a "do nothing" makefile?

[bilderbuchi]

Ah, a somewhat dirty workaround, but I'll look for this run anyway thing. I'm not sure if having a no-op makefile would be a good approach. @arturoc ?

[fx-lange]

Yes it is, I tried a Makefile like this

all:
Release:
Debug:

and get make: Nothing to be done for 'all'. which is just a notice/warning. Another option would be the make option -v. If we add make -v to the Build command under C/C++ Build settings - we get a short print out about make but don't need extra files. The modification would be saved in the addons/.cproject. Still "hacky" but only visible for Eclipse users.

[bilderbuchi]

@fx-lange I just now realized this, but please don't force-add files (as you must have done for addons/.cproject). If git ignores a file, either don't add the file (because it's not a good idea to), or adjust/update the .gitignore pattern so that the file is not being ignored (or ask for help with this).

[fx-lange]

argh, you are right - sorry for that. does this cause any trouble? should I update the .gitignore accordingly?

[bilderbuchi]

it's not a big deal, I just wanted to flag this for you in case you were unaware. I have already corrected the gitignore pattern