On Oct 4, 2006, at 8:55 PM, Ryan McDougall wrote:
However the problem remains that Im at a bit of a loss how to ship a
shared .SO library easily. If I build on my machine (or a set of
supported build machines) then the build will link to my prefix (lets
say /usr/lib) and the end user has no choi
Hi,
I think you're confusing the idea of a build system for portable
software
(something the autotools suite can help with) and an installer (or
package
if you're installing onto a system that has a package manager). From a
Windows perspective, it's the same as the difference between Visual
The trick is that if we use a configure.ac file to help decide what
flags may be needed, >inside< this configure script we need to use
CFLAGS and CPPFLAGS to effect the running of configure.
Not really. Just AC_SUBST a variable in the AM_CFLAGS or AM_CPPFLAGS
directive. E.g., when I write an a
