Re: autoconfigurable package: how to build two configurations?
On Sun, Sep 23, 2007 at 06:50:02PM -0500, Steve M. Robbins wrote: Hello, Are there any examples of a package that builds two binary packages, each from a distinct run of configure? My specific case is soqt, which provides a Qt interface to Coin (OpenInventor). There is a sentiment [1] that I provide packages for Qt3 as well as packages for Qt4. I believe that I need to run the autoconf-generated configure script twice and build each configuration in its own build directory. I'd like to see a package that does this already. Preferably, one that uses cdbs. The dev-ref (still) uses vim as an example afaik. A good goal would be to reduce duplication of code within the rules file. Justin References [0] http://lists.debian.org./debian-mentors/2007/05/msg00069.html
autoconfigurable package: how to build two configurations?
Hello, Are there any examples of a package that builds two binary packages, each from a distinct run of configure? My specific case is soqt, which provides a Qt interface to Coin (OpenInventor). There is a sentiment [1] that I provide packages for Qt3 as well as packages for Qt4. I believe that I need to run the autoconf-generated configure script twice and build each configuration in its own build directory. I'd like to see a package that does this already. Preferably, one that uses cdbs. Any suggestions? Thanks, -Steve [1] http://lists.debian.org/debian-devel/2007/08/msg00700.html signature.asc Description: Digital signature
Re: autoconfigurable package: how to build two configurations?
On 23/09/2007, Steve M. Robbins [EMAIL PROTECTED] wrote: Hello, Are there any examples of a package that builds two binary packages, each from a distinct run of configure? You first have to configure, build, install one of the packages and then configure, build, install the second one; and in the same target create the binary .deb. You'd have something like this: build-stamp-qt3: dh_testdir ./configure --... build-stamp-qt4: dh_testdir ./configure --... build-qt4: build-stamp-qt4 dh_testdir $(MAKE) ... build-qt3: build-stamp-qt3 dh_testdir $(MAKE) ... install-qt3: build-qt3 dh_testdir dh_testroot dh_installdirs DEST_DIR=debian/foo-qt3 $(MAKE) install install-qt4: build-qt4 dh_testdir dh_testroot dh_installdirs DEST_DIR=debian/foo-qt4 $(MAKE) install My specific case is soqt, which provides a Qt interface to Coin (OpenInventor). There is a sentiment [1] that I provide packages for Qt3 as well as packages for Qt4. I believe that I need to run the autoconf-generated configure script twice and build each configuration in its own build directory. I'd like to see a package that does this already. Preferably, one that uses cdbs. Any suggestions? Thanks, -Steve [1] http://lists.debian.org/debian-devel/2007/08/msg00700.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG9vuq0i2bPSHbMcURArOmAJsFJiyU3bMiZaaCNXKiPFz6i9AdPQCfQKt5 rEPADmhDqf94y22YJFCU+NI= =LTV0 -END PGP SIGNATURE- -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Say NO to Microsoft Office broken standard. See http://www.noooxml.org/petition -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: autoconfigurable package: how to build two configurations?
Raphael Geissert wrote: On 23/09/2007, Steve M. Robbins [EMAIL PROTECTED] wrote: Hello, Are there any examples of a package that builds two binary packages, each from a distinct run of configure? You first have to configure, build, install one of the packages and then configure, build, install the second one; and in the same target create the binary .deb. Actually, you could use different build directories: configure: configure-a configure-b configure-a: dh_testdir mkdir build-a cd build-a ../configure --flags touch $@ configure-b: dh_testdir mkdir build-b cd build-b ../configure --otherflags touch $@ build: build-a build-b build-a: configure-a cd build-a make build-b: configure-b cd build-b make etc etc. This way you don't need to erase one version to build the other. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: autoconfigurable package: how to build two configurations?
Hi, Felipe Sateler wrote: Actually, you could use different build directories: [...] This way you don't need to erase one version to build the other. Yes, that is in fact preferable, as building can happen without root privileges that way. Back when I maintained it, python-imaging used to build like that. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
