yade-pkg team mailing list archive

[Bruno Chareyre <bruno.chareyre@xxxxxxxxxxx>]

Ah, sorry, I didn't get the fact you really tried kdevelop.
Let's sort things :

Things that work with kdev4 automatically, if it doesn't work for you we 
should find why :
- go to definitions/declarations
- run compilation (though the debug/release switch would be easier using 
cmake, for now you have to change manually an argument in the build options)
- every aspects of debugging (stepping, breakpoints, conditional 
breakpoints, variable tracking,...) provided you start yade from 
terminal and link.
- auto-parsing at startup for code navigation.

Things that work but may not be commitable :
- launching yade-release from kdevelop (easy to configure on users side, 
but not sure the configuration can be commited to trunk)

Things that could work maybe :
- launching yade in debug mode from kdevelop (I think I tried and it 
didn't work, but it could be tried again)
- auto-follow code style (note it would need to choose a code style 
first). I suspect code style is stored in something like 
~/.kdev/session/yade, not in the project options directly, so not 
commitable, but I could double-check that.

Doesn't work yet but replaced by something else :
- ctags integration is in the TODO list for kdev4. I miss kdev3 for this 
reason (ctags was fully integrated), but actually there is a 
functionally equivalent feature and parsing is done automatically 
(Ctrl+Alt+Q+name for class "name", Ctrl+Alt+M if its a function, 
Ctrl+Alt+O for file, Ctrl+Alt+Q for all at once).

Things that will not work :
- bzr support (there is only svn support)

For debugging, I don't think starting from terminal and linking the app 
is a problem : you need a terminal anyway in order to type the command 
you debug, or if you debug a script you need to type its name somewhere 
(script name can be in kdevelop options of course, but then it is a user 
setting that can't apply for all).

> > exactly easy on windows. Mingw is also ugly and breaks windows desktop
> > features.
> >      
> Can you elaborate in what it is ugly, what exactly it breaks or give a
> link to that information?
>    
I wonder if I didn't mix mingw and cygwin actually. I don't remember why 
they are linked in my mind now. Maybe I tried both independtly : mingw 
compiling for windows and compiling from inside cygwin. I'll check if I 
can find the history of these trials. For now lets say my remarks 
applies only for cygwin.

Cheers.

Bruno

--
_______________
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : +33 4 56 52 86 21
Fax : +33 4 76 82 70 43
________________