Re: KDE programs won't compile
On 6 Jun 1999, Joel Ray Holveck wrote: I can only assume that we install our KDE headers somewhere different than the developers (primarily on Linux machines). By default, KDE installs to /usr/local/kde. On RedHat, the RPM installs it to /opt/kde. All the includes are in /usr/local/kde/include, the libs in /usr/local/kde/lib, etc. where the headers are on the FreeBSD machines and then you'll have to probably add a configure argument like: --with_kde_includes= /some/dir/where/kde/includes/are Most KDE programs, including the configure scripts, look for the KDEDIR environment variable. I believe that the correct thing to do with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this in /etc/profile and /etc/csh.cshrc here. (I have KDE in /usr/local/kde here, too, so I haven't tested it as /usr/local.) NO This can't be left to stand so. A port *should* set the KDEDIR to $PREFIX, not /usr/local. Just maybe I don't have my ports under /usr/local or have a separate test branch under something else? Yes, for better or for worse (I'd vote for worse), the FreeBSD ports install the kde headers in /usr/local/include.. However a simple --prefix=/usr/local *should* fix any configure problems, and if this is to make it into a FreeBSD port, use --prefix=$(PREFIX). --prefix specifies where it should install to. However, this app needs to find some 3rd-party include files, so --prefix is not appropriate. --prefix=($PREFIX) is definately appropriate - you signal with $PREFIX what is the root of your install to tree. If you have your ports under /opt, $PREFIX=/opt -- by default $PREFIX=/usr/local. FWIW, I've found that using /usr/local/kde instead of /usr/local has, in my case, been most helpful. I don't advocate it for every tiny library, but for something as large and complex as KDE, it works well. It must definately be used with moderation. Cheers, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
Most KDE programs, including the configure scripts, look for the KDEDIR environment variable. I believe that the correct thing to do with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this in /etc/profile and /etc/csh.cshrc here. (I have KDE in /usr/local/kde here, too, so I haven't tested it as /usr/local.) NO This can't be left to stand so. A port *should* set the KDEDIR to $PREFIX, not /usr/local. Just maybe I don't have my ports under /usr/local or have a separate test branch under something else? I spoke ambiguously. I did not mean that FreeBSD's KDE install should set KDEDIR to /usr/local. I meant that, if you used FreeBSD's defaults while installing KDE, then you should set KDEDIR to /usr/local in order to install other apps. --prefix specifies where it should install to. However, this app needs to find some 3rd-party include files, so --prefix is not appropriate. --prefix=($PREFIX) is definately appropriate - you signal with $PREFIX what is the root of your install to tree. If you have your ports under /opt, $PREFIX=/opt -- by default $PREFIX=/usr/local. I am referring to where to find KDE, not where to install it. I do not have KDE in $PREFIX here; apps should look in KDEDIR instead of what I set --prefix to. Normally, these are the same, but your comments about test branches etc still apply. In such a case, I would set $PREFIX to /usr/local/test while I have KDEDIR set to /usr/local/kde. An app looking for KDE in /usr/local/test would be sorely disappointed. Happy hacking, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
Most KDE programs, including the configure scripts, look for the KDEDIR environment variable. I believe that the correct thing to do with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this in /etc/profile and /etc/csh.cshrc here. (I have KDE in /usr/local/kde here, too, so I haven't tested it as /usr/local.) KDEDIR is depreciated. 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. 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? --prefix specifies where it should install to. However, this app needs to find some 3rd-party include files, so --prefix is not appropriate. Uh no. The prefix is also used by the configuration script to figure out where the kdelibs were installed to. From configure: I apologize, I did not examine the source before I spoke. I will maintain that --prefix is, in general, a target specifier rather than a source specifier. In the case of the configure script you quoted (and probably all KDE configure scripts), and if they coincide (as they usually will), then --prefix will DTRT. Which configure script did you take this from? I see the same code in many bits of KDE itself. Happy hacking, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
On Sat, Jun 05, 1999 at 09:08:54PM +0300, Tomer Weller wrote: every small kde program i try to install (right now i tried Knewmail and Kover) i get : checking for kde headers installed... configure: error: your system is not able to compile a small KDE application! Check, if you installed the KDE header files correctly. i'm using a current machine as if last night, installed kde from ports (yes, kde-libs was compiled with -CURRENT and EGCS) any idea what's the problem ? $./configure --prefix=/usr/local that should solve it. regards, -Oscar -- For PGP Public Key: finger oboni...@fisicc-ufm.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
Hi, every small kde program i try to install (right now i tried Knewmail and Kover) i get : checking for kde headers installed... configure: error: your system is not able to compile a small KDE application! Check, if you installed the KDE header files correctly. i'm using a current machine as if last night, installed kde from ports (yes, kde-libs was compiled with -CURRENT and EGCS) I can only assume that we install our KDE headers somewhere different than the developers (primarily on Linux machines). Dig around and figure out where the headers are on the FreeBSD machines and then you'll have to probably add a configure argument like: --with_kde_includes= /some/dir/where/kde/includes/are Dig through the knewmail configure script at the top and look for an option like this. Brett *** Brett Taylorbr...@peloton.physics.montana.edu * br...@daemonnews.org * * http://www.daemonnews.org/* *** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
On Sat, 5 Jun 1999, Brett Taylor wrote: I can only assume that we install our KDE headers somewhere different than the developers (primarily on Linux machines). Dig around and figure out where the headers are on the FreeBSD machines and then you'll have to probably add a configure argument like: --with_kde_includes= /some/dir/where/kde/includes/are Dig through the knewmail configure script at the top and look for an option like this. Yes, for better or for worse (I'd vote for worse), the FreeBSD ports install the kde headers in /usr/local/include.. However a simple --prefix=/usr/local *should* fix any configure problems, and if this is to make it into a FreeBSD port, use --prefix=$(PREFIX). - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
I can only assume that we install our KDE headers somewhere different than the developers (primarily on Linux machines). By default, KDE installs to /usr/local/kde. On RedHat, the RPM installs it to /opt/kde. All the includes are in /usr/local/kde/include, the libs in /usr/local/kde/lib, etc. where the headers are on the FreeBSD machines and then you'll have to probably add a configure argument like: --with_kde_includes= /some/dir/where/kde/includes/are Most KDE programs, including the configure scripts, look for the KDEDIR environment variable. I believe that the correct thing to do with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this in /etc/profile and /etc/csh.cshrc here. (I have KDE in /usr/local/kde here, too, so I haven't tested it as /usr/local.) Yes, for better or for worse (I'd vote for worse), the FreeBSD ports install the kde headers in /usr/local/include.. However a simple --prefix=/usr/local *should* fix any configure problems, and if this is to make it into a FreeBSD port, use --prefix=$(PREFIX). --prefix specifies where it should install to. However, this app needs to find some 3rd-party include files, so --prefix is not appropriate. FWIW, I've found that using /usr/local/kde instead of /usr/local has, in my case, been most helpful. I don't advocate it for every tiny library, but for something as large and complex as KDE, it works well. Cheers, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KDE programs won't compile
On 6 Jun 1999, Joel Ray Holveck wrote:
By default, KDE installs to /usr/local/kde. On RedHat, the RPM
installs it to /opt/kde. All the includes are in
/usr/local/kde/include, the libs in /usr/local/kde/lib, etc.
Yup.
Most KDE programs, including the configure scripts, look for the
KDEDIR environment variable. I believe that the correct thing to do
with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this
in /etc/profile and /etc/csh.cshrc here. (I have KDE in
/usr/local/kde here, too, so I haven't tested it as /usr/local.)
KDEDIR is depreciated.
--prefix specifies where it should install to. However, this app
needs to find some 3rd-party include files, so --prefix is not
appropriate.
Uh no. The prefix is also used by the configuration script to figure out
where the kdelibs were installed to. From configure:
ac_default_prefix=${KDEDIR:-/usr/local/kde}
[...]
includedir='${prefix}/include'
[...]
echo $ac_n checking for KDE... $ac_c 16
echo configure:4014: checking for KDE 5
if test ${prefix} != NONE; then
kde_includes=${prefix}/include
ac_kde_includes=$prefix/include
FWIW, I've found that using /usr/local/kde instead of /usr/local has,
in my case, been most helpful. I don't advocate it for every tiny
library, but for something as large and complex as KDE, it works well.
Yes, KDE scatters too many things too many places to really be a good fit
in /usr/local/kde. Plus putting it in its own directory makes for easy
removal and switching between versions of KDE.
- alex
I thought felt your touch
In my car, on my clutch
But I guess it's just someone who felt a lot like I remember you.
- Translator
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
