On Thursday 22 April 2004 03:53 pm, Michael Nottebrock wrote:
> On Thursday 22 April 2004 21:24, Jim Durham wrote:
> > On Thursday 22 April 2004 02:41 pm, Michael Nottebrock wrote:
> > > On Thursday 22 April 2004 20:28, Jim Durham wrote:
> > > > What's the correct way to do this?
> > >
> > > Don't hack the port Makefiles, just make -DWANT_KDE_DEBUG (or define
> > > WANT_KDE_DEBUG in /etc/make.conf).
> >
> > Thanks very much...
> >
> > Something else I should have asked... when you type 'make clean' then
> > 'make' it unpacks the sources again, overwriting any changes .
>
> Actually, the 'make clean' deletes the work/ subdirectory, so if you do
> that, 'make' has to extract the distfile again.
>
> > I have been
> > letting it get to the configure script conclusion, then control C 'ing it
> > and changing the source. What is the proper way to do this?
>
> I'm not sure what you're asking. If you don't want to break with ctrl-c, do
> 'make configure' - this will stop after the configure step and lets you
> change things, then go on with 'make'. If you want your changes preserved
> and automatically applied before each build, turn them into a
> patch-<somename> file in a files subdirectory in the port directory (look
> at other patches in other ports for examples).
There appears to be a problem with the debug code. After compiling the same
code with the _DWITH_KDE_DEBUG argument, I can't even get kdm to run. It
crashes immediately and cycles up and down. Same code without the argument
works.
-Jim
___________________________________________________
.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
