What configuration directory installation locations (--prefix, --libdir, --sysconfdir, etc.) are you using for all of your trinity builds?
Are the locations the same for Lenny (KDE4/QT4 not installed) as the others where KDE4/QT4 are installed?
Yes, they are identical whether or not KDE4/Qt4 is installed.
Thanks.
Darrell
What I use for the Debian builds is: --prefix=/opt/trinity --includedir=/opt/trinity/include/kde --mandir=/opt/trinity/share/man --infodir=/opt/trinity/share/info --with-extra-libs=/opt/trinity/lib --sysconfdir=/etc --localstatedir=/var --libexecdir="${prefix}/lib/kdebase-kde3" --disable-rpath --with-xinerama --enable-closure (when needed, which is most of the time)
There may be one or two that are module specific that I did not mention here, but this should permit close compatibility with the Debian builds.
Tim
What configuration directory installation locations (--prefix, --libdir, --sysconfdir, etc.) are you using for all of your trinity builds?
Are the locations the same for Lenny (KDE4/QT4 not installed) as the others where KDE4/QT4 are installed?
Yes, they are identical whether or not KDE4/Qt4 is installed.
Thanks.
Darrell
What I use for the Debian builds is: --prefix=/opt/trinity --includedir=/opt/trinity/include/kde --mandir=/opt/trinity/share/man --infodir=/opt/trinity/share/info --with-extra-libs=/opt/trinity/lib --sysconfdir=/etc --localstatedir=/var --libexecdir="${prefix}/lib/kdebase-kde3" --disable-rpath --with-xinerama --enable-closure (when needed, which is most of the time)
There may be one or two that are module specific that I did not mention here, but this should permit close compatibility with the Debian builds.
Tim
CORRECTION: --libexecdir="${prefix}/lib/kdebase-kde3" is module specific and should probably be omitted.
Tim
What I use for the Debian builds is: --prefix=/opt/trinity --includedir=/opt/trinity/include/kde --mandir=/opt/trinity/share/man --infodir=/opt/trinity/share/info --with-extra-libs=/opt/trinity/lib --sysconfdir=/etc --localstatedir=/var --libexecdir="${prefix}/lib/kdebase-kde3" --disable-rpath --with-xinerama --enable-closure (when needed, which is most of the
time)
CORRECTION: --libexecdir="${prefix}/lib/kdebase-kde3" is module specific and should probably be omitted.
How do I learn the defaults if any of those variables are not explicitly declared?
What I use for the Debian builds is: --prefix=/opt/trinity --includedir=/opt/trinity/include/kde --mandir=/opt/trinity/share/man --infodir=/opt/trinity/share/info --with-extra-libs=/opt/trinity/lib --sysconfdir=/etc --localstatedir=/var --libexecdir="${prefix}/lib/kdebase-kde3" --disable-rpath --with-xinerama --enable-closure (when needed, which is most of the
time)
CORRECTION: --libexecdir="${prefix}/lib/kdebase-kde3" is module specific and should probably be omitted.
How do I learn the defaults if any of those variables are not explicitly declared?
I am not sure--last I checked it is distribution dependent. Maybe someone on this list is more familiar with autoconf than I am and could shed some light on this topic?
Tim
I am not sure--last I checked it is distribution dependent. Maybe someone on this list is more familiar with autoconf than I am and could shed some light on this topic?
I'm curious because I don't declare all of those explicitly. I'm wondering whether all or most of them should be explicitly declared.
-
Darrell Anderson -
Timothy Pearson