Building for different architectures

[Kyle Fazzari]

On 02/07/2017 08:20 AM, Oliver Grawert wrote:
> hi,
> On Di, 2017-02-07 at 16:07 +0000, Alan Pope wrote:
>> Hi,
>>
>> Suppose I have a snap which requires a couple of non-archive debs as
>> stage packages. Typically I'd have a part for each which uses the
>> source: of a url directly to the deb using the dump plugin. This
>> works
>> fine building on my amd64 laptop (or wherever) and I end up with an
>> amd64 snap.
>>
>> However, if I get a request for an i386 (or indeed armhf) snap, it
>> will break because my i386 snapcraft run will pull an amd64 deb. If I
>> was pulling archive packages then of course the build can run in
>> launchpad and it will do the Right Thing. However, if my yaml
>> contains
>> hard coded arch-specific (non-archive) debs, that breaks, pulling in
>> amd64 deb on an i386 builder.
>>
>> I could have separate yamls per arch of course, but that seems
>> needlessly messy. What have others done in this case?
>>
> do you mean https://bugs.launchpad.net/snapcraft/+bug/1655797 ?
> looks like is was just fixed last week though...
> not sure how/if that works for "non-archive debs" though

It doesn't, I'm afraid. That fix (and another coming soon[1]) are
specific to stage-packages, whereas it sounds like popey is using
`source` directly. I don't think there's a way to do this today, but we
were discussing implementing something similar for sources in the future.

[1]: https://github.com/snapcore/snapcraft/pull/1059

-- 
Kyle Fazzari (kyrofa)
Software Engineer
Canonical Ltd.
kyle at canonical.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170207/b99aa9be/attachment.sig>