improve virtual package infra
cover improve virtual package infra
This patch series, intended for the -next branch, improves virtual package infrastructure by:
- using make control functions in dependency check.
- adding a tutorial to the user manual.
Best regards,
ELB
Eric Le Bihan (2):
infra: improve dependency check in virtual packages.
manual: add virtual package tutorial.
docs/manual/adding-packages-virtual.txt | 102 ++++++++++++++++++++++++++++++ docs/manual/adding-packages.txt | 2 + package/luainterpreter/luainterpreter.mk | 6 ++ package/opengl/libegl/libegl.mk | 7 +- package/opengl/libgles/libgles.mk | 7 +- package/opengl/libopenmax/libopenmax.mk | 7 +- package/opengl/libopenvg/libopenvg.mk | 7 +- package/powervr/powervr.mk | 7 +- 8 files changed, 125 insertions(+), 20 deletions(-) create mode 100644 docs/manual/adding-packages-virtual.txt
--
1.7.9.5
PATCH 1/2 infra: improve dependency check in virtual packages.
The current version of dependency check for virtual package <foo> defines FOO_CONFIGURE_CMDS to print an error message if the dependencies are not met.
This patch updates all the virtual packages to use the GNU Make control function $(error text...) instead.
This makes the error happen at the beginning of the build, with a clearer message.
--- package/luainterpreter/luainterpreter.mk | 6 ++++++ package/opengl/libegl/libegl.mk | 7 +++---- package/opengl/libgles/libgles.mk | 7 +++---- package/opengl/libopenmax/libopenmax.mk | 7 +++---- package/opengl/libopenvg/libopenvg.mk | 7 +++---- package/powervr/powervr.mk | 7 +++---- 6 files changed, 21 insertions(+), 20 deletions(-)
package/luainterpreter/luainterpreter.mk +6 -0
@@ -9,4 +9,10 @@ LUAINTERPRETER_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_LUA_INTERPRET LUAINTERPRETER_ABIVER = $(call qstrip,$(BR2_PACKAGE_LUAINTERPRETER_ABI_VERSION)) +ifeq ($(BR2_PACKAGE_HAS_LUA_INTERPRETER),y) +ifeq ($(LUAINTERPRETER_DEPENDENCIES),) +$(error No lua interpreter implementation selected. Configuration error.) +endif +endif + $(eval $(generic-package))
package/opengl/libegl/libegl.mk +3 -4
@@ -7,11 +7,10 @@ LIBEGL_SOURCE = LIBEGL_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_OPENGL_EGL)) +ifeq ($(BR2_PACKAGE_HAS_OPENGL_EGL),y) ifeq ($(LIBEGL_DEPENDENCIES),) -define LIBEGL_CONFIGURE_CMDS - echo "No libEGL implementation selected. Configuration error." - exit 1 -endef +$(error No libEGL implementation selected. Configuration error.) +endif endif $(eval $(generic-package))
package/opengl/libgles/libgles.mk +3 -4
@@ -7,11 +7,10 @@ LIBGLES_SOURCE = LIBGLES_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_OPENGL_ES)) +ifeq ($(BR2_PACKAGE_HAS_OPENGL_ES),y) ifeq ($(LIBGLES_DEPENDENCIES),) -define LIBGLES_CONFIGURE_CMDS - echo "No libGLES implementation selected. Configuration error." - exit 1 -endef +$(error No libGLES implementation selected. Configuration error.) +endif endif $(eval $(generic-package))
package/opengl/libopenmax/libopenmax.mk +3 -4
@@ -7,11 +7,10 @@ LIBOPENMAX_SOURCE = LIBOPENMAX_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_OPENMAX)) +ifeq ($(BR2_PACKAGE_HAS_OPENMAX),y) ifeq ($(LIBOPENMAX_DEPENDENCIES),) -define LIBOPENMAX_CONFIGURE_CMDS - echo "No libopenmax implementation selected. Configuration error." - exit 1 -endef +$(error No libopenmax implementation selected. Configuration error.) +endif endif $(eval $(generic-package))
package/opengl/libopenvg/libopenvg.mk +3 -4
@@ -7,11 +7,10 @@ LIBOPENVG_SOURCE = LIBOPENVG_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_OPENVG)) +ifeq ($(BR2_PACKAGE_HAS_OPENVG),y) ifeq ($(LIBOPENVG_DEPENDENCIES),) -define LIBOPENVG_CONFIGURE_CMDS - echo "No libOpenVG implementation selected. Configuration error." - exit 1 -endef +$(error No libOpenVG implementation selected. Configuration error.) +endif endif $(eval $(generic-package))
package/powervr/powervr.mk +3 -4
@@ -7,11 +7,10 @@ POWERVR_SOURCE = POWERVR_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_POWERVR)) +ifeq ($(BR2_PACKAGE_HAS_POWERVR),y) ifeq ($(POWERVR_DEPENDENCIES),) -define POWERVR_CONFIGURE_CMDS - echo "No PowerVR implementation selected. Configuration error." - exit 1 -endef +$(error No PowerVR implementation selected. Configuration error.) +endif endif $(eval $(generic-package))
Signature · 1 line
1.7.9.5
PATCH 1/2 infra: improve dependency check in virtual packages.
Eric, All,
On 2014-02-24 10:50 +0100, Eric Le Bihan spake thusly:
Quoted 11 lines
The current version of dependency check for virtual package <foo> defines
FOO_CONFIGURE_CMDSto print an error message if the dependencies are not met.This patch updates all the virtual packages to use the GNU Make control function $(error text...) instead.
This makes the error happen at the beginning of the build, with a clearer message.
Signed-off-by Eric Le Bihan <[email protected]>
Somewhat-unrelated to this change, see a comment below...
Quoted 33 lines
--- package/luainterpreter/luainterpreter.mk | 6 ++++++ package/opengl/libegl/libegl.mk | 7 +++---- package/opengl/libgles/libgles.mk | 7 +++---- package/opengl/libopenmax/libopenmax.mk | 7 +++---- package/opengl/libopenvg/libopenvg.mk | 7 +++---- package/powervr/powervr.mk | 7 +++---- 6 files changed, 21 insertions(+), 20 deletions(-)package/luainterpreter/luainterpreter.mk +6
-0@@ -9,4 +9,10 @@ LUAINTERPRETER_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_LUA_INTERPRET LUAINTERPRETER_ABIVER = $(call qstrip,$(BR2_PACKAGE_LUAINTERPRETER_ABI_VERSION)) +ifeq ($(BR2_PACKAGE_HAS_LUA_INTERPRETER),y) +ifeq ($(LUAINTERPRETER_DEPENDENCIES),) +$(error No lua interpreter implementation selected. Configuration error.) +endif +endif + $(eval $(generic-package))package/opengl/libegl/libegl.mk +1
-0@@ -7,11 +7,10 @@ LIBEGL_SOURCE = LIBEGL_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_OPENGL_EGL)) +ifeq ($(BR2_PACKAGE_HAS_OPENGL_EGL),y)
package/opengl/libegl/libegl.mk line 16
Quoted 10 lines
package/opengl/libegl/libegl.mk +2
-4ifeq ($(LIBEGL_DEPENDENCIES),) -define LIBEGL_CONFIGURE_CMDS - echo "No libEGL implementation selected. Configuration error." - exit 1 -endef +$(error No libEGL implementation selected. Configuration error.) +endif endif $(eval $(generic-package))
I don't know about you folks, but I'm beginning to see a pattern here...
If all of our BR2_PACKAGE_HAS_FOOBAR options would match the corresponding FOOBAR_DEPENDENCIES, then we could use something like (absolutely untested, only pure random thoughts):
$(eval $(call virtual-package,FooBar))
whith 'virtual-package' something like:
define virtual-package
ifeq ($(BR2_PACKAGE_HAS_$(call upper,$(1))),y)
ifeq ($($(call upper,$(1))_DEPENDENCIES),)
$(error No $(1) implementation selected. Configuration error.)
endif
endif
endefBut then we would need:
s/BR2_PACKAGE_HAS_OPENGL_EGL/BR2_PACKAGE_HAS_LIBEGL/ s/BR2_PACKAGE_HAS_OPENGL_GLES/BR2_PACKAGE_HAS_LIBGLES/ s/BR2_PACKAGE_HAS_OPENMAX/BR2_PACKAGE_HAS_LIBOPENMAX/ s/BR2_PACKAGE_HAS_OPENVG/BR2_PACKAGE_HAS_LIBOPENVG/
Lua interpreter and PowerVR already match this.
We could even go further, so as to only require a call to 'virtual-package' and not to 'generic-package', with some carefully-crafted Makefile constructs (but we would loose the capitalisation of eg. lbEGL, since the package is named 'libegl', all in lower-case). 'virtual-package' could even override FOOBAR_SOURCE="" before calling generic-package behind the hood. This would make writing virtual packages even easier.
Thought?
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/2 infra: improve dependency check in virtual packages.
Quoted 99 lines · On Mon, 24 Feb 2014 19:29:51 +0100 "Yann E. MORIN" <[email protected]>…
Eric, All,
On 2014-02-24 10:50 +0100, Eric Le Bihan spake thusly:
Quoted 11 lines
The current version of dependency check for virtual package <foo> defines
FOO_CONFIGURE_CMDSto print an error message if the dependencies are not met.This patch updates all the virtual packages to use the GNU Make control function $(error text...) instead.
This makes the error happen at the beginning of the build, with a clearer message.
Signed-off-by Eric Le Bihan <[email protected]>Reviewed-by "Yann E. MORIN" <[email protected]>Somewhat-unrelated to this change, see a comment below...
Quoted 37 lines
--- package/luainterpreter/luainterpreter.mk | 6 ++++++ package/opengl/libegl/libegl.mk | 7 +++---- package/opengl/libgles/libgles.mk | 7 +++---- package/opengl/libopenmax/libopenmax.mk | 7 +++---- package/opengl/libopenvg/libopenvg.mk | 7 +++---- package/powervr/powervr.mk | 7 +++---- 6 files changed, 21 insertions(+), 20 deletions(-)(quoted diff) +0
-0
b/package/luainterpreter/luainterpreter.mkindex c37d621..5443477 100644 ---a/package/luainterpreter/luainterpreter.mk+++b/package/luainterpreter/luainterpreter.mk(quoted diff) +0
-0@@ -9,4 +9,10 @@ LUAINTERPRETER_DEPENDENCIES = $(callqstrip,$(BR2_PACKAGE_PROVIDES_LUA_INTERPRET
LUAINTERPRETER_ABIVER= $(call
qstrip,$(BR2_PACKAGE_LUAINTERPRETER_ABI_VERSION))package/luainterpreter/luainterpreter.mk +3
-0+ifeq ($(BR2_PACKAGE_HAS_LUA_INTERPRETER),y) +ifeq ($(LUAINTERPRETER_DEPENDENCIES),) +$(error No lua interpreter implementation selected. Configurationerror.) +endif
package/luainterpreter/luainterpreter.mk +2
-0+endif + $(eval $(generic-package))(quoted diff) +0
-0
b/package/opengl/libegl/libegl.mkindex b2b74f1..3311e50 100644package/opengl/libegl/libegl.mk +1
-2@@ -7,11 +7,10 @@ LIBEGL_SOURCE = LIBEGL_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_OPENGL_EGL)) +ifeq ($(BR2_PACKAGE_HAS_OPENGL_EGL),y) ifeq ($(LIBEGL_DEPENDENCIES),) -define LIBEGL_CONFIGURE_CMDS - echo "No libEGL implementation selected. Configurationerror."
package/opengl/libegl/libegl.mk line 16
Quoted 7 lines
package/opengl/libegl/libegl.mk +2
-2- exit 1 -endef +$(error No libEGL implementation selected. Configuration error.) +endif endif $(eval $(generic-package))I don't know about you folks, but I'm beginning to see a pattern here...
If all of our
BR2_PACKAGE_HAS_FOOBARoptions would match the correspondingFOOBAR_DEPENDENCIES, then we could use something like (absolutely untested, only pure random thoughts):$(eval $(call virtual-package,FooBar))whith 'virtual-package' something like:
define virtual-package ifeq ($(BR2_PACKAGE_HAS_$(call upper,$(1))),y) ifeq ($($(call upper,$(1))_DEPENDENCIES),) $(error No $(1) implementation selected. Configuration error.) endif endif endefBut then we would need:
s/BR2_PACKAGE_HAS_OPENGL_EGL/BR2_PACKAGE_HAS_LIBEGL/ s/BR2_PACKAGE_HAS_OPENGL_GLES/BR2_PACKAGE_HAS_LIBGLES/ s/BR2_PACKAGE_HAS_OPENMAX/BR2_PACKAGE_HAS_LIBOPENMAX/ s/BR2_PACKAGE_HAS_OPENVG/BR2_PACKAGE_HAS_LIBOPENVG/Lua interpreter and PowerVR already match this.
We could even go further, so as to only require a call to 'virtual-package' and not to 'generic-package', with some carefully-crafted
Makefileconstructs (but we would loose the capitalisation of eg. lbEGL, since the package is named 'libegl', all in lower-case). 'virtual-package' could even override FOOBAR_SOURCE="" before calling generic-package behind the hood. This would make writing virtual packages even easier.
Quoted 2 lines
Thought?
Sounds good to me.
(The first suggestion, without the lost capitalization.)
Mike
Quoted 3 lines
Regards,
Yann E. MORIN.
PATCH 1/2 infra: improve dependency check in virtual packages.
In reply to Yann E. MORIN"Yann E. MORIN" <[email protected]> schreef:
...
Quoted 19 lines
I don't know about you folks, but I'm beginning to see a pattern here...
If all of our
BR2_PACKAGE_HAS_FOOBARoptions would match the correspondingFOOBAR_DEPENDENCIES, then we could use something like (absolutely untested, only pure random thoughts):$(eval $(call virtual-package,FooBar))whith 'virtual-package' something like:
define virtual-package ifeq ($(BR2_PACKAGE_HAS_$(call upper,$(1))),y) ifeq ($($(call upper,$(1))_DEPENDENCIES),) $(error No $(1) implementation selected. Configuration error.) endif endif endef
Quoted 7 lines
But then we would need:
s/BR2_PACKAGE_HAS_OPENGL_EGL/BR2_PACKAGE_HAS_LIBEGL/ s/BR2_PACKAGE_HAS_OPENGL_GLES/BR2_PACKAGE_HAS_LIBGLES/ s/BR2_PACKAGE_HAS_OPENMAX/BR2_PACKAGE_HAS_LIBOPENMAX/ s/BR2_PACKAGE_HAS_OPENVG/BR2_PACKAGE_HAS_LIBOPENVG/Lua interpreter and PowerVR already match this.
In the past I complained about the version of virtual packages (like toolchain) being 'undefined'. The idea came up to set it as 'virtual' instead. I believe at that time, Thomas also said that renaming the libgl symbols should be fine...
Best regards,
Thomas
PATCH 1/2 infra: improve dependency check in virtual packages.
In reply to Yann E. MORINHi!
On Mon, Feb 24, 2014 at 07:29:51PM +0100, Yann E. MORIN wrote:
[...]
Quoted 18 lines
I don't know about you folks, but I'm beginning to see a pattern here...
If all of our
BR2_PACKAGE_HAS_FOOBARoptions would match the correspondingFOOBAR_DEPENDENCIES, then we could use something like (absolutely untested, only pure random thoughts):$(eval $(call virtual-package,FooBar))whith 'virtual-package' something like:
define virtual-package ifeq ($(BR2_PACKAGE_HAS_$(call upper,$(1))),y) ifeq ($($(call upper,$(1))_DEPENDENCIES),) $(error No $(1) implementation selected. Configuration error.) endif endif endef
Quoted 5 lines
But then we would need:
s/BR2_PACKAGE_HAS_OPENGL_EGL/BR2_PACKAGE_HAS_LIBEGL/ s/BR2_PACKAGE_HAS_OPENGL_GLES/BR2_PACKAGE_HAS_LIBGLES/ s/BR2_PACKAGE_HAS_OPENMAX/BR2_PACKAGE_HAS_LIBOPENMAX/ s/BR2_PACKAGE_HAS_OPENVG/BR2_PACKAGE_HAS_LIBOPENVG/
IMHO, renaming BR2_PACKAGE_HAS_OPENGL_GLES to BR2_PACKAGE_HAS_LIBGLES and friends is OK, as it matches the mesa3d naming and sounds less redundant.
Quoted 10 lines
Lua interpreter and PowerVR already match this.
We could even go further, so as to only require a call to 'virtual-package' and not to 'generic-package', with some carefully-crafted
Makefileconstructs (but we would loose the capitalisation of eg. lbEGL, since the package is named 'libegl', all in lower-case). 'virtual-package' could even override FOOBAR_SOURCE="" before calling generic-package behind the hood. This would make writing virtual packages even easier.Thought?
I like the idea. The virtual packages would become one-liners :-) I'll test it.
Best regards,
ELB
PATCH 1/2 infra: improve dependency check in virtual packages.
Quoted 22 lines · Eric Le Bihan
Hi!
On Mon, Feb 24, 2014 at 07:29:51PM +0100, Yann E. MORIN wrote:
[...]Quoted 18 lines
I don't know about you folks, but I'm beginning to see a pattern here...
If all of our
BR2_PACKAGE_HAS_FOOBARoptions would match the correspondingFOOBAR_DEPENDENCIES, then we could use something like (absolutely untested, only pure random thoughts):$(eval $(call virtual-package,FooBar))whith 'virtual-package' something like:
define virtual-package ifeq ($(BR2_PACKAGE_HAS_$(call upper,$(1))),y) ifeq ($($(call upper,$(1))_DEPENDENCIES),) $(error No $(1) implementation selected. Configuration error.) endif endif endef
Quoted 15 lines
Quoted 5 lines
But then we would need:
s/BR2_PACKAGE_HAS_OPENGL_EGL/BR2_PACKAGE_HAS_LIBEGL/ s/BR2_PACKAGE_HAS_OPENGL_GLES/BR2_PACKAGE_HAS_LIBGLES/ s/BR2_PACKAGE_HAS_OPENMAX/BR2_PACKAGE_HAS_LIBOPENMAX/ s/BR2_PACKAGE_HAS_OPENVG/BR2_PACKAGE_HAS_LIBOPENVG/IMHO, renaming
BR2_PACKAGE_HAS_OPENGL_GLEStoBR2_PACKAGE_HAS_LIBGLESand friends is OK, as it matches the mesa3d naming and sounds less redundant.Quoted 8 lines
Lua interpreter and PowerVR already match this.
We could even go further, so as to only require a call to 'virtual-package' and not to 'generic-package', with some carefully-crafted
Makefileconstructs (but we would loose the capitalisation of eg. lbEGL, since the package is named 'libegl', all in lower-case). 'virtual-package' could even override FOOBAR_SOURCE="" before calling generic-package behind the hood. This would make writing virtual packages even easier.
Indeed, I alluded to this in my comments on one of the earlier versions
of Eric's patches.
In fact, you don't need to do a $(generic-package) at all. Nothing of
the generic package infrastructure is needed for virtual packages: no source fetching, no building and installing, no legal info, no nothing. Therefore also the stamp files are redundant. Therefore also the build directory is redundant. Therefore also the version is redundant.
The only thing we need is:
$(pkg): $($(PKG)_DEPENDENCIES)
We probably need a few more in order to propagate the other things that
need dependency chains, perhaps -source and -legal-info (though it looks like that is still done through the TARGETS_SOURCE variable - I thought we removed that at some point?).
Quoted 4 lines
Quoted 2 lines
Thought?
I like the idea. The virtual packages would become one-liners :-) I'll test it.
Make sure you do this on top of -next, because it may be affected by
Fabio's parallel build changes.
Regards,
Arnout
Quoted 9 lines
Best regards,
ELB
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
PATCH 2/2 manual: add virtual package tutorial.
In reply to Eric Le BihanThe manual now features a new section with instructions about how to add a virtual package.
--- docs/manual/adding-packages-virtual.txt | 102 +++++++++++++++++++++++++++++++ docs/manual/adding-packages.txt | 2 + 2 files changed, 104 insertions(+) create mode 100644 docs/manual/adding-packages-virtual.txt
docs/manual/adding-packages-virtual.txt new file +102 -0
@@ -0,0 +1,102 @@ +// -*- mode:doc; -*- +// vim: set syntax=asciidoc: + +Infrastructure for virtual packages +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +[[virtual-package-tutorial]] + ++virtual-package+ tutorial +^^^^^^^^^^^^^^^^^^^^^^^^^^ + +In Buildroot, a virtual package is a package whose functionalities are +provided by one or more packages, referred to as 'providers'. The virtual +package infrastructure is an extensible mechanism allowing the user to choose +the provider used in the rootfs. + +For example, 'OpenGL ES' is an API for 2D and 3D graphics on embedded systems. +The implementation of this API is different for the 'Allwinner Tech Sunxi' and +the 'Texas Instruments OMAP35xx' plaftorms. So +libgles+ will be a virtual +package and +sunxi-mali+ and +ti-gfx+ will be the providers. + +In the following example, we will explain how to add a new virtual package +('something-virtual') and a provider for it ('some-provider'). + +First, let's create the virtual package. + +.Virtual package +Config.in+ file +================================= +The +Config.in+ file of virtual package 'something-virtual' should contain: + +--------------------------- +01: config BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +02: bool +03: +04: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +05: depends on BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +06: string +--------------------------- +================================= + +In this file, we declare two options, +BR2_PACKAGE_HAS_SOMETHING_VIRTUAL+ and ++BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL+, whose values will be used by the +providers. + +.Virtual package +*.mk+ file +============================ +The Makefile +package/something-virtual/something-virtual.mk+ should contain: + +--------------------------- +01: ################################################################################ +02: # +03: # something-virtual +04: # +05: ################################################################################ +06: +07: SOMETHING_VIRTUAL_SOURCE = +08: SOMETHING_VIRTUAL_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL)) +09: +10: ifeq ($(BR2_PACKAGE_HAS_SOMETHING_VIRTUAL),y) +11: ifeq ($(SOMETHING_VIRTUAL_DEPENDENCIES),) +12: $(error No something-virtual implementation selected. Configuration error.) +13: endif +14: endif +15: +16: $(eval $(generic-package)) +--------------------------- +============================ + +The Makefile is quite small as it will only check if a provider for the +virtual package has been selected. + +When adding a package as a provider, only the +Config.in+ file requires some +modifications. The +*.mk+ file should follow the Buildroot infrastructure with +no change at all. + +.Provider +Config.in+ file +========================== +The +Config.in+ file of the package 'some-provider', which provides the +functionalities of 'something-virtual', should contain: + +--------------------------- +01: config BR2_PACKAGE_SOME_PROVIDER +02: bool "some-provider" +03: select BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +04: help +05: This is a comment that explains what some-provider is. +06: +07: http://foosoftware.org/some-provider/ +08: +09: if BR2_PACKAGE_SOME_PROVIDER +10: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +11: default "some-provider" +12: endif +--------------------------- +========================== + +On line 3, we select +BR2_PACKAGE_HAS_SOMETHING_VIRTUAL+, and on line 11, we +set the value of +BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL+ to the name of the +provider, but only if it is selected. + +Of course, do not forget to add the proper build and runtime dependencies for +this package!
docs/manual/adding-packages.txt +2 -0
@@ -24,6 +24,8 @@ include::adding-packages-luarocks.txt[] include::adding-packages-perl.txt[] +include::adding-packages-virtual.txt[] + include::adding-packages-hooks.txt[] include::adding-packages-gettext.txt[]
Signature · 1 line
1.7.9.5
PATCH 2/2 manual: add virtual package tutorial.
Eric, All,
I think you should base this on master, since we think it would be very interesting to have it in this release.
On 2014-02-24 10:50 +0100, Eric Le Bihan spake thusly:
Quoted 16 lines
The manual now features a new section with instructions about how to add a virtual package.
Signed-off-by Eric Le Bihan <[email protected]>--- docs/manual/adding-packages-virtual.txt | 102 +++++++++++++++++++++++++++++++ docs/manual/adding-packages.txt | 2 + 2 files changed, 104 insertions(+) create mode 100644 docs/manual/adding-packages-virtual.txtdocs/manual/adding-packages-virtual.txt new file +0
-0
docs/manual/adding-packages-virtual.txt line 10
Quoted 10 lines
docs/manual/adding-packages-virtual.txt new file +10
-0@@ -0,0 +1,102 @@ +// -*- mode:doc; -*- +// vim: set syntax=asciidoc: + +Infrastructure for virtual packages +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +[[virtual-package-tutorial]] + ++virtual-package+ tutorial +^^^^^^^^^^^^^^^^^^^^^^^^^^
'virtual-package' is not an infrastructure [ie. you can't use:
$(eval $(virtual-package)) ], so I would suggest to just use:
Virtual package tutorial
^^^^^^^^^^^^^^^^^^^^^^^^
[--SNIP--]
docs/manual/adding-packages-virtual.txt line 28
Quoted 4 lines
docs/manual/adding-packages-virtual.txt new file +4
-0+First, let's create the virtual package. + +.Virtual package +Config.in+ file +=================================
The formatting of the title is weird. Here's what I've changed:
Virtual package +Config.in+ file
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(notice: no leading dot, and an empty line after the ^^^ line)
docs/manual/adding-packages-virtual.txt line 39
Quoted 11 lines
docs/manual/adding-packages-virtual.txt new file +11
-0+The +Config.in+ file of virtual package 'something-virtual' should contain: + +--------------------------- +01: config BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +02: bool +03: +04: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +05: depends on BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +06: string +--------------------------- +=================================
Remove this === line.
docs/manual/adding-packages-virtual.txt line 46
Quoted 6 lines
docs/manual/adding-packages-virtual.txt new file +6
-0+In this file, we declare two options, +BR2_PACKAGE_HAS_SOMETHING_VIRTUAL+ and ++BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL+, whose values will be used by the +providers. + +.Virtual package +*.mk+ file +============================
Ditto title.
Quoted 11 lines
docs/manual/adding-packages-virtual.txt new file +11
-0+The Makefile +package/something-virtual/something-virtual.mk+ should contain: + +--------------------------- +01: ################################################################################ +02: # +03: # something-virtual +04: # +05: ################################################################################ +06: +07: SOMETHING_VIRTUAL_SOURCE = +08: SOMETHING_VIRTUAL_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL))
docs/manual/adding-packages-virtual.txt line 67
Quoted 10 lines
docs/manual/adding-packages-virtual.txt new file +10
-0+09: +10: ifeq ($(BR2_PACKAGE_HAS_SOMETHING_VIRTUAL),y) +11: ifeq ($(SOMETHING_VIRTUAL_DEPENDENCIES),) +12: $(error No something-virtual implementation selected. Configuration error.) +13: endif +14: endif +15: +16: $(eval $(generic-package)) +--------------------------- +============================
Ditto ===.
docs/manual/adding-packages-virtual.txt line 77
Quoted 9 lines
docs/manual/adding-packages-virtual.txt new file +9
-0+The Makefile is quite small as it will only check if a provider for the +virtual package has been selected. + +When adding a package as a provider, only the +Config.in+ file requires some +modifications. The +*.mk+ file should follow the Buildroot infrastructure with +no change at all. + +.Provider +Config.in+ file +==========================
Ditto title.
Quoted 8 lines
docs/manual/adding-packages-virtual.txt new file +8
-0+The +Config.in+ file of the package 'some-provider', which provides the +functionalities of 'something-virtual', should contain: + +--------------------------- +01: config BR2_PACKAGE_SOME_PROVIDER +02: bool "some-provider" +03: select BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +04: help
docs/manual/adding-packages-virtual.txt line 95
Quoted 10 lines
docs/manual/adding-packages-virtual.txt new file +10
-0+05: This is a comment that explains what some-provider is. +06: +07: http://foosoftware.org/some-provider/ +08: +09: if BR2_PACKAGE_SOME_PROVIDER +10: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +11: default "some-provider" +12: endif +--------------------------- +==========================
Ditto ===.
With those changes, the manual looks better, IMHO.
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 2/2 manual: add virtual package tutorial.
Quoted 7 lines · Yann E. MORIN
'virtual-package' is not an infrastructure [ie. you can't use:
$(eval $(virtual-package)) ], so I would suggest to just use:Virtual package tutorial
^^^^^^^^^^^^^^^^^^^^^^^^
Understood.
Quoted 7 lines
docs/manual/adding-packages-virtual.txt line 28
Quoted 4 lines
docs/manual/adding-packages-virtual.txt new file +4
-0+First, let's create the virtual package. + +.Virtual package +Config.in+ file +=================================The formatting of the title is weird. Here's what I've changed:
Quoted 5 lines
Virtual package +Config.in+ file
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^(notice: no leading dot, and an empty line after the ^^^ line)
This was not a title, but an example, as I used +adding-packages-generic.txt+ for inspiration. I thought it was useful to have the code snippets listed in the example section, so the user could quickly jump to them. But it is true that:
1. not all the code snippets are listed as examples.
2. the Ascidoc example syntax, mixed with a code snippet, hurts the eyes (either in text or in the generated HTML).
I'll change to plain and simple titles.
Best regards,
ELB
PATCH 2/2 manual: add virtual package tutorial.
In reply to Yann E. MORINQuoted 4 lines · Yann E. MORIN
Eric, All,
I think you should base this on master, since we think it would be very interesting to have it in this release.
I don't think it's that important. I don't think people will be adding
virtual packages for their custom stuff, so this documentation is targeted towards people that will upstream packages. And for these, we can assume that they read the documentation of master and not that of whatever release they happen to be working with.
And of course, if the $(virtual-package) infrastructure gets added, then
this piece of documentation has to be entirely rewritten.
Quoted 23 lines
On 2014-02-24 10:50 +0100, Eric Le Bihan spake thusly:
Quoted 21 lines
The manual now features a new section with instructions about how to add a virtual package.
Signed-off-by Eric Le Bihan <[email protected]>--- docs/manual/adding-packages-virtual.txt | 102 +++++++++++++++++++++++++++++++ docs/manual/adding-packages.txt | 2 + 2 files changed, 104 insertions(+) create mode 100644 docs/manual/adding-packages-virtual.txtdocs/manual/adding-packages-virtual.txt new file +5
-0@@ -0,0 +1,102 @@ +// -*- mode:doc; -*- +// vim: set syntax=asciidoc: + +Infrastructure for virtual packages +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Quoted 8 lines
docs/manual/adding-packages-virtual.txt line 10
Quoted 5 lines
docs/manual/adding-packages-virtual.txt new file +5
-0+ +[[virtual-package-tutorial]] + ++virtual-package+ tutorial +^^^^^^^^^^^^^^^^^^^^^^^^^^'virtual-package' is not an infrastructure [ie. you can't use:
$(eval $(virtual-package)) ],
Well, soon you will be able to! :-)
Regards,
Arnout
Quoted 104 lines
so I would suggest to just use:
Virtual package tutorial
^^^^^^^^^^^^^^^^^^^^^^^^[--SNIP--]
docs/manual/adding-packages-virtual.txt line 28
Quoted 4 lines
docs/manual/adding-packages-virtual.txt new file +4
-0+First, let's create the virtual package. + +.Virtual package +Config.in+ file +=================================The formatting of the title is weird. Here's what I've changed:
Virtual package +Config.in+ file
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^(notice: no leading dot, and an empty line after the ^^^ line)
docs/manual/adding-packages-virtual.txt line 39
Quoted 11 lines
docs/manual/adding-packages-virtual.txt new file +11
-0+The +Config.in+ file of virtual package 'something-virtual' should contain: + +--------------------------- +01: config BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +02: bool +03: +04: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +05: depends on BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +06: string +--------------------------- +=================================Remove this === line.
docs/manual/adding-packages-virtual.txt line 46
Quoted 6 lines
docs/manual/adding-packages-virtual.txt new file +6
-0+In this file, we declare two options, +BR2_PACKAGE_HAS_SOMETHING_VIRTUAL+ and ++BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL+, whose values will be used by the +providers. + +.Virtual package +*.mk+ file +============================Ditto title.
Quoted 11 lines
docs/manual/adding-packages-virtual.txt new file +11
-0+The Makefile +package/something-virtual/something-virtual.mk+ should contain: + +--------------------------- +01: ################################################################################ +02: # +03: # something-virtual +04: # +05: ################################################################################ +06: +07: SOMETHING_VIRTUAL_SOURCE = +08: SOMETHING_VIRTUAL_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL))docs/manual/adding-packages-virtual.txt line 67
Quoted 10 lines
docs/manual/adding-packages-virtual.txt new file +10
-0+09: +10: ifeq ($(BR2_PACKAGE_HAS_SOMETHING_VIRTUAL),y) +11: ifeq ($(SOMETHING_VIRTUAL_DEPENDENCIES),) +12: $(error No something-virtual implementation selected. Configuration error.) +13: endif +14: endif +15: +16: $(eval $(generic-package)) +--------------------------- +============================Ditto ===.
docs/manual/adding-packages-virtual.txt line 77
Quoted 9 lines
docs/manual/adding-packages-virtual.txt new file +9
-0+The Makefile is quite small as it will only check if a provider for the +virtual package has been selected. + +When adding a package as a provider, only the +Config.in+ file requires some +modifications. The +*.mk+ file should follow the Buildroot infrastructure with +no change at all. + +.Provider +Config.in+ file +==========================Ditto title.
Quoted 8 lines
docs/manual/adding-packages-virtual.txt new file +8
-0+The +Config.in+ file of the package 'some-provider', which provides the +functionalities of 'something-virtual', should contain: + +--------------------------- +01: config BR2_PACKAGE_SOME_PROVIDER +02: bool "some-provider" +03: select BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +04: helpdocs/manual/adding-packages-virtual.txt line 95
Quoted 10 lines
docs/manual/adding-packages-virtual.txt new file +10
-0+05: This is a comment that explains what some-provider is. +06: +07: http://foosoftware.org/some-provider/ +08: +09: if BR2_PACKAGE_SOME_PROVIDER +10: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +11: default "some-provider" +12: endif +--------------------------- +==========================Ditto ===.
With those changes, the manual looks better, IMHO.
Regards,
Yann E. MORIN.
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F