-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Alan,
Many thanks for all your help. I've finally understood what's going on.
A rather important misunderstanding on my part was that cmake has no
control over how the Kbuild makefile places files! *slaps forehead*.
There is just one remaining "is
On 2007-08-16 15:18+0100 Tim Schooley wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all!
[My first post, please bear with me...]
I've been porting a Makefile project to use CMake. Thankfully, it's gone
very smoothly, and now I'm just trying to iron out some ripples. CMake
truly rock
On Thursday 16 August 2007 10:18, Tim Schooley wrote:
> Hi all!
>
> [My first post, please bear with me...]
>
> I've been porting a Makefile project to use CMake. Thankfully, it's gone
> very smoothly, and now I'm just trying to iron out some ripples. CMake
> truly rocks.
>
> I found some advice on
Tim Schooley wrote:
Unfortunately, that's right, but at least "make pristine" or "make
mrproper" is somewhat conventional as a "cleaner-than-clean" target.
True. I should probably do this, as I'm sure there will be other outputs
that need manual cleaning (doxygen stuff and test result files).
Tim Schooley wrote:
My second problem: I'm aware that you currently cant add custom commands
to the "clean" target, but is there _any_ way of cleaning up the kernel
module source directory when "clean" is called, even if it's a slightly
nasty hack ?
Do an ADD_CUSTOM_TARGET for something like `m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all!
[My first post, please bear with me...]
I've been porting a Makefile project to use CMake. Thankfully, it's gone
very smoothly, and now I'm just trying to iron out some ripples. CMake
truly rocks.
I found some advice on this mailing list for
