Mudlet - Forum

I'd probably suggest not even worry about 5.4.2 anymore, and just stick with those library versions (for windows, at least) and 5.6. I'm not sure which of the 3 was causing the problem, however, i'm running the 5.6 compile i'd just made right now, and everything seems to be running error free with my script.

After this long waiting a bit longer shouldn't be a huge issue - Maybe wait until you're also able to sign the final binary?

Yep, I've went off your previous list, so it should be those libraries - still had the issue on them.

Here's the change I made in src.pro with the successful 5.6 build
I'm not sure why the mudlet5_package references are there

Pretty sure I've got Qt 5.6 at 100% now. I've built + tested the resulting compile.

I've updated the wiki, and changed the instructions on pcre for 8.38, and boost to 1.60

In the lua instructions, I added a change there (change TO_LIB= liblua.a to TO_LIB= liblua.a lua51.dll)
to build the lua51.dll file

The below needs to be changed in mudlet's src.pro

src.pro:

} else:win32: {
LIBS += -L"C:\\mudlet5_package" \
-L"C:\\mingw32\\lib" \
-L"C:\\mingw32\\bin" \
-llua51 \
-lpcre-1 \
-llibhunspell-1.4 \
-lzip \ # for dlgPackageExporter
-lz \ # for ctelnet.cpp
-lyajl \
-lopengl32 \
-lglut \
-lglu32
INCLUDEPATH += "C:\\mingw32\\include"
# Leave this undefined so mudlet::readSettings() preprocessing will fall back to

The mudlet5_packages thing is probably where the person who wrote that portion of the project file was storing things on their machine! By rights we should probably have a variable near the top of the file which a user can set to their own requirements and which is used elsewhere it is needed. I'd tend to something based on a subdirectory of a "src" subdirectory of my own user home directory - but I can't see an obvious way to obtain the user's home directory for a qmake project file without a bit of platform specific hackery involving environment variables that are platform (and possibly version) dependent...

Noticed this while extracting, not sure if it has an effect:

tar: hunspell-1.4.1/compile: Cannot create symlink to `/usr/share/automake-1.15/compile': No such file or directory
tar: Exiting with failure status due to previous errors

I'd not noticed the failed symlink with extracting hunspell, however, it doesn't impact the compile. I've got mudlet running with no obvious problems + my script loaded from the 5.6 compile I made from the wiki. The build I made was all cut/paste, I didn't follow any steps that weren't listed. Hopefully the certificate arrives soon

Got my build to work as well, though I've had to copy lua51.dll from the directory it was in to mingw32/bin in order for the LuaRocks installer to work.

I haven't had a reply yet from the certificate company on how to renew a certificate (the web store doesn't offer an option) and I don't want to just buy a new one since that could be dodgy. I'll release epsilon unsigned.

That was in the instructions, yes
Good to hear it's working now though

You're right, I've added that part in myself.