Hello,
[adding automake; replies can drop bug-gsl]
This is
http://lists.gnu.org/archive/html/bug-gsl/2010-06/msg2.html
On 6/13/10 4:16 PM, Brian Gough wrote:
At Thu, 10 Jun 2010 22:16:58 -0400,
Peter Johansson wrote:
AFAIK there is no option in Automake to '--install' only some files
* Peter Rosin wrote on Sat, Jun 19, 2010 at 09:54:22PM CEST:
> The configure script has the following (admittedly boilerplate)
> text in its --help output:
>
> Usage: ./configure [OPTION]... [VAR=VALUE]...
>
> To assign environment variables (e.g., CC, CFLAGS...), specify them as
> VAR=VALUE. Se
At Saturday 19 June 2010, Peter Rosin wrote:
> Hi!
>
> I'm trying to get in position for running the testsuite on MSYS
> using the Microsoft C/C++ Compiler (and don't really know what to
> expect).
>
> As a first step I tried this on a fresh checkout:
>
> ./bootstrap
> ./configure CC=cl CFLAGS
Hi!
I'm trying to get in position for running the testsuite on MSYS using
the Microsoft C/C++ Compiler (and don't really know what to expect).
As a first step I tried this on a fresh checkout:
./bootstrap
./configure CC=cl CFLAGS=-MD CXX=cl CXXFLAGS=-MD
make
and that triggered a distcheck of a
* Wesley Smith wrote on Sat, Jun 19, 2010 at 03:02:26PM CEST:
> Also, one more follow up questions ... how can I have autotools not
> put things in the .libs hidden dir but in the source dir itself?
You can't; that's by intention: in order to use uninstalled libraries
and modules, you typically ne
At Saturday 19 June 2010, Wesley Smith wrote:
>
> Where is this documented? I've been looking here:
> http://www.gnu.org/software/autoconf/manual/autoconf.html .
> There's not much in the way of what the various Makefile.am
> conventions are on this page. Is there a better reference?
The bett
Also, one more follow up questions ... how can I have autotools not
put things in the .libs hidden dir but in the source dir itself?
wes
On Sat, Jun 19, 2010 at 5:50 AM, Ralf Wildenhues wrote:
> Hello Wesley,
>
> * Wesley Smith wrote on Sat, Jun 19, 2010 at 02:40:53PM CEST:
>> I'm trying to use autotools to compile shared object Lua modules. The
>> way these modules are named differs from the typical .so conventions
>> because the
Hello Wesley,
* Wesley Smith wrote on Sat, Jun 19, 2010 at 02:40:53PM CEST:
> I'm trying to use autotools to compile shared object Lua modules. The
> way these modules are named differs from the typical .so conventions
> because they're not actually libs one links against but are instead
> loaded
Hi,
I'm trying to use autotools to compile shared object Lua modules. The
way these modules are named differs from the typical .so conventions
because they're not actually libs one links against but are instead
loaded by Lua itself. For example, a Lua module binding OpenGL would
look like opengl.
10 matches
Mail list logo
