> > It will work just fine when you don't, as long as you include the
> > directory where the lib file is in your LIB path. Which is the same
> > way the linker commandline option works. I don't see how
> that makes it
> > useless, though.
>
> If you have to include (the equivalent of) -L in your link
> command anyway, I don't see where being able to leave off -l
> buys much.
You don't, as long as you either stick the LIB file in the default
library directory, or modify the environment variable LIB to include
wherever you stick the LIB file. Both of which could be handled by an
installer.
//Magnus
