Re: [certi-dev] [SOLVED] Unable to create RTI ambassador

[Eric Noulard]

2011/9/13 Jan-Patrick Osterloh <address@hidden>:
> Hurrray!! Solved :-)

Nice to ear that.


> After some heavy debugging in DependencyWalker (I figured out a
> Profiling Method, which profiles the loading of dlls etc during runtime
> of an executable), I finally found the problem (by accident). X-Plane
> loads itself a lot of dlls. If a program has loaded a DLL, then it is
> not loaded again by another DLL in this program. Unfortunately, X-Plane
> found some DLLs in another path which are also needed by RTIA,

Do you have the list of those DLL?
RTIA shouldn't depend on much beside CERTI dlls and MSVCRT.dll?

May be we can build RTIA with some static lib (those which are in conflict)
in order to avoid such bug hunting safari.

> such they got loaded. And this DLLs where incompatible with RTIA, so it 
> crashed
> immediately when started. I solved the problem now, by adding all DLLs
> that are needed by RTIA into the CERTI/bin folder.

On unix we can use RPATH
http://www.vtk.org/Wiki/CMake_RPATH_handling
[see CERTI CMakeLists.txt option USE_FULL_RPATH]

to solve this DLL mismatch but apparently there is no such feature on windows:
http://stackoverflow.com/questions/107888/is-there-a-windows-msvc-equivalent-to-the-rpath-linker-flag

> Now it works fine. These problems could someone drive crazy.

I bet it does.

> Thanks a lot for your help!

You are welcome.
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org