Thanks ... a test-tool is exactly the same as a tool; the only
difference is that 'make install' does nothing. :-)
So it's standard stuff --
include $(GNUSTEP_MAKEFILES)/common.make
TEST_TOOL_NAME = test
test_OBJC_FILES = foo.m
include $(GNUSTEP_MAKEFILES)/test-tool.make
At which point, 'make' will compile the tool.
Thanks
PS: 'make test' will work too, gnustep-make will recognize 'test'
as the name of one of the tools and will compile that one.
-Original Message-
From: "Sheldon Gill" <[EMAIL PROTECTED]>
Sent: Wednesday, September 20, 2006 3:47 pm
To: "Developer GNUstep"
Subject: Compiling and running a test tool
Hi,
I can compile and run a test tool consisting of a single source file by
invoking "make test" using a GNUmakefile like this
include $(GNUSTEP_MAKEFILES)/common.make
foo_OBJC_FILES=foo.m
include $(GNUSTEP_MAKEFILES)/test-tool.make
test:
./obj/foo
which is pretty sweet. Trouble is, how do you extend this to a test tool
which
is spread over multiple source files?
Or a test tool which depends on another tool build beforehand?
The obvious thing to try was:
thing_OBJC_FILES=foo.m bar.m
include $(GNUSTEP_MAKEFILES)/test-tool.make
test:
./obj/thing
but that doesn't work at all. Changing that depends to
test: thing
means it will all compile and link sweetly but won't be run.
It's getting late and my brain is slow.
Help anyone?
Regards,
Sheldon
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev