omxregister-bellagio(1) [debian man page]

OMXREGISTER-BELLAGIO(1) 					 OpenMAX Bellagio					   OMXREGISTER-BELLAGIO(1)

NAME

       omxregister-bellagio - register OpenMAX/Bellagio components

SYNOPSIS

       omxregister-bellagio [-v] [-h] [ componentspath ]...

DESCRIPTION

       Before using any OpenMAX component, they must be registered with the omxregister-bellagio command.

       By  default,  this  will  create  a  file  named  .omxregister  under  the  home XDG data directory with all the components found in ${lib-
       dir}/libomxil-bellagio0.

OPTIONS

       -v     Display a verbose output, listing all the components registered.

       -h     Display help.

       componentspath
	      Location of the OpenMAX/Bellagio components (by default ${libdir}/libomxil-bellagio0).  Multiple locations should  be  separated	by
	      colons

FILES

       $XDG_DATA_HOME/libomxil-bellagio/registry or $OMX_BELLAGIO_REGISTRY.
	      The OpenMAX/Bellagio component registry file.

ENVIRONMENT

       BELLAGIO_SEARCH_PATH
	      This variable can be set to indicate the location(s) of the components

       OMX_BELLAGIO_REGISTRY
	      Location of the registry.

       XDG_DATA_HOME
	      Location of the home data directory where registry is saved (if $OMX_BELLAGIO_REGISTRY is unset).

AUTHORS

       Bhattacharyya Sourya, Melpignano Diego, Niemimuukko Ukri, Sen Pankaj, Siorpaes David and Urlini Giulio.

       Man page written by Marc-Andre Lureau.

Bellagio							     Sept 2009						   OMXREGISTER-BELLAGIO(1)

wsreg_add_dependent_component(3WSREG)		    Product Install Registry Library Functions		     wsreg_add_dependent_component(3WSREG)

NAME

       wsreg_add_dependent_component, wsreg_remove_dependent_component, wsreg_get_dependent_components - add or remove a dependent component

SYNOPSIS

       cc [flag ...]  file ...-lwsreg [library ...]
       #include <wsreg.h>

       int wsreg_add_dependent_component(Wsreg_component *comp, const Wsreg_component *dependentComp);

       int wsreg_remove_dependent_component(Wsreg_component *comp, const Wsreg_component *dependentComp);

       Wsreg_component **wsreg_get_dependent_components(const Wsreg_component *comp);

DESCRIPTION

       The wsreg_add_dependent_component() function adds the component specified by dependentComp to the list of dependent components contained in
       the component specified by comp.

       The wsreg_remove_dependent_component() function removes the component specified by dependentComp from the list of dependent components con-
       tained in the component specified by comp.

       The wsreg_get_dependent_components() function returns the list of dependent components contained in the component specified by comp.

RETURN VALUES

       The  wsreg_add_dependent_component()  function returns a non-zero value if the specified dependent component was successfully added; other-
       wise, 0 is returned.

       The wsreg_remove_dependent_component() function returns a non-zero value if the specified dependent  component  was  successfully  removed;
       otherwise, 0 is returned.

       The  wsreg_get_dependent_components()  function	returns  a null-terminated array of Wsreg_component pointers that represents the specified
       component's list of dependent components.  If the specified component has no dependent components, NULL is returned.  The  resulting  array
       must be released by the caller through a call to wsreg_free_component_array(). See wsreg_create_component(3WSREG).

USAGE

       The  relationship  between two components in which one must be installed for the other to be complete is a dependent/required relationship.
       The component that is required by the other component is the required component.  The component that requires the other	is  the  dependent
       component.

       The  required  component must be installed and registered before the dependent component can be.  Uninstaller applications should check the
       registry before uninstalling and unregistering components so a successful uninstallation of one product will not result in another  product
       being compromised.

       Read access to the product install registry is required to use these functions because these relationships are held with lightweight compo-
       nent references that can only be fully resolved using the registry contents.

       The act of registering a component having required components results in the converse dependent relationships being  established  automati-
       cally.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |MT-Level		     |Unsafe			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       wsreg_add_required_component(3WSREG),	wsreg_can_access_registry(3WSREG),    wsreg_create_component(3WSREG),	 wsreg_initialize(3WSREG),
       wsreg_register(3WSREG), attributes(5)

SunOS 5.10							    22 Sep 2000 			     wsreg_add_dependent_component(3WSREG)