17:10:14 #startmeeting 17:10:14 Meeting started Sat Dec 5 17:10:14 2009 UTC. The chair is mchua. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:10:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:10:24 mchua, cheers 17:10:24 Andrew Overholt is presenting Eclipse. 17:10:29 #topic Agenda 17:10:33 1. tools for packagers 17:10:39 2. tools for c/c++ developers 17:10:47 3. ...argh, the slide moved on and I forgot - will get to this in turn 17:10:51 #topic tools for packagers 17:11:06 Andrew is showing how to edit a specfile in eclipse. 17:11:49 Eclipse, when you open a spec file in it, has a window called Package Explorer that can show you the source files and such inside the package you're trying to make. 17:12:05 It also has an outline view so you can easily get to the various sections of a specfile you're trying to edit. 17:12:13 (%prep, %build, %install, etc) 17:12:30 There's also a history tab that shows you the changelog of a specfile. 17:13:34 You can also compare different versions of the ssame specfile; it'll show you a color-coded diff. 17:13:43 There is a diffk-like view being actively developed now. 17:14:27 Andrew is displaying the basic specfile editor - it has syntax coloring, basic text editing stuff. 17:14:42 If you hover over the variables, it will show you the values the macros have been defined as. 17:15:21 (for instance, hovering over the "%{name}" part of a "Requires: %{name}--rcp " line will give you the value of %{name} 17:15:24 ) 17:15:39 Also when you're typing out a Requires: line - there's autocomplete. 17:15:56 It will show you a list of packages that list the things you've started typing. 17:16:23 You can import srpms and interact with repositories from within Eclipse. 17:17:17 For instance, you can see the outstanding bugs filed against a package. 17:18:10 You can see the comments on a bug, and comment directly on a bug within Eclipse. 17:20:43 Eclipse keeps track of everything you do for a bug - what files you opened, what comments you entered, etc. 17:20:57 it keeps track of relationships between the stuff you do on a bug. 17:22:03 Hey - can someone take over transcribing? I have to go welcome our lunch caterer to FUDCon. 17:22:35 jds2001: ^^ 17:22:48 (or really anyone, I should be back in <15 I think) 17:52:04 (sorry about the lag folks, I had to go take care of our lunch) 17:52:16 Jeff is now presenting about... C/C++ tools 17:52:25 (still in Eclipse) 17:56:34 #topic integration of systemtap and eclipse 17:56:43 Roland and Charley presenting 17:57:07 originally making a tool for systemtap developers, but turned it into something you can use to profile any program. 17:57:32 (file) > profile as > (MENU!) 17:57:40 options in the menu are things like probe/profile 17:58:02 They pulled up a very small C++ program as an example. 17:58:10 And have just profiled it; there is a graph on the screen 17:58:36 it looks like a finite state machine, with a line between two functions if one calls the other during execution. 17:58:53 next to each block labeled with a function name is the percentage of the calls that function got. 17:59:02 for instance if function main() called function foo() once and bar() twice 17:59:23 it would be foo-33%<---main-100%--->bar-66& 17:59:26 er, 66% 17:59:45 (is it function calls or memory? I'm having a hard time typing and listening simultaneously.) 18:00:03 Can show it in various graphical output modes - bar graphs, etc. 18:00:08 it's basically a general purpose code profile 18:00:10 profiler 18:00:14 (for C++?) 18:03:41 Presentation ended - probably worth asking presenter to post slides 18:03:45 #endmeeting