uniform OMX IL implementation

Hi,
From OMX IL spec, it seems that OMX core and OMX component are tied closey with each other. Suppose one has a set of OMX core and compatible OMX component. Now if he wants to integrate 3rd party OMX component (working in some other OMX core implementation) he has to do some modifications the that component. Also this is possible only if he has access to source code.
What could be the easiest solution to this? Bellagio is open source OMX IL implementation. Is it used widely across developers? or everybody has own proprietary implemenation?

Regards,
Viraj

I guess some previous posts discuss similar topic:

http://www.khronos.org/message_boards/viewtopic.php?f=7&t=962
http://www.khronos.org/message_boards/viewtopic.php?f=7&t=1201

Regards,
Viraj

The working group took the view that we could not mandate how components are dynamically discovered and loaded, as it is inherently platform-specific. We did mandate how staically linked components are exposed to the IL core.

The abscense of a mandated approach for dynamic discovery and loading does not prevent IL core and component implementers from giving the details of how to integrate their core / components with other components / cores. This would usually be required by platform integraters. At worst, this would allow stub components (that load the real components) to be registered with, and loaded by, the core. Obviously any component-core interaction outside the scope of the IL standard would be problematic.

Thanks,

Roger

Thanks for the reply Roger.

Regards,
Viraj