Re: build two binary packages with different configure parameters
On Mon, May 21, 2007 at 11:26:02AM +0200, Miriam Ruiz wrote: I had to do something like that for ultrastar-ng. I created two different directories, called configure from inside each of them with the proper different parameters and had to duplicate the make and make install. Dunno if it's not elegan enough, but I didn't want to make it too complex. You might want to have a look at it. There's nothing special in it anyway. I finally stole a quite elegant solution from mrxvt. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: build two binary packages with different configure parameters
I had to do something like that for ultrastar-ng. I created two different directories, called configure from inside each of them with the proper different parameters and had to duplicate the make and make install. Dunno if it's not elegan enough, but I didn't want to make it too complex. You might want to have a look at it. There's nothing special in it anyway. Greetings, Miry
Re: build two binary packages with different configure parameters
[I apologize for leaving this for two weeks, I moved house in the mean time and was not online for a terrible lot of time] On Sat, May 05, 2007 at 10:44:19AM -0400, Justin Pryzby wrote: On Sat, May 05, 2007 at 03:07:53PM +0200, Marc Haber wrote: I have a package which uses debhelper at build time, and is built by a rather simple configure - make - make install triathlon. As it fails badly on xen, the xen people ask to provide a xen-enabled binary package. Thus, I need to build the package once with a normal configure, and a second time with configure --with-extra-libs=foo. The rest of the build process is identical. All packages that I have seen which do this duplicate the entire build process in debian/rules by having configure-foo, configure-bar, build-foo, build-bar, install-foo and install-bar targets along with all stamps explicitly doubled. I hate the idea of having to do this with my package just to have a single different configure call. Is there any more elegant way to do this? If so, which package uses it that I can steal from? vim is referenced as a prototype for multiple binary packages with different compilation variations. It's perhaps not clear from the large rules, but it really does handle 10+ such packages, and only calls configure once (configure-stamp-%:, this is quite probably not portable make) and this includes a make clean to remove the earlier-compiled binaries objects and such for compilation of the current binary. I agree that vim's build system is rather elegant. However, I fail to see how to handle the case where the upstream sources are not in a dedicated directory which can conveniently be moved away after building a variant. I feel that the vim package might be a number too large to handle this. Any more hints? Usually make is supposed to be as parallelized as possible; as such, rules that call $(MAKE) again are pretty inelegant. However, for this case, you want to avoid parallelizing it: the compilations must be serial not concurrent. Yes. I assume that all packages that build multiple variants of a package do so sequentially. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: build two binary packages with different configure parameters
On Sat, May 05, 2007 at 03:07:53PM +0200, Marc Haber wrote: Hi, I have a package which uses debhelper at build time, and is built by a rather simple configure - make - make install triathlon. As it fails badly on xen, the xen people ask to provide a xen-enabled binary package. Thus, I need to build the package once with a normal configure, and a second time with configure --with-extra-libs=foo. The rest of the build process is identical. All packages that I have seen which do this duplicate the entire build process in debian/rules by having configure-foo, configure-bar, build-foo, build-bar, install-foo and install-bar targets along with all stamps explicitly doubled. I hate the idea of having to do this with my package just to have a single different configure call. Is there any more elegant way to do this? If so, which package uses it that I can steal from? vim is referenced as a prototype for multiple binary packages with different compilation variations. It's perhaps not clear from the large rules, but it really does handle 10+ such packages, and only calls configure once (configure-stamp-%:, this is quite probably not portable make) and this includes a make clean to remove the earlier-compiled binaries objects and such for compilation of the current binary. Usually make is supposed to be as parallelized as possible; as such, rules that call $(MAKE) again are pretty inelegant. However, for this case, you want to avoid parallelizing it: the compilations must be serial not concurrent. In fact the template debian/rules created by dhmake does this: |binary-common: [... dh foo ...] |# Build architecture independant packages using the common target. |binary-indep: build-indep install-indep |$(MAKE) -f debian/rules DH_OPTIONS=-i binary-common | |# Build architecture dependant packages using the common target. |binary-arch: build-arch install-arch |$(MAKE) -f debian/rules DH_OPTIONS=-s binary-common The debhelper commands look at the DH_OPTIONS from the environment so the arch/indep targets do different things and build different packages. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
