Attempting to port my code to collada-dom 2.4.2, I discovered that dae.open now always returns NULL. Looking at the code, it appears the issue happens here: domCOLLADAProxy* DAE::openCommon(const string& path, daeString buffer) { close(path); string uri = makeFullUri(path); plugin->setDatabase(database); if (plugin->read(daeURI(*this, uri.c_str()), buffer) != DAE_OK) return NULL; return getRoot(uri); } the return NULL in the if statement is being triggered. That appears to come from here: daeInt daeIOPluginCommon::read(const daeURI& uri, daeString docBuffer) { // Make sure topMeta has been set before proceeding if (topMeta == NULL) { return DAE_ERR_BACKEND_IO; } *snip* The topMeta variable should be populated by the owning DAE object at DAE::setIOPlugin on this line: int res = plugin->setMeta(getMeta(getDomCOLLADAID())); The nested getDomCOLLADAID call is to this code: daeInt getDomCOLLADAID(const char* specversion) { #ifdef COLLADA_DOM_SUPPORT150 if( specversion == NULL || strcmp(specversion,"1.5.0") == 0 ) { return ColladaDOM150::domCOLLADA::ID(); } #endif #ifdef COLLADA_DOM_SUPPORT141 if( specversion == NULL || strcmp(specversion,"1.4.1") == 0 ) { return ColladaDOM141::domCOLLADA::ID(); } #endif return NULL; } You'll note we expect a specversion argument but have none passed, so we'll always return the version 150 ID it seems.
Thanks for reporting. I could reproduce the bug. As you said it seems like getDomCOLLADAID() returns the wrong version and therefore, the initialization fails. I don't think this is a packaging bug. Could you report the bug upstream [1] ? I'll update once upstream fixed this. Also note that somebody already reported this bug on Sourceforge [2]. But since they switched to Github, reporting there would probably be a good idea. [1] https://github.com/rdiankov/collada-dom/issues [2] http://sourceforge.net/p/collada-dom/bugs/157/
This is now fixed upstream. https://github.com/rdiankov/collada-dom/commit/6706dd1ca292b22792b1066289e7e5ee21d5649a
collada-dom-2.4.3-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/collada-dom-2.4.3-1.fc20
Package collada-dom-2.4.3-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing collada-dom-2.4.3-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7182/collada-dom-2.4.3-1.fc20 then log in and leave karma (feedback).
collada-dom-2.4.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.