Re: control file question
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote: Hi Julian! The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: Build-Depends supports an arch specification, like: Build-Depends: libc-arm-version (=2.1) [arm] See policy section 7.1 for details. I know about that, but that doesn't help since it won't be compiled on that host architecture. It's for cross compiling, so for something like dietlibc-arm-dev you'll get Build-Depends that differ from dietlibc-dev on the _same_ host architecture. What if you rearrange the dietlibc packages so they are all in binary-all, and name them dietlibc-ppc, dietlibc-arm, etc. The autobuilder for each arch will build dietlibc-arch, so they will all get built without you listing build deps that work for cross-compiling. Correct me if I'm wrong, but the same .deb of dietlibc-arm-dev can be installed on any arch machine, right? That way, there doesn't have to be a separate deb for ever pair of architectures, just one for each target. (I notice that currently there are only dietlibc-dev packages, not cross-packages like dietlibc-ppc-dev that could be installed on any arch machine.) Hmm, I'm not sure if this helps any, but you might want to think about it. I'm new to this list, and I'm about to start trying to make my first package and become a developer :) -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , ns.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BCE
Re: control file question
Hi Julian! The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: Build-Depends supports an arch specification, like: Build-Depends: libc-arm-version (=2.1) [arm] See policy section 7.1 for details. I know about that, but that doesn't help since it won't be compiled on that host architecture. It's for cross compiling, so for something like dietlibc-arm-dev you'll get Build-Depends that differ from dietlibc-dev on the _same_ host architecture. -- Regards Abraham I'm also against BODY-SURFING!! ___ Abraham vd Merwe [ZR1BBQ] - The Debian Project P.O. Box 3472, Matieland, Stellenbosch, 7602 Cell: +27 82 565 4451 Email: [EMAIL PROTECTED] Http: http://people.debian.org/~abz/ PGP signature
Re: control file question
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote: Hi Julian! The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: Build-Depends supports an arch specification, like: Build-Depends: libc-arm-version (=2.1) [arm] See policy section 7.1 for details. I know about that, but that doesn't help since it won't be compiled on that host architecture. It's for cross compiling, so for something like dietlibc-arm-dev you'll get Build-Depends that differ from dietlibc-dev on the _same_ host architecture. But surely you can determine the packages needeed when dpkg-buildpackage is run on the various different architectures? I'm not sure I understand what the problem is. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
control file question
Hi! Can I put a different Build-Depends for each binary package in a control file or can there only be a Build-Depends for the source package? The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: dietlibc-dev (same target as host) dietlibc-arm-dev (arm target, different host) dietlibc-powerpc-dev (powerpc target, different host) . . . The first one's Build-Depends is normal, but the rest also have cross compile suites as Build dependancies, e.g. the dietlibc-arm-dev Build-Depends would look like this: Build-Depends: debhelper ( 3.0.0), binutils-arm (= 2.9.5.0.12), gcc-arm (= 1:2.95.2-12e4), cpp-arm (= 1:2.95.2-12e4), libc6-dev-arm (= 2.1.3-8e4), task-cross-arm (= 0.2) Obviously putting all of these dependancies in the source package will result in a package which is virtually unbuildable on almost all systems out there. -- Regards Abraham Am I SHOPLIFTING? ___ Abraham vd Merwe [ZR1BBQ] - The Debian Project P.O. Box 3472, Matieland, Stellenbosch, 7602 Cell: +27 82 565 4451 Email: [EMAIL PROTECTED] Http: http://people.debian.org/~abz/ pgpeqxxRRsD1F.pgp Description: PGP signature
Re: control file question
On Tue, Jun 19, 2001 at 11:50:52AM +0200, Abraham vd Merwe wrote: Hi! Can I put a different Build-Depends for each binary package in a control file or can there only be a Build-Depends for the source package? You can only have one Build-Depends in the control file for the source package. The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: Build-Depends supports an arch specification, like: Build-Depends: libc-arm-version (=2.1) [arm] See policy section 7.1 for details. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Re: control file question
Hi Julian! The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: Build-Depends supports an arch specification, like: Build-Depends: libc-arm-version (=2.1) [arm] See policy section 7.1 for details. I know about that, but that doesn't help since it won't be compiled on that host architecture. It's for cross compiling, so for something like dietlibc-arm-dev you'll get Build-Depends that differ from dietlibc-dev on the _same_ host architecture. -- Regards Abraham I'm also against BODY-SURFING!! ___ Abraham vd Merwe [ZR1BBQ] - The Debian Project P.O. Box 3472, Matieland, Stellenbosch, 7602 Cell: +27 82 565 4451 Email: [EMAIL PROTECTED] Http: http://people.debian.org/~abz/ pgpxMKSFsKnJr.pgp Description: PGP signature
Re: control file question
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote: Hi Julian! The problem I have is that I have a library with same host architecture but different cross compilation targets, so I have things like: Build-Depends supports an arch specification, like: Build-Depends: libc-arm-version (=2.1) [arm] See policy section 7.1 for details. I know about that, but that doesn't help since it won't be compiled on that host architecture. It's for cross compiling, so for something like dietlibc-arm-dev you'll get Build-Depends that differ from dietlibc-dev on the _same_ host architecture. But surely you can determine the packages needeed when dpkg-buildpackage is run on the various different architectures? I'm not sure I understand what the problem is. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/