Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Vladimír Vondruš
@mosra
i was actually thinking if i could drop gcc 4.8 support soon, hah ... good to know it's still very important :D
DaeMon87
@DaeMon87
@mosra
CorradePluginManager.dll
CorradeUtility.dll
Magnum.dll
MagnumDebugTools.dll
MagnumGL.dll
MagnumMeshTools.dll
MagnumPrimitives.dll
MagnumSceneGraph.dll
MagnumShaders.dll
MagnumText.dll
MagnumTextureTools.dll
MagnumTrade.dll
Vladimír Vondruš
@mosra
hm, that looks like everything is present
some runtime lib missing, then?
Andy Somogyi
@AndySomogyi
I'm going to take a look at a centos docker image, I've never used docker before, so it's all new to me.
Vladimír Vondruš
@mosra
too bad winapi is so shitty that it's not able to tell which DLL is missing
@DaeMon87 can you open the StbTrueTypeFont.dll in the ol' Dependency Walker tool?
or alternatively in this one: https://github.com/lucasg/Dependencies
DaeMon87
@DaeMon87
I tried that dependencies tool and 1 of the dlls its looking for is a debug one ill ad that to my executable folder
Vladimír Vondruš
@mosra
hmm that shouldn't be
it will most probably lead to a crash
which one is it?
maybe the plugin dll is from a debug build?
DaeMon87
@DaeMon87
MagnumText-d.dll
Vladimír Vondruš
@mosra
yeah that looks like the plugin is also a debug one
usually debug plugins are in magnum-d/ and release in magnum/, try to copy the release one instead if you have it
DaeMon87
@DaeMon87
I am only using release dlls, in the list from the dependencies tool thats the only debug dll referenced the other 3 are release dlls
Vladimír Vondruš
@mosra
yes but if it would be just release DLLs it wouldn't want MagnumText-d.dll
DaeMon87
@DaeMon87
interesting though when I open the debug dll for the plugin, its looking or MagnumText.dll while the other 3 are -d.dlls
Vladimír Vondruš
@mosra
MagnumText-d.dll would then want Magnum-d.dll and CorradeUtility-d.dll and ...
huh
seems like something fishy happened in the build :)
DaeMon87
@DaeMon87
maybe i switched the args in the cmake config
Vladimír Vondruš
@mosra
at this point i would just throw all binaries away and start over
DaeMon87
@DaeMon87
Ill give that a shot much thanx for the help
Vladimír Vondruš
@mosra
you're welcome, DLL hell is the worst
Tracy Ma
@linuxaged
sometimes Magnum C++ Docs online searching page loads quite slowly, i'm in China mainland.
Vladimír Vondruš
@mosra
the search data are huge, i need to figure out some better caching
Tracy Ma
@linuxaged
i guessed this may be a network problem, many websites are not accessable here 😔
Vladimír Vondruš
@mosra
i'm hosting this on a local cloud provider in central Europe, which should hopefully be not affected by any political or whatever whims like the US-centric ones are
and also hopefully small enough to be a target of some censorship effort
Vladimír Vondruš
@mosra
anybody using std::string_view?
Vladimír Vondruš
@mosra
asking so i know if i should provide conversion of it to corrade's StringView or if that can wait for later
Tracy Ma
@linuxaged
Corrade container is prefered in our magnum project, lightweight and cross-platform consistent
Janos95
@Janos95
i am using string view, but if corrade provides one I would just switch :)
none of the libraries i am using, uses std string views, so that's pretty easy.
Vladimír Vondruš
@mosra
image.png

An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days.

does github know something i don't?! :scream:

Janos95
@Janos95
haha thats pretty morbid
Konstantinos Chatzilygeroudis
@costashatz
Hahahha
Jonathan Hale
@Squareys

does github know something i don't?! :scream:

I think all bigger open source projects are getting this :P

Janos95
@Janos95
just noticed this :
"echo "#include <algorithm>" | gcc-head -std=c++11 -P -E -x c++ - | wc -l" returns 11765
while
"echo "#include <algorithm>" | gcc-head -std=c++20 -P -E -x c++ - | wc -l" returns a whopping 45222
compiling an empty file including the algorithm header takes 0.15 sec (with c++11) vs 0.9 sec (with c++20)
Vladimír Vondruš
@mosra
hah, i thought you'd compare that to gcc 9
Janos95
@Janos95
I chased the includes and it turns out that <algorithm> transitively includes <ranges> which is 30 loc and contains lots of template stuff
Vladimír Vondruš
@mosra
because this happened for gcc 10, so i expected improvements: https://twitter.com/wakomeup/status/1196097492456214529
#include <ranges> is a fireable offense, then