Hi Arthur,
Look carefully at your configure.ac file or any scripts calling your
makefile. See if you find anyone setting CFLAGS, CPPFLAGS, etc on the
way in. They maybe adding -c (erroneously) to these variables.
To answer your question, the TEST macro should be completely independent
of the
Win7-64 bit
Cygwin 64-bit
g++ 4.9.2
I'm trying to link test program. The linker command option given to g++
during 'make check' says "don't link". Any way around this?
check_PROGRAMS = test
test_INCLUDE = -I$(top_srcdir)/src
test_SOURCES = $(testCPP) $(testHead)
test_LDADD
> -Original Message-
> From: Gavin Smith [mailto:gavinsmith0...@gmail.com]
> Sent: Thursday, March 12, 2015 9:09 AM
> To: Andy Falanga (afalanga)
> Cc: automake@gnu.org
> Subject: Re: How are env variables passed to the compilation process
>
> On 10 March 2015 at 22:04, Andy Falanga (afala
On 10 March 2015 at 22:04, Andy Falanga (afalanga) wrote:
> I'm trying to figure out how things like CXXFLAGS and CFLAGS get passed to
> ultimate point of compilation. I thought I had it down but something that
> just happened recently has me wondering. I've gotten my project building now
> u
My modified src/Makefile.am is:
# Testing SLIP
testdir= ./test
check_PROGRAMS = test
test_SOURCES = $(testCPP) $(testHead)
test_LDADD = libslip.a
TESTS = $(check_PROGRAMS)
CLEANFILES = $(testdir)
I have found that if $(testHead) is not incl
