default_cmake

[Dennis Veatch]

On Monday 23 March 2009 3:21:09 pm Auke Kok wrote:
> Dennis Veatch wrote:
> > I take it you refer to the change in the run_build function. You are
> > right, only if there is a CMakeLists.txt file. That seemed the simplest
> > way to determine which default build to run. ATM, I don't see another way
> > to determine how to detect when either default build should be run. I am
> > trying to keep this on a kiss level, so If you have something clever in
> > mind please point me in that direction.
> >
> > Unless you are referring to the default_cmake_build function, where it
> > runs the default_cmake function. Maybe that really should be called
> > default_cmake_config, since it is doing a similar thing the
> > default_config does.
>
> just change the order around: attempt to do a default_build first, and
> if that fails (configure/Makefile are missing) scan for CMake junk...
>
> Auke
> _______________________________________________

Here is the patch with things reversed, looks for default_build then the cmake 
"junk" :)

Tested with units and physfs.
-- 
You can tuna piano but you can't tune a fish.

http://www.lunar-linux.org/
It's worth the spin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: default.cmake.function.ver-5.patch
Type: text/x-patch
Size: 1089 bytes
Desc: not available
URL: <http://foo-projects.org/pipermail/lunar-dev/attachments/20090323/e08f16de/attachment-0001.bin>