|
Allegro 4.2.0 has been released! |
Evert
Member #794
November 2000
|
That's right: no beta, no Release Candidate. This is the real thing. Grab it from the download page. Binary packages for Windows and MacOS X will be available in the course of the week. CHANGES since 4.2.0 RC2 said:
Peter Wang made fixmul() detect overflows as it used to do in the 4.0.x Peter Hull fixed a bug in the fixbundle utility. Dennis Busch found a bug where d_clear_proc would not work properly if the Grzegorz Adam Hankiewicz made Allegro log all TRACE output with a prefix Grzegorz Adam Hankiewicz made dialogs with MSG_CHAR/MSG_UCHAR handlers Peter Hull fixed problems with the mouse position as reported by Allegro and Peter Hull made Command-Q not close the application if no exit-button Peter Hull fixed problems with joysticks under MacOS X as reported by Peter Hull fixed a bug preventing more than one Allegro application from Peter Hull did a lot of other things for the MacOS X port too. Jiri Gabriel fixed loading of multiple ranges in a single bitmap with txt Milan Mimica and Jiri Gabriel fixed several bugs in extract_font_range. Dennis Busch fixed a Unicode bug in the mode selector. Evert Glebbeek added FA_ALL and FA_NONE file attribute flags. Peter Hull fixed a deadlock in OS X when calling vsync() while the screen Robert Alfonso fixed a grabber crash when importing a new font range into an Chris Robinson fixed the fileselector in UNIXnot properly recognising Hrvoje Ban and Peter Wang wrote a documentation section that explains Elias Pschernig disabled DGA auto-detection under X11 i_am_drv added support for .rmi midis to the midi reader Elias Pschernig fixed a fix-point overflow in pivot_sprite. Michal Molhanec fixed several problems with the Watcom compiler. Peter Hull fixed an error with 'make uninstall' on MacOS X. Matthew Leverton added a programs: makefile target. Many small fixes and improvements by Michal Molhanec, Peter Hull, Chris Documentation improvements by Grzegorz Adam Hankiewicz, Tore Halse and Missing from the archive is the new demo game (the old 4.0 demo is in the archive). This will be available shortly as a seperate download and will replace the old one in 4.2.1. Apart from the usual request that people start using it and report and help fixing problems (not too many, we hope), I think it would be nice if there was a short guide that goes over the differences (feature-wise) between 4.0 and 4.2. I can probably write one myself, but if someone wants to volunteer to do it that would be great. Many thanks to all the people who have contributed to Allegro in one way or another. This would never have happened without any of you or the support from the a.cc community. Cheers people! |
Corelian
Member #3,376
March 2003
|
I got the Windows-friendly .zip archive. My develpoment environment is MinGW (GCC 3.4.2) + MSYS (1.0.10). Built with ./fix.sh --dtou make make chm-docs make compress make install
Built AllegroGL (0.2.4 CVS), played the Allegro demo game, recompiled one of my own Allegro projects. The result: I would like to thank everyone working on this great library for your hard work and time. Now let's hope we'll see the new stable AllegroGL and OpenLayer 2.0 soon. EDIT: Quote: Hrvoje Ban and Peter Wang wrote a documentation section that explains several common mistakes. That is a good addition to the documentation, although its usefulness may be questionable since the most common beginner mistake seems to be the mistake #1: Ignoring this manual. In section Creating bitmaps before loading. IMHO there should be a /* wrong */ comment on the second line of code to clarify that the code is wrong and to make the documentation more consistent. SECOND EDIT: |
Richard Phipps
Member #1,632
November 2001
|
Great news! Well done everyone that's contributed to this. Thanks for all your efforts. |
ReyBrujo
Moderator
January 2001
|
Neat! I knew there was a reason I did not go to work today... besides feeling like vomiting at anytime! Now someone we all know will be forced to do some updates to the Files and Documentation sections ;-) Congratulations everyone! -- |
miran
Member #2,407
June 2002
|
Seems to be working fine in FC4. -- |
dthompson
Member #5,749
April 2005
|
Congratz guys! Well done! I'll download this immediately. ______________________________________________________ |
Fladimir da Gorf
Member #1,565
October 2001
|
Finally a "stable" release and not something with a name which scares the newcomers... Works perfectly for me! The downside is that now I need to get the precompiled versions of 4.2 for all platforms for OL 2.0... OpenLayer has reached a random SVN version number ;) | Online manual | Installation video!| MSVC projects now possible with cmake | Now alvailable as a Dev-C++ Devpack! (Thanks to Kotori) |
Felipe Maia
Member #6,190
September 2005
|
Thank you all. Allegro rules. |
ReyBrujo
Moderator
January 2001
|
Compiled and installed correctly under Ubuntu 5.10. Will check all the other builds later, installing a qemu with DSL to see if I can compile it there as well. -- |
Marco Radaelli
Member #3,028
December 2002
|
Compiled fine all the three versions on Windows XP SP2 with gcc 3.4.2
|
Leniuch
Member #5,175
October 2004
|
Great! The strange thing is, that I found an info about 4.2 coming at some other site (warsztat.pac.pl to be specific) before allegro.cc. Isn't that strange? EDIT: Too much "strange" here. Little advice: beer + posting = shame |
Evert
Member #794
November 2000
|
Well, I uploaded the files two days ago and I think the release was unofficially announced on #allegro, so it's possible someone got the news before I posted it here. |
amarillion
Member #940
January 2001
|
Congratulations evert, elias, peter, peter, grzegorz, dennis, chris and all the others -- |
juvinious
Member #5,145
October 2004
|
Works fine for me in Gentoo. __________________________________________ |
ReyBrujo
Moderator
January 2001
|
Compiled and "worked" under Qemu+DSL. Lack of X dev support forced it to work with VGA, but at least the demo worked "flawlessly". -- |
Paul Pridham
Member #250
April 2000
|
Yay, I'm first one to report problems! Only with the make procedure so far... here's what I get, after building for MSVC6: D:\allegro4_20>make install D:\allegro4_20>make chm-docs Compiling d:\allegro4_20\docs\chm\allegro.chm make: [docs/chm/allegro.chm] Error -1073741819 (ignored) ... For that last one, hhc.exe actually crashed. Didn't do this for the last 4.2 WIP. I was able to build the chm file via the Help Workshop GUY, however. ---- |
ImLeftFooted
Member #3,935
October 2003
|
C:\Documents and Settings\student\Desktop\allegro>make install make[3]: Entering directory `C:/Documents and Settings/student/Desktop/allegro' misc/mdhelper.sh C:/dev-cpp/lib C:/dev-cpp/include C:/dev-cpp/include/allegro C /dev-cpp/include/allegro/platform C:/dev-cpp/include/allegro/internal C:/dev-cp /include/allegro/inline sh: C:\Documents: No such file or directory make[3]: *** [create-install-dirs] Error 127 make[3]: Leaving directory `C:/Documents and Settings/student/Desktop/allegro' Maybe mdhelper.sh should get the files surrounded in quotes? Solution for now: move allegro to a directory that doesnt contain spaces. |
ReyBrujo
Moderator
January 2001
|
Hmm... for Dustin problem, I guess Allegro should check if there are spaces in the current directory, and get the DOS directory name, or warn about spaces in the path and stop the build. The problem for Paul is a bit more complex... note how all backslashes disappeared. That is, they weren't escaped? Can you run by hand misc\mdhelper.bat C:\PROGRA~1\MICROS~2\VC98\lib to see if that works? -- |
Paul Pridham
Member #250
April 2000
|
Ahh, ReyBrujo... my brain slowly churned into action and recalled something about using "mingw32-make" to build instead of just "make". I'm doing this now, and have built the regular and debug libs... now working on the static-linked. Maybe this is documented somewhere, but I didn't see it during my casual perusal of the build docs anyway. ---- |
Thomas Fjellstrom
Member #476
June 2000
|
Hasn't that always been the case? That allegro can't be in a path with spaces? -- |
ImLeftFooted
Member #3,935
October 2003
|
These demos had a rather odd effect on this Win2k Pro Service pack 4 machine excolmap ones that i tested and look ok: Problem description: Hypothesis: Looks like something to that changes based on the resolution of the screen maybe? Maybe theres a flaw in win2k's direct x drivers? |
Kitty Cat
Member #2,815
October 2002
|
Sounds like the video card's drivers are using improper hsync and vsync settings. Some monitors will let you adjust this on a per-resolution basis. -- |
ImLeftFooted
Member #3,935
October 2003
|
Edit: |
Paul Pridham
Member #250
April 2000
|
Quote: Hasn't that always been the case? That allegro can't be in a path with spaces? Well I thought that the "fix.bat msvc --msvcpaths" was supposed to take care of it... ---- |
Thomas Fjellstrom
Member #476
June 2000
|
Quote: Well I thought that the "fix.bat msvc --msvcpaths" was supposed to take care of it... Wouldn't that just take care of the paths to msvc? -- |
|
|