Bob Friesenhahn <[EMAIL PROTECTED]> writes:
> On Wed, 26 Jul 2006, Ed Hartnett wrote:
>>
>> I have no check target per se, just the automake primary. I have:
>>
>> # Test the netCDF-3 library.
>> check_PROGRAMS = t_nc
>> TESTS = ${check_PROGRAMS}
>>
>> This yields in the Makefile:
>>
>> check_PROG
On Wed, 26 Jul 2006, Ed Hartnett wrote:
I have no check target per se, just the automake primary. I have:
# Test the netCDF-3 library.
check_PROGRAMS = t_nc
TESTS = ${check_PROGRAMS}
This yields in the Makefile:
check_PROGRAMS = t_nc$(EXEEXT)
I see. It appears that the auto-extension of PR
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>>
>> When I call the shell script, it works great. But when I run "make
>> check" it doesn't call the shell script. It calls the .exe file, and
>> that fails:
>
> I see that you failed to identify the versions of autoconf, automake,
> and libtool you ar
When I call the shell script, it works great. But when I run "make
check" it doesn't call the shell script. It calls the .exe file, and
that fails:
I see that you failed to identify the versions of autoconf, automake,
and libtool you are using. Often it makes a difference, particularly
when
Howdy Automakers!
I have finally gotten my library to build under mingw on windows,
which is great, but there is a problem running the test programs.
For each test program, on windows I get both an exe file and a shell
wrapper.
For example, with the test program t_nc.c, which on unix will end up
In an autotools project, I recently moved sourcefiles into convenience
libraries, because the number of sourcefiles was getting rather large.
Before this reorganisation, the binary size of the resulting (stripped)
executable was about 800KB.
But after I moved about 50% of the total sourcecode in
