Re: Re: Compiling KDE from CVS, but keeping Debianized packages?
Hello,
forgive me my newby-questions, but I'll have a couple of more small Q's and before starting long compiles with potentially results that I don't want, I'd like to double-check a couple of things.
- How are the CFLAGS/CXXFLAGS set? For debug level, optimization leve, target CPU, etc? Do I just set them on the command line before starting to make the debian/rules?
- How do I enable debugging-information in the files? By setting CXXFLAGS as above, or by a different magic?
- To prevent binaries from being stripped, I just remove the lines "dh_strip" from the debian/rules files?
- To build kdelibs/kdebase with SSL, what do I do? Will kdelibs-crypto and kdebase-crypto automatically be built with the rest, or is special action required? Or could I just remove the lines "--without-ssl" from the configure-line in the debian/rules?
I think those are the questions I wanted to ask, thanks in advance for answers!
--Tim :-)
>
> Van: "Ivan E. Moore II" <rkrusty@tdyc.com>
> Datum: Sat, 13 Jan 2001 16:44:27 -0700
> Aan: tnvander@chello.nl
> CC: debian-kde@lists.debian.org
> Onderwerp: Re: Compiling KDE from CVS, but keeping Debianized packages?
>
> On Sun, Jan 14, 2001 at 03:06:57AM +0330, tnvander@chello.nl wrote:
> > Hello,
> >
> > I'm wondering how I can compile KDE from CVS, but keep everything installed as Debian packages? I guess I need to download the source-packages for a lot of the KDE Debian packages, but each KDE CVS module is split into plenty of Debian packages so I'm not quite sure how to approach it.
> >
> > Any hints from anyone?
> >
>
> cd kdelibs
> debian/rules binary
>
> for example. take a look at debian/control...at the top is a line that
> starts out as Build-Depends...make sure you have those packages installed.
>
> Ivan
> --
> ----------------
> Ivan E. Moore II
> rkrusty@tdyc.com
> http://snowcrash.tdyc.com
> GPG KeyID=90BCE0DD
> GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
>
Reply to:
- Follow-Ups:
- korn & imap.
- From: Bart Oldeman <Bart.Oldeman@bristol.ac.uk>