From owner-freebsd-current Sun Jun 13 16:24:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-1.ppp.wenet.net [206.15.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 3167515182 for ; Sun, 13 Jun 1999 16:24:49 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id QAA28945; Sun, 13 Jun 1999 16:24:17 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 13 Jun 1999 16:24:17 -0700 (PDT) From: Alex Zepeda To: Joel Ray Holveck Cc: Brett Taylor , Tomer Weller , "" Subject: Re: KDE programs won't compile In-Reply-To: <86909xdfa3.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How do you mean "depreciated"? Should users not set it, or > applications not check for it, or what? [...] > The 2.0 kdelibs/README states: > IMPORTANT: most applications need KDEDIR as the directory where KDE is > installed. Please set this in your login file. > Of course, this could be out-of-date. Yes, I think this is out of date, I've just let intertia set in, and haven't removed it. I seem to recall a bunch of discussion about the removal of the KDEDIR variable, but as of yet, I still see a lot of getenv("KDEDIR"). Actually, I just checked this, if $KDEDIR isn't set it uses the compiletime default, so yes, KDEDIR isn't really needed, as long as ld can find the libs, and gcc can find the headers. > I do not know of an alternate mechanism. A brief examination of the > 2.0 kdebase and koffice configure.in's do not immediately reveal one > either, other than --prefix. Is this the accepted method, then? > What if a user wants to install something in a different place than > the rest of KDE? I think this is generally frowned upon, but I know kdebase has --disable-path-check, and I guess if something is based off the "KDE autoconf gunk" it could easily include that switch. If a program doesn't use autoconf or doesn't have the switch, you're stuck manually copying files. According to Stephan Kulow: blarf: the program has to KStandardDirs::registerPrefix() for now it just won't work (I'm rather pissed at KStandDirs right now anyways for breaking some stuff I spent time fixing, but that's another thread). > Which configure script did you take this from? I see the same code in > many bits of KDE itself. kdebase. Well, 90% of the autoconf code is shared between all the kde modules. It's been setup in the CVS/CVSup module kde-common if you want to take a look. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message