![]() |
|
This thread is locked; no one can reply to it.
![]() ![]() |
1
2
|
Allegro 4.1.16 - clear_to_color bug |
Richard Phipps
Member #1,632
November 2001
![]() |
It works! It seems that I have an include folder in Dev-Cpp and an include folder in Dev-CPP/Mingw32. It looks like Dev-c++ was using the Dev-CPP/Include one. However I've noticed that the allegro version comes out as 4.1.14 rather than 4.1.16. It likes like I have old junk left there.. Waah! |
Carrus85
Member #2,633
August 2002
![]() |
|
Elias
Member #358
May 2000
|
Haha. Just the typical devcpp-is-to-blame Maybe: #define allegro_init() allegro_init_version_check(ALLEGRO_VERSION_STR) allegro_init_version_check(char const *str) { if (strcmp (str, ALLEGRO_VERSION_STR)) allegro_message ("Wanring! Your headers version is different from the library version!"); } Of course, this would need more than a simple strcmp, e.g. 4.0.0/4.0.3 would be ok.. but it would have detected this particular case at least. -- |
Evert
Member #794
November 2000
![]() |
Quote: Maybe check in allegro_init if the DLL version and the header version is the same? Yes! I think this is a great idea, actually. Quote: Of course, this would need more than a simple strcmp, e.g. 4.0.0/4.0.3 would be ok.. We can just skip the check if ALLEGRO_SUB_VERSION&1 is false. |
|
1
2
|