| Adding a custom build step to a managed project [message #113003] |
Wed, 28 July 2004 19:43 |
Eclipse User |
|
|
|
Originally posted by: fake.email.address
I've just started using CDT, and I have a need to extend the build
process. We're using CxxTest (a simplified CppTest-like framework) for
unit testing. The way it works is that you put your unit test classes
in header files that you run through a Perl script, and this Perl script
generates the driver code (including the main() function) that runs the
tests.
I suppose what would be best is if we had a naming convention for our
tests (like TestName.test.h), and then CDT would automatically run all
the .test.h files through the Perl script as part of the build, which
then generates the appropriate .cpp file that needs to be added to the
project and compiled.
I thought that writing a tool extension using the ManagedBuildInfo
extension point would be the right course of action, but I haven't
managed to get anything to work so far. The catch is that it seems like
tools generate one output per one input, but what we need is to be able
to pass -all- the .test.h files to the Perl script at once, and this
generates a single .cpp file as a result.
It's clear how to do this in a makefile, but we would like to be able to
automate it using CDT's managed makefile projects. Can anyone offer any
advice or a push in the right direction? The documentation is somewhat
sparse as far as tutorials go, so I'm having trouble figuring out just
where to start.
Thanks!
--
Tony
|
|
|
Powered by
FUDForum. Page generated in 0.03043 seconds
Home