|
|
|
| Allegro 4.2.0 has been released! |
|
Evert
Member #794
November 2000
 |
Quote:
D:\allegro4_20>make install
That happens if there's a mis-match in DJGPP and MinGW programmes. You wouldn't be using DJGPP's make, or MinGW's make with a DJGPP-based bash, would you? |
|
Tobias Dammers
Member #2,604
August 2002
 |
Hehehe.... crappy LFN support I guess... /me remembers the ugly workarounds djgpp uses... --- |
|
Ronald Blankendaal
Member #6,561
November 2005
|
Hi everybody, Congratulations to all the people that made 4.2.0 a reality! Amazing job, guys! Allegro builds fine on MingW32 for me, but unfortunately it doesn't on DJGPP (gcc.exe (GCC) 4.0.1), this is the message I get: Compiling Allegro for djgpp, optimised. Please wait... Am I doing something wrong ('fix djgpp', 'make')? Are the devs aware of this issue? Kindest regards, Ronald |
|
Peter Wang
Member #23
April 2000
|
Oops. Please add this line somewhere near the top of src/graphics.c. Thanks for pointing it out. extern void blit_end(void);
|
|
gnolam
Member #2,030
March 2002
 |
Nice! Now we just need a new version of AllegroGL. -- |
|
Fladimir da Gorf
Member #1,565
October 2001
 |
A small request, people: I only have Windows and GCC, so could you OS X, Linux and MSVC users attach your compiled library files? 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) |
|
Ronald Blankendaal
Member #6,561
November 2005
|
Thanks for the help Peter, Allegro compiles ok now, and the examples seem to work just fine. src/dos/vesa.c: In function 'get_vesa_info': and this is the output of 'make install': C:\DJGPP\allegro>make install C:\DJGPP\ALLEGRO> misc\mdhelper.bat c:\djgpp\include C:\DJGPP\ALLEGRO> misc\mdhelper.bat c:\djgpp\include\allegro C:\DJGPP\ALLEGRO> misc\mdhelper.bat c:\djgpp\include\allegro\platform C:\DJGPP\ALLEGRO> misc\mdhelper.bat c:\djgpp\include\allegro\internal C:\DJGPP\ALLEGRO> misc\mdhelper.bat c:\djgpp\include\allegro\inline C:\DJGPP\ALLEGRO> copy lib\djgpp\liballeg.a c:\djgpp\lib I don't think that went entirely correct.. any idea what's wrong? Regards, Ronald |
|
Dennis
Member #1,090
July 2003
 |
Compiled Allegro4.20 with MinGW3.1.0 and MSVC6. For my project, i only use MSVC6 to compile. Problem: Oddity: --- 0xDB | @dennisbusch_de --- |
|
Thomas Harte
Member #33
April 2000
 |
Quote: A small request, people: I only have Windows and GCC, so could you OS X, Linux and MSVC users attach your compiled library files? I have to admit to not really understanding the way libraries work on OS X yet. I have attached a bundle of everything from lib/macosx, but whether that is enough to install the framework and template that most OS X users will consider essential rather than just the BSD subsystem style libs I have no idea. I used GCC 4.0 and all the latest libraries, so these are probably for OS X v10.4 Tiger only. [My site] [Tetrominoes] |
|
Peter Wang
Member #23
April 2000
|
Ronald: did the header files get installed properly? Otherwise install-info failing is ignorable (though allegro.info should have been generated). EDIT: attached a patch which should fix the warnings with src/dos/vesa.c Dennis: the problem is that hline and vline are now inline functions which actually call _allegro_hline and _allegro_vline. The implementations are in include/allegro/inline/draw.inl. What happens if you use one of the older fixed-point functions in debug mode, say, fcos instead of fixcos? I'm not familiar with MSVC so I'm just hoping that the problem does not show up with fcos.
|
|
Paul Pridham
Member #250
April 2000
 |
Quote: That happens if there's a mis-match in DJGPP and MinGW programmes. You wouldn't be using DJGPP's make, or MinGW's make with a DJGPP-based bash, would you? Evert, I have recently updated my mingw32 installation, and I don't have DJGPP set up on my machine currently. The "make.exe" in my mingw32/bin directory looks a little suspect though: root 122880 Nov 7 1999 make.exe* Shouldn't it be newer? Maybe I just didn't install mingw properly. Honestly, I don't remember, I did it one bored evening this past summer. Anyway, everything is built, including the CHM docs, and running smoothly. Thanks to the Allegro team, the Earth is safe once again! ---- |
|
Peter Wang
Member #23
April 2000
|
For all our sakes, please delete that thing or move it out of the way! Or just run "make -v" and see what it is.
|
|
Ronald Blankendaal
Member #6,561
November 2005
|
Peter, Both liballeg.a and the header files got installed successfully. I guess that's fine then, thanks again for the patch and your help. Regards, Ronald |
|
ReyBrujo
Moderator
January 2001
 |
Ronald, were you compiling and installing under a pure DOS environment? Or using Windows XP? Check if you got an allegro.inf file created, maybe it did not support the four letter extension and created a three letter one instead. -- |
|
Ronald Blankendaal
Member #6,561
November 2005
|
Hello again, I'm compiling on a dos command prompt inside WinXP. Inside C:\DJGPP\allegro\docs\info, the file allegro.info gets created, but during make install, the copy command fails: copy docs\info\allegro.info c:\djgpp\info Maybe the path in which the copy command is executed is not C:\DJGPP\allegro, because a manual copy inside that directory DOES work?! Or there might be a problem with the uppercasing of the file? Ronald |
|
ReyBrujo
Moderator
January 2001
|
Quote: misc\mdhelper.bat c:\djgpp\include\allegro\inline C:\DJGPP\ALLEGRO> Is it possible that you already had the directory created, which generated this error? Quote:
copy lib\djgpp\liballeg.a c:\djgpp\lib It was in the allegro directory, as it could copy the library but not the info. I am a bit lightheaded right now, so I cannot guess what happened. -- |
|
Paul Pridham
Member #250
April 2000
|
Peter,
Huh, strange! Anyway yea, I'll get rid of it. ---- |
|
Michael Faerber
Member #4,800
July 2004
 |
I've quickly tried to make an ebuild for the new Allegro version, there I found something: In the Allegro 4.1.18 ebuild (the most recent official one) there is a patch for Allegro, looking like this: --- misc/allegro.m4 +++ misc/allegro.m4 @@ -11,7 +11,7 @@ dnl AM_PATH_allegro([MINIMUM-VERSION, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]$ dnl Test for allegro, and define allegro_CFLAGS and allegro_LIBS dnl -AC_DEFUN(AM_PATH_ALLEGRO,[ +AC_DEFUN([AM_PATH_ALLEGRO],[ AC_ARG_WITH(allegro-prefix, [ --with-allegro-prefix=PFX Prefix where liballegro is installe$ ALLEGRO_CONFIG_prefix="$withval", ALLEGRO_CONFIG_prefix="") I plan to submit a new ebuild to Gentoo Portage, but before I do this I want to know if this patch is still necessary? Oh, and btw, Allegro compiled fine (also without the patch). EDIT: I just noticed that the new demo game wasn't included -- |
|
Evert
Member #794
November 2000
|
Quote: but before I do this I want to know if this patch is still necessary? No, that fix was made a while back. Quote: Allegro compiled fine (also without the patch). It would - the patch doesn't affect the build process of Allegro, it affects the allegro.m4 file that other people can use to test if Allegro is installed. By the way, if you're also in charge of specifying on what hardware Allegro has been tested and is known to work, Allegro is 64 bit safe. |
|
Michael Faerber
Member #4,800
July 2004
|
Thanks for your answer! I've already written a bug report on Bugzilla so that the new Ebuild will be included in Portage! -- |
|
Dennis
Member #1,090
July 2003
|
Peter Wang said: the problem is that hline and vline are now inline functions which actually call _allegro_hline and _allegro_vline. The implementations are in include/allegro/inline/draw.inl.
recognition: solution: conclusion: (recognition,solution,conclusion...the AK-47 robot from KnightsOfTheOldRepublic reprogrammed me to this funny type of answer-structuring:)) Peter Wang said: What happens if you use one of the older fixed-point functions in debug mode, say, fcos instead of fixcos? I'm not familiar with MSVC so I'm just hoping that the problem does not show up with fcos. 'fcos' works without any warnings or errors. --- 0xDB | @dennisbusch_de --- |
|
Ronald Blankendaal
Member #6,561
November 2005
|
Hi everybody, I decided to remove my djgpp directory entirely and rebuild from scratch. Still, a minor, related, warning pops up during compilation: tests/vesainfo.c: In function 'get_vesa_info': Everything else is smooth. Then, 'make install' does its magic, until Extended Error 183 install-info c:/djgpp/info/allegro.info c:/djgpp/info/dir After make finishes, I can do the copy and install-info commands manually myself without problems. All the other files are installed as far as I can tell, and the examples work fine. I've no idea what's the problem here, can you guys tell me where to look further? Regards, Ronald |
|
ReyBrujo
Moderator
January 2001
|
I would ask you to do a small test: search in makefile.dj and makefile.all for the allegro.info rule, and rename allegro.info to allegro.inf, and try again. My bet is that, for who knows why, the four letter extension is breaking this build (similar to an old Watcom problem where compilation failed because a file had nine characters as name: datafiles.c). I am at work right now, but may be able to check and modify the makefiles if you cannot. -- |
|
Ronald Blankendaal
Member #6,561
November 2005
|
Thank you ReyBrujo, that was it! I changed makefile.dj, line 42 from INFO = info and that did the trick, make install works fine now. Thanks again, fellows! Regards, Ronald |
|
Peter Wang
Member #23
April 2000
|
Dennis: It's strange, because hline/vline are supposed to be using the same technique as fcos and friends. I can't see any difference between them. Please try to figure it out and let me know if you need some guidance around the Allegro source code.
|
|
|
|
and the old demo game still showed the Allegro 4.0 movie ...