All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: EXPORT_FUNCTIONS - change in behaviour proposal
Date: Mon, 10 Dec 2012 16:09:07 +0000	[thread overview]
Message-ID: <1355155747.29967.31.camel@ted> (raw)

After Enrico's reported problem, I've been poking around the
EXPORT_FUNCTIONS code. Currently OE-Core metadata generates list A
below. In particular, this leads to code like:

 do_configure calls gnomebase_do_configure
 gnomebase_do_configure calls autotools_do_configure

which has a level of indirection. The gnomebase class never references
do_configure. I can appreciate adding in a default mapping of:

 do_configure calls autotools_do_configure

since it allows a user to call into autotools_do_configure from a custom
do_configure but I can't see the value of the intermediary
gnomebase_do_configure. Does anyone know of a use for it?

I have a suspicion that if it ever did do anything useful, it stopped
being useful long ago.

I'm therefore strongly tempted to remove the intermediaries from the
code. This would result in list B below which is a more direct set of
mappings.

Any thoughts/comments from anyone?

Cheers,

Richard

List A:
 autotools_do_siteconfig calls siteconfig_do_siteconfig
 autotools_do_siteconfig_gencache calls siteconfig_do_siteconfig_gencache
 base_do_patch calls patch_do_patch
 cmake_do_configure calls autotools_do_configure
 cmake_do_install calls autotools_do_install
 core-image_do_rootfs calls image_do_rootfs
 core-image_make_zimage_symlink_relative calls image_make_zimage_symlink_relative
 core-image_remove_init_link calls image_remove_init_link
 core-image_rootfs_no_x_startup calls image_rootfs_no_x_startup
 core-image_rootfs_update_timestamp calls image_rootfs_update_timestamp
 core-image_set_image_autologin calls image_set_image_autologin
 core-image_zap_root_password calls image_zap_root_password
 do_compile calls base_do_compile
 do_compile calls cmake_do_compile
 do_compile calls cpan_do_compile
 do_compile calls distutils_do_compile
 do_compile calls kernel_do_compile
 do_compile calls module_do_compile
 do_compile calls setuptools_do_compile
 do_configure calls autotools_do_configure
 do_configure calls base_do_configure
 do_configure calls cmake_do_configure
 do_configure calls cml1_do_configure
 do_configure calls cpan_do_configure
 do_configure calls gnomebase_do_configure
 do_configure calls kernel_do_configure
 do_configure calls qmake2_do_configure
 do_configure calls qmake_base_do_configure
 do_deploy calls kernel_do_deploy
 do_fetch calls base_do_fetch
 do_generate_toolchain_file calls cmake_do_generate_toolchain_file
 do_install calls autotools_do_install
 do_install calls base_do_install
 do_install calls cmake_do_install
 do_install calls cpan_do_install
 do_install calls distutils_do_install
 do_install calls gnomebase_do_install
 do_install calls kernel_do_install
 do_install calls module_do_install
 do_install calls setuptools_do_install
 do_package calls base_do_package
 do_patch calls base_do_patch
 do_siteconfig calls autotools_do_siteconfig
 do_siteconfig_gencache calls autotools_do_siteconfig_gencache
 do_unpack calls base_do_unpack
 gnomebase_do_configure calls autotools_do_configure
 gnomebase_do_install calls autotools_do_install
 package_name_hook calls debian_package_name_hook
 qmake2_do_configure calls qmake_base_do_configure
 setuptools_do_compile calls distutils_do_compile
 setuptools_do_install calls distutils_do_install


List B:
 do_compile calls base_do_compile
 do_compile calls cmake_do_compile
 do_compile calls cpan_do_compile
 do_compile calls distutils_do_compile
 do_compile calls kernel_do_compile
 do_compile calls module_do_compile
 do_configure calls autotools_do_configure
 do_configure calls base_do_configure
 do_configure calls cmake_do_configure
 do_configure calls cml1_do_configure
 do_configure calls cpan_do_configure
 do_configure calls kernel_do_configure
 do_configure calls qmake_base_do_configure
 do_deploy calls kernel_do_deploy
 do_fetch calls base_do_fetch
 do_generate_toolchain_file calls cmake_do_generate_toolchain_file
 do_install calls autotools_do_install
 do_install calls base_do_install
 do_install calls cmake_do_install
 do_install calls cpan_do_install
 do_install calls distutils_do_install
 do_install calls kernel_do_install
 do_install calls module_do_install
 do_package calls base_do_package
 do_patch calls patch_do_patch
 do_siteconfig calls siteconfig_do_siteconfig
 do_siteconfig_gencache calls siteconfig_do_siteconfig_gencache
 do_unpack calls base_do_unpack
 package_name_hook calls debian_package_name_hook




             reply	other threads:[~2012-12-10 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 16:09 Richard Purdie [this message]
2012-12-10 17:29 ` EXPORT_FUNCTIONS - change in behaviour proposal Chris Larson
2012-12-10 17:29   ` [bitbake-devel] " Chris Larson
2012-12-10 17:44   ` Richard Purdie
2012-12-10 17:44     ` [bitbake-devel] " Richard Purdie
2012-12-10 19:41     ` Chris Larson
2012-12-10 19:41       ` [bitbake-devel] " Chris Larson
2012-12-11  0:12       ` Richard Purdie
2012-12-11  0:12         ` [bitbake-devel] " Richard Purdie

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=1355155747.29967.31.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.