Closed vtereshkov closed 1 year ago
I'm looking into it rn
@skejeton No, it doesn't, as I have already told you. My conjecture is that this *.exe is in fact a debug build rather than a release one, so that it expects the debug versions of those DLLs (notice the D suffix in the DLL names).
On the other hand, when I run the same *.exe on another machine with Visual Studio installed, it no more complains about the DLLs, but immediately crashes on a failed assertion:
@skejeton The only way to run the app I have found so far is to clone the repo and rebuild everything from scratch:
@skejeton I have finally figured out what we need to fix this issue:
catedu.exe
rather than debug ones (no more problems with missing DLLs)user
and assets
folders to the same folder as catedu.exe
(they all can be in the same archive)Hmm interesting because I thought the builds were already compiled in release mode. I'll fix the CI right now.
Yes indeed the build script used debug builds.
@vtereshkov Can you confirm the CI builds work with the most recent build?
@skejeton Your latest Git LFS fix CI has failed -- please check it. Without this fix, I only have symlinks, not the actual assets.
Yeah I saw that. I'm working on it right now.
@vtereshkov Should be all fixed.
@skejeton Confirmed and closed.