KDevelop4 and gdb version

On Wed, Jan 24, 2007 at 06:05:57PM +0300, Vladimir Prus
wrote:
> On Wednesday 24 January 2007 17:57, Matt Rogers wrote:
> > On Wed, Jan 24, 2007 at 01:42:52PM +0300, Vladimir
Prus wrote:
> > > 
> > > Sometime soon, I plan to start working on
debugger support in KDevelop4. 
> > > 
> > > I plan to require, until the first public
KDevelop 4 release, that CVS version of gdb
> > > is used. The reason is that making KDevelop
have alternative code paths
> > > for each feature that gdb adds in CVS is
going to be major pain.
> > > 
> > > I indend to add "feature list"
feature to gdb, so that KDevelop can check for 
> > > features it needs and reliably inform the
user that his gdb version is too old.
> > > At the same time, I'll use all new features I
can, and running KDevelop4 with
> > > last released version of gdb is likely to be
either very inconvenient or 
> > > downright impossible.
> > > 
> > > I hope that the time till the next gdb
release (~ 4 month) and the time till
> > > KDevelop 4 release is sufficient to add
everything I need. If anybody has some
> > > concerns or suggestions about this, speak
out!
> > > 
> > > - Volodya
> > > 
> > 
> > How easy is it to build gdb from cvs?
> 
> On stock linux system, building x86 gdb is
"./configure && make". I think
> expat is the only remotely non-standard dependency, and
it's available 
> everywhere.
> 
> - Volodya
> 

Ok, that's easy enough. I am not against this requirement
personally,
but I want to see what others have to say.

Do you know of anything special that is needed to build cvs
versions of
gdb on Mac OS X? Several of us have shiny new macs to use on
KDE 4. 
--
Matt

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday 24 January 2007 11:52, Matt Rogers wrote:
> On Wed, Jan 24, 2007 at 06:05:57PM +0300, Vladimir Prus
wrote:
> > On Wednesday 24 January 2007 17:57, Matt Rogers
wrote:
> > > On Wed, Jan 24, 2007 at 01:42:52PM +0300,
Vladimir Prus wrote:
> > > > Sometime soon, I plan to start working
on debugger support in
> > > > KDevelop4.
> > > >
> > > > I plan to require, until the first
public KDevelop 4 release, that
> > > > CVS version of gdb is used. The reason
is that making KDevelop have
> > > > alternative code paths for each feature
that gdb adds in CVS is going
> > > > to be major pain.
> > > >
> > > > I indend to add "feature list"
feature to gdb, so that KDevelop can
> > > > check for features it needs and reliably
inform the user that his gdb
> > > > version is too old. At the same time,
I'll use all new features I
> > > > can, and running KDevelop4 with last
released version of gdb is
> > > > likely to be either very inconvenient or
downright impossible.
> > > >
> > > > I hope that the time till the next gdb
release (~ 4 month) and the
> > > > time till KDevelop 4 release is
sufficient to add everything I need.
> > > > If anybody has some concerns or
suggestions about this, speak out!
> > > >
> > > > - Volodya
> > >
> > > How easy is it to build gdb from cvs?
> >
> > On stock linux system, building x86 gdb is
"./configure && make". I think
> > expat is the only remotely non-standard
dependency, and it's available
> > everywhere.
> >
> > - Volodya
>
> Ok, that's easy enough. I am not against this
requirement personally,
> but I want to see what others have to say.
>
> Do you know of anything special that is needed to build
cvs versions of
> gdb on Mac OS X? Several of us have shiny new macs to
use on KDE 4. 
> --
> Matt
good for me.
Mathieu
-- 
Excess on occasion is exhilarating.  It prevents moderation
from
acquiring the deadening effect of a habit.
		-- W. Somerset Maugham

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday, 24. January 2007 17:52, Matt Rogers wrote:
> Ok, that's easy enough. I am not against this
requirement personally,
> but I want to see what others have to say.

I have enough CVS/SVN versions on my hd, one more won't keep
me
from building KDevelop.

Just curious how KDE's "maintainer" people outside
of KDevelop will react
to the necessity of having an external CVS dependency. After
all, the 
convenience of getting those kdelibs porting things done by
Laurent,
Dirk & Co. is not negligible.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday 24 January 2007 21:53, Jakob Petsovits wrote:
> Just curious how KDE's "maintainer" people
outside of KDevelop will react
> to the necessity of having an external CVS dependency.
After all, the
> convenience of getting those kdelibs porting things
done by Laurent,
> Dirk & Co. is not negligible.

Well, I hope they won't care because the dependency will be
run-time only.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday, 24. January 2007 21:01, Alexander Dymo wrote:
> Well, I hope they won't care because the dependency
will be run-time only.

I really should post less and think more.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday, 24. January 2007 21:01, Alexander Dymo wrote:
> Well, I hope they won't care because the dependency
will be run-time only.

I really should post less and think more.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel