Hi Josh,
OCPI_SYSTEM_CONFIG is optional and not really used yet.
I'm not sure where "example.cxx" is, but if you are thinking about
"hello.cxx",
the ContainerManager::find("rcc") requires that the rcc-container
"driver" be linked in to the executable.
It should be, according to the latest Makefile for the hello example,
which includes ocpisetup.mk, which mentions
this library.
On RHEL 5 (and MacOS), just mentioning the library (even with no
explicit external reference to it), causes it to be used by the
executable. I.e. "ldd hello" shows that librcc_container.so is indeed
loaded by the executable.
If you created example.cxx yourself, let's see the Makefile.
Jim
On 12/5/11 4:36 AM, Josh Sutton wrote:
Hi,
I have checked out the latest version of OpenCPI, but am having some
problems running the examples on Ubuntu.
The following code snippets seem to be the cuplrits:
example.cxx calls -
ContainerManager::find("rcc")
which calls, from OcpiContainerManager.cxx -
OCPI::API::Container *Manager::find(const char *model, const char *which,
const OA::PValue *props) {
parent().configureOnce();
which calls -
From OcpiDriverManager.cxx: ManagerManager:configureOnce()
if (!file)
file = getenv("OCPI_SYSTEM_CONFIG");
if (!file) {
file = "/opt/opencpi/platform.xml";
optional = true;
}
In each of the examples ContainerManager::find("rcc") returns a null pointer
It's failing because OCPI_SYSTEM_CONFIG is not defined, and
/opt/opencpi/platform.xml does not exist.
Any thoughts? Can anyone confirm that the current repository
examples run out of the box? Or alternatively suggest where
OCPI_SYSTEM_CONFIG or platform.xml can be found?
Cheers,
Josh
_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
