[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xlog-discussion] KPSK with Xlog remote logging

From: Kjellquist, David T
Subject: RE: [Xlog-discussion] KPSK with Xlog remote logging
Date: Tue, 10 Feb 2004 14:22:44 -0500

I should have said kdevelop would have worked. I assumed you didn't want
to use it and wanted to compile without it.

-----Original Message-----
From: Joop Stakenborg [mailto:address@hidden
Sent: Tuesday, February 10, 2004 1:27 PM
To: Kjellquist, David T
Cc: address@hidden; address@hidden
Subject: Re: [Xlog-discussion] KPSK with Xlog remote logging

On Tue, 10 Feb 2004 10:27:51 -0500
DAVID KJELLQUIST <address@hidden> wrote:

> Joop;
>     Got it this time <grin>. Of course you are correct, you should not
> have to individually compile the code containing QObject references.
> It turns out that the source of the problem is the signal/slot 
> communications used by Qt. Moc is a preprocessor that processes these 
> reserved words. In the the Makefile.am in the kpsk subdir  METASOURCES
> = AUTO   is the directive to invoke automoc. I don't know why it isn't
> happening because the directive is in the Makefile.am. But, you should
> be able to invoke automoc directly just like autoconf. automoc is a
> Perl script. I will try this tonight myself.

Yeah! I got it! The trick is to use kdevelop!
Open the kpsk.kdevprj file from the Project->Open menu, next select
Build->Autoconf and Automake, Build->configure, Build->make.

Apparently kdevelop does some magical things, because I noticed moc now
gets called for every header file. Also notice automake1.6 is needed,
which I didn't have installed.

Looking good so far! The remote logging works okay. If somebody else
wants to give it a try, I could do a 'make dist' and make the file
available somewhere (that is, if david doesn't object).

Thanks so far Dave,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]