Patchwork [RFC,0/7] Split apart qemu-config

login
register
mail settings
Submitter Paul Eggleton
Date Aug. 20, 2012, 10:32 a.m.
Message ID <cover.1345458715.git.paul.eggleton@linux.intel.com>
Download mbox
Permalink /patch/34923/
State New
Headers show

Pull-request

git://git.openembedded.org/openembedded-core-contrib paule/qemu-config

Comments

Paul Eggleton - Aug. 20, 2012, 10:32 a.m.
*** 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
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?




Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.

The following changes since commit c39e823138cbf4210e17bdb95ca322ec0a6c8f78:

  libpam: Fix missing DESTDIR for a mkdir causing build failures (2012-08-19 13:31:59 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/qemu-config
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qemu-config

Paul Eggleton (7):
  qemu-config: relicense as MIT
  oprofileui: split server to separate recipe to avoid X11 dependency
  qemu-config: split out anjuta-remote-run
  oprofileui-server: move initscript from qemu-config
  qemu-config: split out shutdown icon to its own recipe
  qemu-config: split out export of root via NFS to its own recipe
  qemu-config: turn into distcc-config and a task

 meta/recipes-bsp/qemu-config/qemu-config.bb        |   45 ---
 .../qemu-config/qemu-config/COPYING.GPL            |  339 --------------------
 .../devel-config/anjuta-remote-run.bb              |   19 ++
 .../anjuta-remote-run}/anjuta-remote-run           |    0
 .../recipes-devtools/devel-config/distcc-config.bb |   25 ++
 .../devel-config/distcc-config}/distcc.sh          |    2 +-
 .../devel-config/nfs-export-root.bb                |   17 +
 .../devel-config/nfs-export-root}/exports          |    0
 .../tasks/task-core-device-devel.bb                |   18 ++
 .../oprofile/oprofileui-server/init}               |    8 +-
 .../oprofile/oprofileui-server_git.bb              |   24 ++
 meta/recipes-kernel/oprofile/oprofileui.inc        |   11 +-
 meta/recipes-kernel/oprofile/oprofileui_git.bb     |   10 +-
 .../shutdown-desktop/shutdown-desktop.bb           |   20 ++
 .../shutdown-desktop}/shutdown.desktop             |    0
 meta/recipes-sato/tasks/task-core-x11-sato.bb      |    3 +-
 16 files changed, 141 insertions(+), 400 deletions(-)
 delete mode 100644 meta/recipes-bsp/qemu-config/qemu-config.bb
 delete mode 100644 meta/recipes-bsp/qemu-config/qemu-config/COPYING.GPL
 create mode 100644 meta/recipes-devtools/devel-config/anjuta-remote-run.bb
 rename meta/{recipes-bsp/qemu-config/qemu-config => recipes-devtools/devel-config/anjuta-remote-run}/anjuta-remote-run (100%)
 create mode 100644 meta/recipes-devtools/devel-config/distcc-config.bb
 rename meta/{recipes-bsp/qemu-config/qemu-config => recipes-devtools/devel-config/distcc-config}/distcc.sh (57%)
 create mode 100644 meta/recipes-devtools/devel-config/nfs-export-root.bb
 rename meta/{recipes-bsp/qemu-config/qemu-config => recipes-devtools/devel-config/nfs-export-root}/exports (100%)
 create mode 100644 meta/recipes-devtools/tasks/task-core-device-devel.bb
 rename meta/{recipes-bsp/qemu-config/qemu-config/qemu-autostart => recipes-kernel/oprofile/oprofileui-server/init} (74%)
 create mode 100644 meta/recipes-kernel/oprofile/oprofileui-server_git.bb
 create mode 100644 meta/recipes-sato/shutdown-desktop/shutdown-desktop.bb
 rename meta/{recipes-bsp/qemu-config/qemu-config => recipes-sato/shutdown-desktop/shutdown-desktop}/shutdown.desktop (100%)
ml@communistcode.co.uk - Aug. 20, 2012, 11:08 a.m.
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,