On Wed, 27 Apr 2011 18:44:39 +0200, Goswin von Brederlow <goswin-v-b@web.de> wrote: > Stephen Kitt <steve@sk2.org> writes: > > So if I understand things correctly that would mean using /usr/lib/win32 > > and /usr/lib/win64, regardless of the binutils/gcc triplet (which is fine > > as > > If that is what dpkg-architecture outputs. The path should never be > hardcoded. That makes sense, of course. > > Goswin, I take it you're advocating building _win32.deb packages (or > > something similar) - is that correct? I didn't even realise that would be > > possible without appropriate buildds... I know about “dpkg-buildpackage > > -aâ€_ or “pdebuild --architectureâ€_ for local rebuilds, but would > > rebuilding such a package be possible on the existing buildd network? > > No. You would still build a _all.deb. The debian/rules file would just > ask dpkg-architecture what the right multiarch dir is for the win32 ABI. > You can ask dpkg-architecture for information of an architecture other > than what you are building for. OK, thanks for clarifying that! Regards, Stephen
Attachment:
signature.asc
Description: PGP signature