From: Pierre Bourgin <pbou...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: xbps-src: lost in cross-build, aka on makedepends vs hostmakedepends
Date: Mon, 28 Sep 2015 03:24:28 -0700 (PDT) [thread overview]
Message-ID: <97986a39-c845-4ab9-b011-51e39102c8ca@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 760 bytes --]
Hello,
While trying to create new packages, I'm a completely lost with
cross-building.
Although my packagings are fine on native building, they fail a lot on
cross-build x86_64 to armv7hf for instance.
(example: https://github.com/voidlinux/void-packages/pull/2612)
I think I miss some concepts on cross-building ...
Do you have advices/rules on when put a given dependency into
hostmakedepends instead of makedepends in a template file ?
Why not put all depedencies in hostmakedepends for instance ?
Examples of dependencies to manage for cross-build: python, qt-devel, vala.
I've carrefully checked xbps-src/Manual.md (nothing usefull for this) and
checked various templates as examples, but I can't figure out :(
Many thanks for your help !
Pierre
[-- Attachment #1.2: Type: text/html, Size: 837 bytes --]
next reply other threads:[~2015-09-28 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 10:24 Pierre Bourgin [this message]
2015-09-28 12:13 ` Stefan Mühlinghaus
2015-09-28 13:23 ` Pierre Bourgin
2015-09-28 13:52 ` Stefan Mühlinghaus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97986a39-c845-4ab9-b011-51e39102c8ca@googlegroups.com \
--to="pbou..."@gmail.com \
--cc="void..."@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).