Comments on: Eclipse for C programming http://micke.hallendal.net/blog/eclipse-for-c-programming/ Personal blog of Mikael Hallendal Wed, 07 Jan 2009 00:45:06 +0000 http://wordpress.org/?v=2.5.1 By: Mikael Hallendal http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-913 Mikael Hallendal Sat, 04 Aug 2007 10:07:41 +0000 http://micke.hallendal.net/blog/?p=249#comment-913 Thanks a lot for the update Jeff, looking forward to try it out. Thanks a lot for the update Jeff, looking forward to try it out.

]]> By: Jeff Johnston http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-912 Jeff Johnston Fri, 03 Aug 2007 15:55:24 +0000 http://micke.hallendal.net/blog/?p=249#comment-912 Regarding Andrew's comment above, I just wanted to verify that the Autotools for CDT 4.0.0 is now available on the Sourceware Eclipse update site: <a href="http://sourceware.org/eclipse/update" rel="nofollow">http://sourceware.org/eclipse/update</a> You can find details on how to install it from Eclipse at: <a href="http://sourceware.org/eclipse/autotools" rel="nofollow">http://sourceware.org/eclipse/autotools</a> I should note that there is a bug in the CDT code such that the resultant binaries of your Makefile do not appear in the Binaries folder. This minor annoyance is being worked on for 4.0.1. The binaries do exist, but the CDT doesn't look in the folder you supply in your configure. You can manually configure the Run dialog to run these binaries, but if they were in the Binaries folder, all you would have to do is to right click and choose "Run as a C/C++ executable". Regarding Andrew’s comment above, I just wanted to verify that the Autotools for CDT 4.0.0 is now available on the Sourceware Eclipse update site:

http://sourceware.org/eclipse/update

You can find details on how to install it from Eclipse at: http://sourceware.org/eclipse/autotools

I should note that there is a bug in the CDT code such that the resultant binaries of your Makefile do not appear in the Binaries folder. This minor annoyance is being worked on for 4.0.1. The binaries do exist, but the CDT doesn’t look in the folder you supply in your configure. You can manually configure the Run dialog to run these binaries, but if they were in the Binaries folder, all you would have to do is to right click and choose “Run as a C/C++ executable”.

]]> By: hynek http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-911 hynek Thu, 26 Jul 2007 20:01:42 +0000 http://micke.hallendal.net/blog/?p=249#comment-911 I still strongly prefer SlickEdit. It's not for free but it blows away anything I've seen/used before. I still strongly prefer SlickEdit. It’s not for free but it blows away anything I’ve seen/used before.

]]> By: Andrew Overholt http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-910 Andrew Overholt Thu, 26 Jul 2007 18:11:32 +0000 http://micke.hallendal.net/blog/?p=249#comment-910 Colin: I was discussing the whole project thing with Tom Tromey the other day. He was noting how it's odd that emacs hasn't grown the notion of projects yet. It really makes it handy for things like version control and bug tracking since you can just tack that onto the project metadata. Unfortunately, it makes it so that everything has to be in a project. I like to think of this enforcing things being in version control, but I can see how it's a pain to hack on a random file. The JDT supports pasting a random .java file into the workspace and creating a project for it on the fly. See about half-way down here: <a href="http://archive.eclipse.org/eclipse/downloads/drops/S-3.3M1-200608101230/eclipse-news-M1.html" rel="nofollow">http://archive.eclipse.org/eclipse/downloads/drops/S-3.3M1-200608101230/eclipse-news-M1.html</a> Colin: I was discussing the whole project thing with Tom Tromey the other day. He was noting how it’s odd that emacs hasn’t grown the notion of projects yet. It really makes it handy for things like version control and bug tracking since you can just tack that onto the project metadata. Unfortunately, it makes it so that everything has to be in a project. I like to think of this enforcing things being in version control, but I can see how it’s a pain to hack on a random file. The JDT supports pasting a random .java file into the workspace and creating a project for it on the fly. See about half-way down here:

http://archive.eclipse.org/eclipse/downloads/drops/S-3.3M1-200608101230/eclipse-news-M1.html

]]> By: Colin Walters http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-909 Colin Walters Thu, 26 Jul 2007 16:46:01 +0000 http://micke.hallendal.net/blog/?p=249#comment-909 Eclipse is pretty good now. I've found I like PyDev for doing Python work. By far the biggest issue I've found is that it's really hard to just open random projects and work on them. Say I want to work on jhbuild all of a sudden; I have to go through the whole Create Project thing...ick. Eclipse is pretty good now. I’ve found I like PyDev for doing Python work.

By far the biggest issue I’ve found is that it’s really hard to just open random projects and work on them. Say I want to work on jhbuild all of a sudden; I have to go through the whole Create Project thing…ick.

]]> By: Andrew Overholt http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-908 Andrew Overholt Thu, 26 Jul 2007 16:34:44 +0000 http://micke.hallendal.net/blog/?p=249#comment-908 Sweet. Ben Konrath has always talked about GObject integration but we've barely kept our heads about water over the past few years. I *think* the upstream CDT guys want to take in the autotools work for their next release. Either way, it's pretty nice stuff and it's improving all the time: <a href="http://overholt.ca/wp/?p=82" rel="nofollow">http://overholt.ca/wp/?p=82</a> Jeff's always looking for ways to test it. He's pretty much got everything working for projects like gdb (he used to work on it) but things like GNOME or Gtk projects he doesn't really know how to test them. If you could provide him with some guidance on how he can ensure things work, that would totally rock. He's jjohnstn@redhat.com but he's off until Monday so if he doesn't reply it's not 'cause he's not interested :) Sweet. Ben Konrath has always talked about GObject integration but we’ve barely kept our heads about water over the past few years. I *think* the upstream CDT guys want to take in the autotools work for their next release. Either way, it’s pretty nice stuff and it’s improving all the time:

http://overholt.ca/wp/?p=82

Jeff’s always looking for ways to test it. He’s pretty much got everything working for projects like gdb (he used to work on it) but things like GNOME or Gtk projects he doesn’t really know how to test them. If you could provide him with some guidance on how he can ensure things work, that would totally rock. He’s jjohnstn@redhat.com but he’s off until Monday so if he doesn’t reply it’s not ’cause he’s not interested :)

]]> By: Mikael Hallendal http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-907 Mikael Hallendal Thu, 26 Jul 2007 15:14:47 +0000 http://micke.hallendal.net/blog/?p=249#comment-907 Andrew, ah thanks for the clarification. Very nice to see that there is work going on to improve the experience when working with autotools projects. I'm hoping to spend some time to look into some GObject-integration of sorts. If nothing else a GObject-generator. Andrew, ah thanks for the clarification. Very nice to see that there is work going on to improve the experience when working with autotools projects.

I’m hoping to spend some time to look into some GObject-integration of sorts. If nothing else a GObject-generator.

]]> By: Andrew Overholt http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-906 Andrew Overholt Thu, 26 Jul 2007 15:06:00 +0000 http://micke.hallendal.net/blog/?p=249#comment-906 Technically you weren't using gcj, but were just using gij, the interpreter. That is, unless Ubuntu has SDK 3.3 and CDT 4.0 .debs already but I don't think they do. Using just the interpreter is not feasible as you discovered :). gcj is the ahead-of-time compiler (gcc frontend) that creates the .sos that are used instead of just in vanilla bytecode interpreter. I'm glad you found things useful. You should try out Jeff Johnston's work on autotools integration: <a href="http://sourceware.org/eclipse/autotools" rel="nofollow">http://sourceware.org/eclipse/autotools</a> I think it should work against 4.0 clean but I don't think he has an update site yet that you can use with the upstream download. I'll get him to do that. Technically you weren’t using gcj, but were just using gij, the interpreter. That is, unless Ubuntu has SDK 3.3 and CDT 4.0 .debs already but I don’t think they do. Using just the interpreter is not feasible as you discovered :). gcj is the ahead-of-time compiler (gcc frontend) that creates the .sos that are used instead of just in vanilla bytecode interpreter.

I’m glad you found things useful. You should try out Jeff Johnston’s work on autotools integration: http://sourceware.org/eclipse/autotools
I think it should work against 4.0 clean but I don’t think he has an update site yet that you can use with the upstream download. I’ll get him to do that.

]]> By: Germán Poó-Caamaño http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-905 Germán Poó-Caamaño Thu, 26 Jul 2007 13:41:30 +0000 http://micke.hallendal.net/blog/?p=249#comment-905 For powerful indexing and old school programmers, you still have cscope (http://cscope.sourceforge.net/) and a nice interface, from our neighbors, kscope (http://kscope.sourceforge.net/). If you are interested in future work that can be done for a maintainer of code, could be useful give a read to the paper "An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks " (http://www.cs.cmu.edu/~ajko/papers/Ko2006SeekRelateCollect.pdf). The authors used Eclipse as a case of study and they gave recommendations about future improvements. For powerful indexing and old school programmers, you still have cscope (http://cscope.sourceforge.net/) and a nice interface, from our neighbors, kscope (http://kscope.sourceforge.net/).

If you are interested in future work that can be done for a maintainer of code, could be useful give a read to the paper “An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks ” (http://www.cs.cmu.edu/~ajko/papers/Ko2006SeekRelateCollect.pdf).

The authors used Eclipse as a case of study and they gave recommendations about future improvements.

]]> By: Mikael Hallendal http://micke.hallendal.net/blog/eclipse-for-c-programming/#comment-904 Mikael Hallendal Thu, 26 Jul 2007 13:13:00 +0000 http://micke.hallendal.net/blog/?p=249#comment-904 Well observed iain and thanks for taking the time to view the film. Well observed iain and thanks for taking the time to view the film.

]]>