From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/7] Split apart qemu-config
Date: Mon, 20 Aug 2012 12:08:16 +0100 [thread overview]
Message-ID: <50321AA0.7050404@communistcode.co.uk> (raw)
In-Reply-To: <cover.1345458715.git.paul.eggleton@linux.intel.com>
On 20/08/12 11:32, Paul Eggleton wrote:
> *** Note: this is an RFC series, please do not merge yet! ***
>
> Split apart qemu-config, replacing it with a task (task-core-device-devel)
> that is not specific to usage together with QEMU. oprofileui is now split
> into client and server parts, and together with the prevous work to merge
> dbus-launch back into the main dbus package, this makes things work much
> more smoothly when this task is installed with x11 removed from
> DISTRO_FEATURES. Additionally it was found that oprofileui was not
> correctly depending on oprofile itself, and this has also been fixed.
> (This is a reworking of a patch series I sent out some time ago.)
>
> There is a remaining question however - is this task actually useful?
> For reference, it enables the following:
>
> 1) Use of distcc to accelerate compiling applications within the
> emulated environment using direct compilation on the host
> 2) Accessing the root filesystem via NFS
> 3) Remote profiling via oprofileui
> 4) Running applications in the target from the Anjuta IDE
There has been no development work on Anjuta for 22 months now
(according to git logs) so is this even supported any more? I gave it a
go once, but never really got anywhere.
>
> 5) bash shell
>
> Whilst these might have minor utility on an individual basis, I can't
> honestly say that that the overall set seems particularly useful to me
> as a whole; and some of the parts are less useful than they used to be -
> is oprofile commonly used these days now that tools like perf are
> available? Is anyone actually using Anjuta for embedded development? For
> that matter, does anyone regularly build applications within QEMU
> emulated targets?
Personally, I have never used QEMU for developing embedded software due
to the fact that the hardware for the proposed application to run on is
always quite specific.
Regards,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2012-08-20 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 10:32 [RFC PATCH 0/7] Split apart qemu-config Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 1/7] qemu-config: relicense as MIT Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 2/7] oprofileui: split server to separate recipe to avoid X11 dependency Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 3/7] qemu-config: split out anjuta-remote-run Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 4/7] oprofileui-server: move initscript from qemu-config Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 5/7] qemu-config: split out shutdown icon to its own recipe Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 6/7] qemu-config: split out export of root via NFS " Paul Eggleton
2012-08-20 10:32 ` [RFC PATCH 7/7] qemu-config: turn into distcc-config and a task Paul Eggleton
2012-08-20 11:08 ` Jack Mitchell [this message]
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=50321AA0.7050404@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/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