which corrade commit are you on?
ah, then you are about a month before mosra/corrade@e6f6538 which probably fixes this (in case you really are hitting the case of multiple instances of the same manager)
when you update, let me know if that fixed it for you
@mosra I might be using using namespace ..., I'll have to take a look.
Will Magnum build on centos 5.0? Looks like I have to make a centos build. Last time I had to use centos, it had some absolutely ancient versions of gcc, python 2.?... and you had to download RPM from various placed just to build anything.
@DaeMon87 great, this probably just means some dependency DLL is not found -- what corrade and magnum DLLs do you have next to your application executable?
i remember someone wanted me to do this a while ago, but when i saw the requirements i noped away out of that
https://github.com/pypa/manylinux i saw this
centos 6? ugh
it's funny, on one hand you have the modern c++ extremists who complain when your platform can't do full C++17
on the other hand you have these total compatibility extremists who force you to go back to the tech of 2010, abandoning even c++11
i used to have gcc 4.4 compatibility, but got rid of that in 2017 because that was an absolute maintenance nightmare
as far as i can see, centos 6 is gcc 4.4
gcc 4.8
some runtime lib missing, then?
@DaeMon87 can you open the StbTrueTypeFont.dll in the ol' Dependency Walker tool?
or alternatively in this one: https://github.com/lucasg/Dependencies
it will most probably lead to a crash
which one is it?
maybe the plugin dll is from a debug build?
usually debug plugins are in
magnum-d/ and release in magnum/, try to copy the release one instead if you have it
huh
seems like something fishy happened in the build :)