[Cmake] Modifying the .dsptemplate files

[Ian Scott]

The sort of configurations I want to use right now are

Debug (Use static standard libraries)
Release (Use static standard libraries)

I suspect we would also want to add the following at some point;

Release (Use static standard libraries) with debug information
Release (Use static standard libraries) with inlining turned off and
profiling enabled.

So I guess the answer is that whilst I only have a limited set of required
configurations, in general there are more options that is reasonable to hard
code into cmake. For example, at Manchester we would also be interested in
using it to build some QT code. This would require the custom build options
to be enabled in the DSP files. Mind you this would probably require
modification of the CMake code itself.



Ian.


> -----Original Message-----
> From: Bill Hoffman [mailto:bill.hoffman at kitware.com]
> Sent: Tuesday, May 01, 2001 4:57 PM
> To: Ian Scott; cmake at public.kitware.com
> Subject: Re: [Cmake] Modifying the .dsptemplate files
>
>
> Are the VXL configurations that special to VXL?  If you want
> to add useful
> configurations, they could be added to CMake.
>
> Our future plans include a binary installation of CMake so CMake does
> not have to be part of the source tree being built.
> However, I sort of
> thought that we could make one configuration set that would fit all.
>
> -bill
>
>
>
> At 04:50 PM 5/1/2001 +0100, Ian Scott wrote:
> >I would like to add some extra build configurations to the
> CMake output for
> >VXL. It appears that this is straight forward to do, by
> simply modifying my
> >local versions of
> >CMake\Source\*.dsptemplate
> >
> >I have therefore two questions.
> >
> >1. Is the hand modification of .dsptemplate part of the
> intended interface.
> >This would (in the longer term) mean that the syntax of the template
> >substitution markers would be published in the documentation.
> >
> >2. Would it be possible to move the standard location of these files,
> >somewhere outside the CMake source tree. In particular I
> would like to put
> >somewhere it at the root of the VXL source tree, so that our modified
> >version can be put under our CVS control. A slightly fancier
> solution would
> >be to search up the directory tree from the current
> directory, and only if
> >they haven't been found there, to use the ones in the CMake
> source tree.
> >
> >
> >Regards,
> >Ian Scott.
> >--------------------------------------------------------------
> >Ian Scott               BT/Royal Commission Industrial Fellow
> >Dept. of Imaging Science                ian.m.scott at stud.man.ac.uk
> >Stopford Building                                 tel: +44
> (0)161 275 7357
> >University of Manchester                  fax: +44 (0)161 275 5145
> >                            http://www.isbe.man.ac.uk/~iscott/
> >
> >
> >
> >_______________________________________________
> >Cmake mailing list
> >Cmake at public.kitware.com
> >http://public.kitware.com/mailman/listinfo/cmake
>