From: Henning Schild <henning.schild@siemens.com>
To: <andrea.marson.dave@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: Cross-building and debugging
Date: Mon, 30 Oct 2017 14:43:05 +0100 [thread overview]
Message-ID: <20171030144305.21dcf20c@md1em3qc> (raw)
In-Reply-To: <0b55db7d-e602-4f4b-b6d5-bc1c0a0e18e8@googlegroups.com>
Am Mon, 30 Oct 2017 01:34:19 -0700
schrieb <andrea.marson.dave@gmail.com>:
> Hi everybody,
>
> IIUC, when using Isar it is implicitly assumed that the user
> applications are natively built on the target.
> If, for any reason, this is not possibile, one has to cross-build the
> applications.
Why would that not be possible? I guess you just do not have the
patience to wait for the slow qemu-wrapped compiler.
If you ask me now, cross compile support should not be added to Isar,
because it is against what Debian is doing. But maybe someone will
convince me otherwise some day.
> Which approach do you recommend to set up the cross-build
> environment, in order to make it work smoothly with Isar?
There are a few patches out there that enable cross builds, but none of
that stuff was proposed for upstream yet.
https://github.com/ilbers/isar/commits/lenormf/develop-l20170602-dpkg-cross
https://groups.google.com/d/msgid/isar-users/8fe13268-9bfa-4b24-897a-133c9530c188%40googlegroups.com
If the only upside of such complexity is gain in speed i would probably
reject patches that try to introduce something like that. With the
recently merged cache features one could just keep the .debs and the
compile-time would only be a problem once and maybe for CI.
Today you could use dpkg-raw and just package your binaries, that maybe
came from another build-system. Or you could write a recipe that adds
cross-compile tasks to dpkg-raw.
>> inherit dpkg-raw
>>
>> do_compile() {
>> make CROSS_COMPILE=/foobar/
>> ...
>> }
>>
>> addtask compile after do_unpack before do_install
Henning
> Thank you,
> Andrea
>
next prev parent reply other threads:[~2017-10-30 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 8:34 andrea.marson.dave
2017-10-30 12:49 ` Andreas Reichel
2017-10-30 13:43 ` Henning Schild [this message]
2017-10-31 15:34 ` Baurzhan Ismagulov
2017-10-31 15:00 ` Baurzhan Ismagulov
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=20171030144305.21dcf20c@md1em3qc \
--to=henning.schild@siemens.com \
--cc=andrea.marson.dave@gmail.com \
--cc=isar-users@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