atom feed21 messages in org.freebsd.freebsd-portsRe: [kde-freebsd] Building kdebase3
FromSent OnAttachments
Jonathan ChenAug 2, 2002 2:42 am 
Michael NottebrockAug 2, 2002 3:13 am.h
Michael NottebrockAug 2, 2002 3:49 am 
Alan EAug 2, 2002 3:55 am 
Michael NottebrockAug 2, 2002 4:08 am 
Andy FawcettAug 2, 2002 4:09 am 
Frerich RaabeAug 2, 2002 4:13 am.diff
Alan EAug 2, 2002 4:14 am 
Alan EAug 2, 2002 4:19 am 
Michael NottebrockAug 2, 2002 4:38 am 
Karel J. BosschaartAug 2, 2002 6:20 am 
Frerich RaabeAug 2, 2002 6:21 am 
Michael NottebrockAug 2, 2002 6:41 am 
Michael NottebrockAug 2, 2002 6:59 am 
Matthew EmmertonAug 2, 2002 8:31 am 
Alan EAug 2, 2002 9:50 am 
Jonathan ChenAug 2, 2002 1:26 pm 
Kent StewartAug 2, 2002 1:46 pm 
Kent StewartAug 2, 2002 6:59 pm 
Jonathan ChenAug 3, 2002 6:21 pm 
Alan EAug 4, 2002 12:45 am 
Subject:Re: [kde-freebsd] Building kdebase3
From:Alan E (ala@geeksrus.net)
Date:Aug 2, 2002 4:19:19 am
List:org.freebsd.freebsd-ports

On Fri, Aug 02, 2002 at 01:14:00PM +0200, Frerich Raabe wrote: Content-Description: clearsigned data

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Friday 02 August 2002 12:55, Alan E wrote:

On Fri, Aug 02, 2002 at 12:14:18PM +0200, Michael Nottebrock wrote: Apparently, it's possible to build things in such an order that klistview.h doesn't exist at the time uic is run and so the include does not get generated; at least that's my hypothesis as of now. i don't think uic is borked, but i think the environment around it is

That .ui files fails to include a file. Try the attached patch please.

Nope. Try again. It's not a kdebase issue. I cannot speak for will, but I will not commit any patch to kdebase over this, as there is nothing wrong with it. This is a build issue. Uic discovers the include files it needs if they exist, ANAICT.

klistview.h a new file with 3.0.2?

How else could kdebase get built without kdelibs installed? Answer that, and we're that much closer to the real solution.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message