Allegro.cc - Online Community
Post Reply

Allegro.cc Forums » Allegro Development » Win32 binaries for Allegro 5.2.2 and MinGW 5.3.0.3

rss feed Print
 1   2 
Win32 binaries for Allegro 5.2.2 and MinGW 5.3.0.3
Edgar Reynaldo
Member #8,592
May 2007
avatar

No, that was my idea. tarring helps when you combine it with 7z. It makes for a much smaller archive than if you just 7z it straight from the beginning.

Neil,
The only difference between the 5.2.1.1 binaries and these is FreeType 2.6.5 instead of 2.7.1 in the newer version. The version of PhysFS used is the same, 2.0.3.

Can you provide a small demo program that shows what is wrong? That fails to load a ttf from an archive?

bamccaig
Member #7,536
July 2006
avatar

I guess the other reason is that tarballs preserve Unix permissions, but that probably doesn't apply to you. I wonder how .tar.xz compares to .tar.7z. I imagine MinGW must have xz by now... Though I guess that's chicken and egg for MinGW itself.

Neil Roy
Member #2,229
April 2002
avatar

Can you provide a small demo program that shows what is wrong? That fails to load a ttf from an archive?

Sure, just grab your physfs example you compiled. It fails. No need for one from me. I'm done with this. My next project will use SDL2.

I won't sit here playing twenty questions when I already showed that it worked with 5.2.1, and it doesn't work with this. I have changed NONE of my code... can you understand English?! IT WORKED BEFORE... IT DOESN'T WORK NOW... the ONLY thing that has changed is the Allegro version. I even used the compiler YOU provided.

If it was MY CODE, it would NEVER have worked. Download my Deluxe Pacman 2 game in the link in my signature. That is 5.2.1, and you will see it loads the fonts and uses them no problems with physfs. 5.2.2 (5.2.3GIT) here... will not.

This exact same problem came up 3 years ago in 2014 with someone else (I provided a link to their message earlier here). And they had the same problem, same error, same divide by zero or whatever... so obviously this is nothing new.

If you REALLY need an example, it's easy, make a zip, put a TTF into it, try and load the TTF using Allegro, loading the TTF from the ZIP with this version.

--
Deluxe Pacman
"Whereas Canada is founded upon principles that recognize the supremacy of God and the rule of law" - First line of the Canadian constitution.

Edgar Reynaldo
Member #8,592
May 2007
avatar

Have a little patience with me Neil? :-/

I'm not in any way accusing you of it being your fault.

I'm trying to narrow down the cause so I can fix it. The allegro version is not the only thing that changed. The freetype version changed also. It could be a bug in either library. There's not much you can screw up when compiling physfs or freetype, except which libpng you (choose to) use.

I've never used physfs before. I don't know why it would be failing to find the file within the archive, but it is, or it is mangling the file when reading it. That in turn depends on zlib.

So you can see, there's quite a few things that could go wrong.

I'll try to make an example to test this, but I don't have a lot of free time right now. :/

Neil Roy
Member #2,229
April 2002
avatar

If you scroll up, I have had patience. But there are no other answers I can give you. I compiled it with Allegro 5.2.1 and it works fine. I compiled it with this Allegro, and it will not load. I have had ZERO code change in my own game code as I don't work on that game anymore except to update it with newer versions of Allegro.

When I recompiled it, I recompiled it with the MinGW compiler you provided. I totally delete my old compiler folder and replace it entirely with yours. I have my libraries in a separate folder, so it wasn't corrupted somehow either.

The only libraries I use with this is Allegro. The only PNG I use is whatever comes with Allegro.

And as I already stated, the physfs example you compiled in the examples folder doesn't work. So, no need to really make something else, you already have something that fails in your example folder. That was not compiled by me at all, but it fails, so that is probably the best place to look.

My apologies but... when I get continually asked what I did wrong, or differently when I did nothing wrong, I get a little annoyed. I've told you all I can. I use the library properly, Lord knows I have enough experience with it and the problems. I am very careful to check everything and to report all errors, even where none are probable.

SOMETHING was changed between Allegro 5.2.1 and this one to do with Freetype and Phyfs. That's where I would look. Perhaps switch back to any older versions you used and recompile that physfs example with it and I would be happy to test it out. But... there's not much more I can do on my end.

--
Deluxe Pacman
"Whereas Canada is founded upon principles that recognize the supremacy of God and the rule of law" - First line of the Canadian constitution.

Edgar Reynaldo
Member #8,592
May 2007
avatar

Bumping the thread to give me more time to investigate this.

An older version of zlib may fix this.

EDIT
Actually, the version of zlib used in the 5.2.1.1 build was 1.2.8 where the version of zlib used in the 5.2.3 build is 1.2.11. That might be the problem.

Post Reply
 1   2 


Go to: