|
Video files in Allgro? |
Martano
Member #6,536
October 2005
|
I downloaded "all420.zip" and unzipped it in my allegro folder, overwriting all. But still get the same errors. |
Victor Williams Stafusa da Silva
Member #4,212
January 2004
|
Andréas Martano said: I downloaded "all420.zip" and unzipped it in my allegro folder, overwriting all. But still get the same errors. Did you runned "fix", "make" and "make install"? [The attack of the space bugs - Speedhack 2005] [Rambananas - Speedhack 2006] [Make clean - Speedhack 2009] [The source god - TINS 2010] |
Evert
Member #794
November 2000
|
Just grab a binary package from the files section of Allegro.cc |
Thomas Fjellstrom
Member #476
June 2000
|
Also, don't just overwrite, delete the original folder, then uncompress the new. Otherwise things will screw up. -- |
Martano
Member #6,536
October 2005
|
I always get an error when trying to run make. But the binaries in the download page are from 4.0.3 ....too late already overwrote them. -------------------------------------------------- Found them! Found the binaries for 4.2 . |
Evert
Member #794
November 2000
|
Quote: I always get an error when trying to run make. What's the error message and how do you run make? Quote: ....too late already overwrote them. Not a problem. Just delete the directory tree and unpack a clean package. |
Martano
Member #6,536
October 2005
|
Quote: What's the error message and how do you run make?
I open a shell, go to the makefile folder and type: makefile After I tried to change the name of the makefile to "makefile.exe". And used the shell again. With the APEG makefile it complains about a fatal error. With the Allegro makefile it doesn't complain, but do nothing (at least I saw no change). ---------------------------------------------- I copied Allegro 4.2 to the right folders and I am getting these errors now: [Linker error] undefined reference to `oggpackB_readinit' What is the mean of "Linker error" is it about the includes, linker (-lalleg), or what? |
Michael Faerber
Member #4,800
July 2004
|
Do not rename Makefile to Makefile.exe!! Instead you have to run an existing make.exe or mingw32-make.exe in the directory where the Makefile is located. Example: Your mingw32-make.exe is in C:\MINGW\BIN. Your Makefile is in C:\ALLEGRO. You have to open a command line window and type: CD C:\ALLEGRO -- |
Evert
Member #794
November 2000
|
Quote:
I open a shell, go to the makefile folder and type: makefile
Ok, have you read the instructions in allegro/doc/build/ (pick the one for your compiler, probably MinGW or MSVC)? |
Martano
Member #6,536
October 2005
|
Thanks for the explanation. But now I am having only this error when compiling the example code: C:\Dev-Cpp\Meus\ABCD\Makefile.win [Build Error] [Testes.exe] Error 1 If I delete the: libapeg.a from the linker, the error disappears. But I get "linker errors". ----------------------------------------- Now I copied the APEG binaries to the same folder of the test project. [Linker error] undefined reference to `oggpackB_read' I am not even using the command: oggpackB_read |
Kitty Cat
Member #2,815
October 2002
|
You should probably show us the actual error. Saying that removing the libs from the linker removes the errors but gives you errors doesn't make much sense. PS. you normally use -lname to specify a library (libname.a) on the command line. -- |
Victor Williams Stafusa da Silva
Member #4,212
January 2004
|
Sorry to saying that in this form, but its looks like that you fuked up your compiler completely deleting, renaming and replacing files when you shouldn't do that. And fuked allegro too. I recommed to delete your compiler and your allegro and reinstall they from the start... [The attack of the space bugs - Speedhack 2005] [Rambananas - Speedhack 2006] [Make clean - Speedhack 2009] [The source god - TINS 2010] |
Martano
Member #6,536
October 2005
|
I tried to put a "-" before the "libapeg.a", but got an error saying that couldn't find: -libapeg.a ---- The problem is: If I have: libapeg.a in the linkers, I get many errors of this type: [Linker error] undefined reference to `oggpackB_readinit' - If I put only: -lalleg int the linker, I get only these errors: C:\Dev-Cpp\Meus\ABCD\testes.o In function `Z13_mangled_mainiPPc': - The code is:
|
Kitty Cat
Member #2,815
October 2002
|
Quote: I tried to put a "-" before the "libapeg.a", but got an error saying that couldn't find: -libapeg.a Becuase that's not right. The lib<name>.a files should be in your compiler's lib directory, and you link with them using -l<name> (similar to how Allegro is liballeg.a and you link with -lalleg). -- |
Martano
Member #6,536
October 2005
|
Thanks again. But now I am getting only this error: C:\Dev-Cpp\Meus\ABCD\Makefile.win [Build Error] [Testes.exe] Error 1 I will try to reinstall Dev and Allegro like Victor said. |
Kitty Cat
Member #2,815
October 2002
|
Quote:
But now I am getting only this error: That's not the error. That just says that there was an error. The actual error should be before that. -- |
Martano
Member #6,536
October 2005
|
But the compile tab says only that. The Compile Log says: Compiler: Default compiler O sistema nÆo pode encontrar o arquivo especificado. (The system couldn't find the file) make.exe: *** [Testes.exe] Error 1 Execution terminated |
Kitty Cat
Member #2,815
October 2002
|
It can't find the libs. Double check those -l switches, and see why they aren't the same as liballeg.a/-lalleg -- |
Martano
Member #6,536
October 2005
|
The linkers that I am using are: -l<libapeg.a> |
Kitty Cat
Member #2,815
October 2002
|
Reread my post. Quote: It can't find the libs. Double check those -l switches, and see why they aren't the same as liballeg.a/-lalleg
-- |
Martano
Member #6,536
October 2005
|
Quote: Reread my post. Quote: Sorry... I didn't understand it. What do you want to say with "double check" and "why they aren't the same"? |
Kitty Cat
Member #2,815
October 2002
|
Well, to use liballeg.a, you use -lalleg. So, to use libapeg.a, you use...? -- |
Martano
Member #6,536
October 2005
|
-lapeg ? Didn't work : cannot find -lapeg I will try to reinstall. |
Michael Jensen
Member #2,870
October 2002
|
Quote: But the compile tab I didn't know the command line had a compile tab... anyway let us know what happens.
|
Martano
Member #6,536
October 2005
|
APEG.txt: "Windows users: If you're going to link against the static version of Do I need to do that? Because I have only the binaries, and not 'cbuild' and 'cbuild install'. ------------ I reinstalled XP, dev-cpp, allegro (copied the binaries to "C:\Dev-Cpp\include" and "C:\Dev-Cpp\lib", and the 3 ".dll" files to the folder of my project) and APEG (copied the ".h" files to "C:\Dev-Cpp\include", the ".a" files to "C:\Dev-Cpp\lib", and the ".dll" files to my project folder). Then I changed the linkers of my project to: -lapeg But when I try to compile I receive many errors of this type: [Linker error] undefined reference to `oggpackB_readinit' The problem is, as you can see in the code showed in previous post, I am not using any "ogg". But when I try to delete the linkers related to APEG, I get only these errors: C:\Dev-Cpp\Meus\ABCD\testes.o(.text+0x1a9) In function `Z13_mangled_mainiPPc': These errors make sense, because I AM using `apeg_play_mpg' in the code. I hope this explain all the problem. |
|
|