GUI v3.0.3 entry point error about mcmap HOT 5 OPEN

What is your machine/version of windows ? I will take another look, but not now. A cursory glance says it might be an architecture issue. In the meantime, I laid the steps out there: #103 So you can try for yourself, and be sure there will not be any issues.

Also, as I was saying in the previous issue, please avoid recreating issues and prefer reopening old ones.

from mcmap.

Also, as I was saying in the previous issue, please avoid recreating issues and prefer reopening old ones.

Unfortunately I do not have permission to reopen an issue (only close as complete or close as not planned on an open issue) otherwise I would have; the option disappears entirely on a closed issue despite being the author of that issue.

I'll have a look through #103; thank you! In the mean time, would something likely have changed internally between 3.0.2 and 3.0.3 that would require a later version of windows?

from mcmap.

My bad then, I was not aware this was a thing. Thank you for letting me know.

I do not think so. It is either a compilation issue/not static enough or a platform mismatch; are you able to give anything about your setup ? Windows 10/11 ? 64bits ? amd64 ?

Most likely it is a GPU dependency pulled by graphical interface, even though I specifically built it statically it must depend on some libs.

from mcmap.

I do not think so. It is either a compilation issue/not static enough or a platform mismatch; are you able to give anything about your setup ? Windows 10/11 ? 64bits ? amd64 ?

Most likely it is a GPU dependency pulled by graphical interface, even though I specifically built it statically it must depend on some libs.

Running 64bit win7 on this machine; neither OS not GPU/driver changes on my end between 3.0.2 and 3.0.3 so my assumption is some manner of dependency. Was 3.0.2 compiled on win7 while 3.0.3 was compiled on win10/11? I was turning it over last night and was wondering if it could change due to the source OS at compilation time but that's definitely above my pay grade.

If I work through #103 and it functions we could potentially assume source OS, while if it doesn't we could perhaps assume some library that was updated between 3.0.2 and 3.0.3? Worst case, I'll hand it over to a win11 machine (it's out for repair again; HP and I are not friends) and pass it the server's save files each time. I'll definitely let you know what I find when I make the time to try it out.

from mcmap.

I imagine the source OS influences.

The big difference was the switch to Qt6 and is most likely the culprit. I spent a few hours building with all kinds of configurations but I could not remove the dx*.dll dependencies, so building with Qt5 must be the way to go for win7. I do not own a win7 machine and would rather keep my build servant on win10, so I guess win7 and win11 will not be supported configurations.

However, I am about to leave the country and will not have a Windows machine to test on for two weeks. In the meantime, please try using the powershell and running the CLI version of mcmap 3.0.3 - if you are on a server it may even be easier to automate with a bat file.

If you really want the GUI fast, please try #103, and ask questions on there so that we can improve and end up with a definite guide on how to build. Switching from Qt6 to Qt5 is done by going through the project and replacing 'Qt6' by 'Qt5', so don't be afraid writing on things.

from mcmap.