[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Mon, Apr 23, 2001 at 10:49:30AM +0100, Vincent Penquerc'h wrote:
> > system allegro.h. This may be kind of out of date though, since
> > shared libraries cloud the issue a lot (you have to either
> > install the test version, or jump through hoops) and in any
> > case, it doesn't make sense because `-I' would also apply to
> > <>-included files.
>
> indeed, examples do link with the system library, so it needs to be
> installed for the samples to be installed. not a big deal for me as i
> installed it in my $HOME, i just noticed it yesterday trying to implement
> the linux set_keyboard_rate call. i think i know why it was not
> implemented in the first place, the ioctl returns errno 22 (wrong
> parameters) every time ...
They link with it at run-time, yes, unless you tell them
otherwise. When testing AllegroGL with custom versions of
Allegro, I always do a `make install' because it's too
inconvenient otherwise. But if you're just trying out the
Allegro example programs to test your changes, and would rather
jump through hoops than install the new library, you can set
environment variables to tell the run-time linker to use a
different copy of the library.
George