I just tried to compile CUnit on the latest stable MinGW/MSYS, but failed. This was using the subversion head, at r134.
I found a workaround, by checking out the repo and creating the makefiles and configure script on Linux, then tarring it up and transferring to Windows.
It's really important that the tarball contains the configure script, so that people can more easily get started... or is there a compelling reason not to do that?
Anonymous
Can you list what kind of errors did you get. The only reason why configure is missing is that the entire build can be done on any linux/unix platform that supports autoconf/automake etc. The bootstrap script should be able to generate configure provided right set of tools are available on the platform.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Added configure and ltmain.sh scripts to the sources. Can you please try compiling again and let me know if this solves compilation issue ?
I tried this out just now on Windows 7 with 32-bit MinGW. I get the following output from "./configure" now, showing that we also need "config.sub" to be added to the sources:
$ ./configure
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
/home/john/ascend/cunit/missing: Unknown
--run' option Try/home/john/ascend/cunit/missing --help' for more informationconfigure: WARNING: `missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
---------- Disabling debug mode compilation.
++++++++++ Enabling automated(XML) mode compilation
++++++++++ Enabling basic mode compilation
++++++++++ Enabling console mode compilation
---------- Disabling curses mode compilation
---------- Disabling examples mode compilation
---------- Disabling test mode compilation
---------- Disabling memtrace functionality at compile time
---------- Disabling use of deprecated v1.1 names
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
configure: error: cannot run /bin/sh ./config.sub