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
> 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
On Wed, 2006-10-04 at 20:11 -0700, Andre Stechert wrote:
> 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
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
Hello,
First of all, Im only looking for serious answers, and I dont want to
start any flamewars, so Ill start out by saying that quite likely the
only problem here is my lack of knowledge of autotools, and the other
the issues involved. Please correct me at any point you disagree with.
After s
Hello,
On Wed, Oct 04, 2006 at 11:59:40AM +0800, Tzu-Chien Chiu wrote:
> Makefile.am
> bin_PROGRAMS = bar
> bar_LDADD = @top_builddir@/xyz.la
> bar_DEPENDENCIES = $(bar_LDADD) @many_objs@
a few nits first: all AC_SUBSTed variables are available as make
variables, so you can use $(top_builddir) a
