You can still follow the same procedure and make your master node (e.g., downloadmanager node) pass it's queryinterface downstream to the slave node (e.g., parser node) instead of the master node itself responding to the request.
-Ravi On Jan 11, 12:48 am, jeffb <[email protected]> wrote: > Ravi, > I think what GeorgeC is trying to say is that in a multi-node > pipeline, the query for the PVMFDataSourceNodeRegistryInitInterface is > not propagated beyond the initial source node. For example, while the > download manager implements the > PVMFDataSourceNodeRegistryInitInterface, it does not send a > queryInterface to a node that it creates from the registry, nor does > it send the setDataSourceNodeInitialization message to the created > node. This appears to prevent a parser node that is created by the > download manager from creating a node from the registry. Am I > overlooking something? Other than a parser node recreating the > registry, do you have a suggestion about how to get around this? > > Regards, > Jeff > > On Jan 8, 12:57 pm, RaviY <[email protected]> wrote: > > > If your node implements the interface > > "PVMF_DATA_SOURCE_NODE_REGISRTY_INIT_INTERFACE_UUID" (class > > PVMFDataSourceNodeRegistryInitInterface), then even your node will be > > given access to iPlayerNodeRegistry. > > > -Ravi > > > On Jan 7, 2:49 am, George C <[email protected]> wrote: > > > > Ravi, > > > > Thanks for your replay. Related to external access subject: if I need > > > to create dynamically (during execution) a node (such as a parser > > > node) I need to have access to iPlayerNodeRegistry->CreateNode(..). I > > > noticed that the access to the iPlayerNodeRegistry is given only to > > > DownloadManagerNode via iSourceNodeRegInitIF->SetPlayerNodeRegistry > > > (..). How could I have access to the iPlayerNodeRegistry from a node > > > that is not a DownloadManagerNode? > > > One cumbersome way to solve this issue would be to create my own > > > registry and all the necessary functions to populate it with nodes > > > and recognizers, in other words to duplicate the implementation from > > > the player engine. > > > > George > > > > On Dec 15 2009, 10:53 pm, RaviY <[email protected]> wrote: > > > > > In any given shared library, only a few symbols are visible > > > > externally. These symbols are marked with OSCL_IMPORT_REF/ > > > > OSCL_EXPORT_REF. So, you should check if the function that you are > > > > referencing is being exported or not. > > > > > -Ravi > > > > > On Dec 16, 5:28 am, George C <[email protected]> wrote: > > > > > > Ravi, > > > > > > I also have abuild related problem. I am trying to add a new node > > > > > where I use someexternalclass methods already defined in an existing > > > > > OpenCore node (more exactly in ProtocolEngineNode). The compile phase > > > > > works fine but I got link errors: "undefined reference". For some > > > > > reasons the linker is unable to find its implementation. Do you have > > > > > any suggestion? > > > > > > Thanks, > > > > > > George > > > > > > On Dec 4, 9:50 am, RaviY <[email protected]> wrote: > > > > > > > I agree. It is kind of confusing for folks building OpenCORE outside > > > > > > of Android to modify the pv_config* files. I can help you hack it up > > > > > > for your use. > > > > > > > You can do the following things in build_config/opencore_dynamic/ > > > > > > makefile before the line "include $(MK)/cml2_shared.mk" ... > > > > > > - To add a new shared library libxyz.so that comprises of two static > > > > > > libraries libstatic1.a and libstatic2.a. > > > > > > SOLIBDIRS_xyz := "/path/to/libstatic1 /path/to/libstatic2" > > > > > > SOLIBS_xyz := "-lstatic1 -lstatic2" > > > > > > E.g. When one wants to add a new dynamically loadable parser node. > > > > > > > - To add a new static library libstatic3.a into an existing shared > > > > > > library libpqr.so. > > > > > > SOLIBDIRS_pqr := $(SOLIBDIRS_pqr) "/path/to/libstatic3" > > > > > > SOLIBS_pqr := $(SOLIBS_pqr) "-lstatic3" > > > > > > E.g. When one wants to add a new parser node to be linked statically > > > > > > with libopencore_player.so. > > > > > > > Hope this helps. > > > > > > -Ravi > > > > > > > On Dec 4, 7:41 pm, jeffb <[email protected]> wrote:> Can anyone > > > > > > help me? > > > > > > > > On Dec 2, 9:44 am, jeffb <[email protected]> wrote: > > > > > > > > > I have a new parser node and recognizer node. I am trying > > > > > > > > tobuild > > > > > > > > open core outside android. I have followed the quickstart > > > > > > > > tutorial > > > > > > > > which is in opencore directory. When I follow these > > > > > > > > instructions, it > > > > > > > > does not recognize that I have added parser node and recognizer > > > > > > > > node > > > > > > > > directories. I have included make files similar to the ones for > > > > > > > > MP4 > > > > > > > > parser and recognizer nodes within these new directories. > > > > > > > > > What do I need to do to make thebuildsystem recognize these new > > > > > > > > directories and automatically generate the necessary > > > > > > > > pv_config.h, > > > > > > > > rules.cml, sybols.cml, pv_config_derived.mk, > > > > > > > > pv_config_selected.mk, > > > > > > > > and make files within build_config/opencore_dynamic? > >
-- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
