On Tue, Apr 7, 2009 at 10:04 AM, John Drescher wrote:
>> But I don't really know what the users needs. Like for me I don't need
>> to pass any options. Others might have had to tweak things to
>> recognize a given library.
>>
>> I wonder if I could just run a find&replace regex on the
>> CMakeCach
On Mon, Apr 6, 2009 at 10:33 PM, Michael Jackson
wrote:
> I _think_ the way to do this in your script would be to use either one of:
>
> -C = Pre-load a script to populate the cache.
> -D := = Create a cmake cache entry.
>
> In the -C variant you would have a *.cmake file that has
On Mon, Apr 6, 2009 at 10:33 PM, Michael Jackson
wrote:
> I _think_ the way to do this in your script would be to use either one of:
>
> -C = Pre-load a script to populate the cache.
> -D := = Create a cmake cache entry.
>
> In the -C variant you would have a *.cmake file that has
I _think_ the way to do this in your script would be to use either one
of:
-C = Pre-load a script to populate the
cache.
-D := = Create a cmake cache entry.
In the -C variant you would have a *.cmake file that has all the
necessary entries in it that you want to set, or
I want to write a script that, in response to 'make distcheck', git
clones the source repo into a new directory under the build directory,
builds it and runs make test.
The issue is that if the user had to tweak their cmake settings to get
it to build thats not going to work, since the new build d
