On Mon, Feb 21, 2011 at 9:11 PM, David C. Rankin
<drankinatty@...> wrote:
<snip>
>  I apologize if this is all basic stuff, but I don't know cmake. To help
> Trinity move things to cmake, I need to learn.
<snip>

Don't apologize, we all need to start somewhere. Stupid questions
don't come from beginners, they come from experts. A question that is
simple and obvious to an expert would be stupid coming from an expert,
but isn't stupid at all from a beginner, so ask away and don't feel
stupid in the least! (just don't ask me, I know nuthin'! ;-) )

>  If we can come up with a coherent 'recipe' for moving modules to cmake, I'm
> more than happy to write the wiki. From #trinity-desktop on freenode, I take it
> samelian is the goto guy on the CMakeLists.txt. It seems if we can put a bit of
> effort into coming up with this recipe, then we can multiply by tenfold the
> number of monkeys typing the recipe into a keyboard for other trinity-modules.

"More than happy sounds like a dangerous mental condition. 'We had to
put Dave in the mental home... he was more than happy.'" --George
Carlin

(NOT picking on David lol, George actually used the name "Dave" in the
above quote, look up George Carlin Everyday Expressions on youtube)

>  What say the experts on putting some type of recipe together?

I think that's what Samelian was working on with that link. With just
two devs (one of which doesn't know much about cmake), it could take
awhile to get the "recipe" together. We also need to keep in mind that
each package is going to have some specific options that won't work in
all packages... some options might work in a few packages, or maybe
just one, so the person doing each specific package would need to
figure out those.

-- 
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager