• Advertisement
Sign in to follow this  

Use Assimp in Universal Windows App

This topic is 415 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Using the Directx12 Universal Windows App (template in vs2015) Assimo does not work. It gives me this error: 

"The program '[4312] application.exe' has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'."

Is there any way to make assimp work here?

thank you.

Share this post


Link to post
Share on other sites
Advertisement

Well, something is missing, or at least the computer thinks so. I don't know how, but I would think the magic numbers can tell you what it is not finding.

 

Fwiw, the dependency list of my libassimp is

$ ldd /usr/lib64/libassimp.so
        linux-vdso.so.1 (0x00007ffe91036000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fc669c0c000)
        libminizip.so.1 => /lib64/libminizip.so.1 (0x00007fc6699fc000)
        libIrrXML.so.1 => /lib64/libIrrXML.so.1 (0x00007fc6697e4000)
        libpoly2tri.so.1.0 => /lib64/libpoly2tri.so.1.0 (0x00007fc6695d4000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fc66924c000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fc668f3c000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fc668d24000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fc66895c000)
        libGL.so.1 => /lib64/libGL.so.1 (0x00007fc6686cc000)
        libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00007fc6684c4000)
        libjpeg.so.62 => /lib64/libjpeg.so.62 (0x00007fc668254000)
        libpng16.so.16 => /lib64/libpng16.so.16 (0x00007fc66801c000)
        libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fc667e0c000)
        libaesgm.so.0 => /lib64/libaesgm.so.0 (0x00007fc667bf4000)
        /lib64/ld-linux-x86-64.so.2 (0x000055e0e6224000)
        libGLX.so.0 => /lib64/libGLX.so.0 (0x00007fc6679bc000)
        libX11.so.6 => /lib64/libX11.so.6 (0x00007fc66767c000)
        libXext.so.6 => /lib64/libXext.so.6 (0x00007fc667464000)
        libGLdispatch.so.0 => /lib64/libGLdispatch.so.0 (0x00007fc6671ac000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fc666fa4000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fc666d84000)
        libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fc666b5c000)
        libXau.so.6 => /lib64/libXau.so.6 (0x00007fc666954000)

Likely windows has not all these, but eg libpng, libjpeg, libpthread, and a number of decompressing libraries seem likely.

Share this post


Link to post
Share on other sites

AFAIK Microsoft restricts subset of WinAPI for UWA.

For example, CreateFile() is for desktop applications only: look at "Requirements" section of this page:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa363858(v=vs.85).aspx

 

Here is a list of restrictions to C++ standard functions for UWA:

https://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh972425(v=vs.140).aspx

 

Not all MS dlls that are in desktop apps, may be used in UWA.

Probably Assimp uses subset of the banned API.

Edited by Happy SDE

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement