I'm having some trouble using the mouse in my allegro programs.
I'm not sure if it's setup related but this seemed like a good place to post it.
When I compile any program that uses
extern volatile int mouse_x; or any of the volitile mouse variables I get a messed up linker message.
Note no problems up untill linking.
Does anyone else have this problem or do you think I installed it improperly.
I followed Bob's Dev-C++ \ Allegro instructions to a tee.

Come to think of it.. in the example directory all the examples work. So it may be a problem I'm having with Dev-C++
well here are my linker messages:
code:Warning: resolving _mouse_y by linking to __imp__mouse_y (auto-import)
Warning: resolving _mouse_x by linking to __imp__mouse_x (auto-import)
fu000001.o(.idata$3+0xc): undefined reference to `lib_mingw32_liballeg_a_iname'
fu000003.o(.idata$3+0xc): undefined reference to `lib_mingw32_liballeg_a_iname'
nmth000000.o(.idata$4+0x0): undefined reference to `_nm__mouse_y'
nmth000002.o(.idata$4+0x0): undefined reference to `_nm__mouse_x'
I get these any time I try to the extern mouse variables heres some sample code that generated those errors
code:#include <allegro.h>
extern volatile int mouse_x;
extern volatile int mouse_y;
extern volatile int mouse_b;
int main() {
allegro_init();
install_mouse();
install_keyboard();
set_gfx_mode(GFX_AUTODETECT, 320,200,0,0);
while (key[KEY_ESC]) {
textprintf(screen, font, 1,1,10,"Mouse: %d,%d",mouse_x,mouse_y);
};
return 0;
}
END_OF_MAIN();
And here's what the Dev-C++ compile log looks like:
code:Linking files :
C:\DEVCPP\BIN\g++ "c:\mywork\mouse\main.o" -o c:\mywork\mouse\Mouse.exe C:\DevCpp\Lib\liballeg.a -s -IC:\DEVCPP\INCLUDE\ -IC:\DEVCPP\INCLUDE\G__~1 -IC:\DEVCPP\INCLUDE\ -LC:\DEVCPP\LIB\ -BC:\DEVCPP\BIN\

My Dev-C++/MinGW32/Allegro installation is per Bob's specifications

I had this funny feeling that is what he was doing. That's why I wanted to look at his code.

Stupic, eh?

WHy would you do it in the first place? Is it really necessary?