Thank You. This is what I came up with:
override_dh_auto_configure: ifeq ($(DEB_HOST_ARCH_OS), $(filter $(DEB_HOST_ARCH_OS), linux)) ifeq ($(DEB_HOST_ARCH), $(filter $(DEB_HOST_ARCH), amd64 i386 x32)) # amd64, i386, x32 and linux dh_auto_configure -- -DCLASSICBUILD=YES -DI2CBUILD=YES else # not amd64, i386, x32 but linux dh_auto_configure -- -DCLASSICBUILD=NO -DI2CBUILD=YES endif else #not linux: kfree, hurd ... ifeq ($(DEB_HOST_ARCH_CPU), $(filter $(DEB_HOST_ARCH_CPU), amd64 i386)) #kfree-amd64, kfree-i386, hurd-i386, 3 dh_auto_configure -- -DI2CBUILD=NO -DCLASSICBUILD=YES endif endif Just out of curiousity, is there a place where I can see what dpkg-architecture returns for every architecture?t 2 On 14 February 2014 17:35, Sven Joachim <svenj...@gmx.de> wrote: > On 2014-02-14 13:52 +0100, Dariusz Dwornikowski wrote: > > > After some inquiry, I can see that it can build only on amd64, i386, > > kfreebsd-i386, kfreebsd-amd64 and hud-i386, because the lib it depends on > > (libx86) is only present there. On other architectures I could build only > > one of the binaries -- parse-edid, because it does not depend on anything > > else. > > I meant that you could build read-edid on other Linux architectures as > well (with I2C only). > > > So my new idea is: > > > > on amd64, i386 I build both binaries CLASSIC and I2C > > Probably on x32 as well, although this failed with 3.0.1-1 for some > unknown reason (there is no build log :-(). > > > on kfreebsd-i386, kfreebsd-amd64 and hurd-i386 I build both binaries > CLASSIC > > So, as a summary you want to build CLASSIC if DEB_HOST_ARCH_CPU is amd64 > or i386. > > > on the rest I build only parse-edid (only get-edid uses build options). > > I'd say you should try to build read-edid with I2C if > DEB_HOST_ARCH_OS=linux. > > Cheers, > Sven > -- Pozdrawiam, Dariusz Dwornikowski, Assistant Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41
