Greetings to new members Filipe and Wesley

[E. Wing]

Just wanted to say hi to the two new members who joined our mailing
list. We're pretty low traffic right now, so feel free to say hello or
whatever ideas you might have for the project.

Thanks,
Eric

[Wesley Smith]

Hi Everyone,
I'm wes. I'm curious who all is on this list. I'm a PhD student at
UC Santa Barbara in the Media Arts and Technology program. Right now
I'm building the audiovisual software infrastructure for a number of
small -> large projects here. I'm essentially looking for a robust
build system that I can integrate into my audiovisual software which
uses Lua heavily. My goal is to have some high-level interfaces for
deploying and building audiovisual applications which tend to have
lots and lots of dependencies as well has supporting media files and
configuration scripts. It can be a mess to manage, especially since
I'm working on 3 platforms: OSX, Windows, Ubuntu.

I'm trying to get the source right now, but I get the following error:

blister:~/Documents/CMakeLua whsmith$ hg clone
http://hg.assembla.com/CMakeLua YourClone
Traceback (most recent call last):
File "/usr/local/bin/hg", line 11, in <module>
from mercurial import demandimport; demandimport.enable()
ImportError: No module named mercurial

I'm on OSX. Google hasn't been much help. Anyone have a clue?

thanks,
wes

[Wesley Smith]

PS.

The repo has a good number of files in it. Could I get a few pointers
to the key files where the bindings take place? Also perhaps a
description of the general repo layout? This would really help me get
into it.

best,
wes

[E. Wing]

> I'm trying to get the source right now, but I get the following error:
>
> blister:~/Documents/CMakeLua whsmith$ hg clone
> http://hg.assembla.com/CMakeLua YourClone
> Traceback (most recent call last):
> File "/usr/local/bin/hg", line 11, in <module>
> from mercurial import demandimport; demandimport.enable()
> ImportError: No module named mercurial
>
> I'm on OSX. Google hasn't been much help. Anyone have a clue?

Hmmm, I'm on OS X (Leopard) right now, but I can't reproduce your
problem. I used one of the Mercurial OS X installers to install.

Can you check your version? I think mine is one of the 0.95+patches releases.

$ hg --version

Mercurial Distributed SCM (version bc475d1f74ca)

Copyright (C) 2005-2007 Matt Mackall <m...@selenic.com> and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[E. Wing]

Yeah, good question. It's already fuzzy in my mind. All the CMake
source code is in Source/

I know for sure that:
cmGetPropertyCommand.cxx
cmMakefile.cxx have Lua stuff because I just resolved some merge conflicts.

I think cmCommand.cxx was very significant, probably where most of the
binding takes place. And cmake.cxx has a bunch of stuff too.

You can do a grep for lua in Source/ and probably find everything.

The middle-layer API-interface I introduced is called
LuaPublicAPIHelper.lua
and in the Modules/ directory.

And there is a simple test project in
Tests/LuaTest/
which has a CMakeLists.lua instead of CMakeLists.txt.

Thanks,
Eric

[E. Wing]

On 2/3/08, E. Wing <ewma...@gmail.com> wrote:
> > I'm trying to get the source right now, but I get the following error:
> >
> > blister:~/Documents/CMakeLua whsmith$ hg clone
> > http://hg.assembla.com/CMakeLua YourClone
> > Traceback (most recent call last):
> > File "/usr/local/bin/hg", line 11, in <module>
> > from mercurial import demandimport; demandimport.enable()
> > ImportError: No module named mercurial
> >
> > I'm on OSX. Google hasn't been much help. Anyone have a clue?
>

One more thought, maybe make sure your ~/.hgrc file is clean.

I also Googled for your error. It may be related to using 0.9.4. I
recommend upgrading if you're Mercurial version is not 0.9.5.

[Wesley Smith]

Yeah, I'm on Tiger. I installed mercurial from source. It seems to
no be able to find the mercurial module. I finally figured it out and
movde mercurial from usr/local/lib to
/Frameworks/python/..../site-packages blah blah blah. There's a
reason I don't like python :) Too bad CMakeLua isn't in a CVS or SVN
repo. Oh well. On with the show.

wes

[Wesley Smith]

Are you all patching the CMake source directly? I would discourage
this as much as possible. Even when I'm building C++ modules from
scratch I don't do this. My general strategy for making bindings is
to leave the source I'm binding completely free of Lua in order to
maximize compatibility with future updates. I make my bindings to C++
classes through inheritance or composition depending on the context.
Some examples are:

class Thing {};

class Thing_udata : public Thing {};

class Thing_udata {
Thing *m_thing;
//or Thing &m_thing;
//or const Thing& m_thing; it depends
};

I also use a userdata template to do alot of the work of the bindings.
I plan on making it a policy-based template, but for now it's all or
nothing. So a true binding would be

class Thing_udata : public Thing, public udata::Udata<Thing_udata>
{};

Anyway, I haven't gone very far in the source and I know very little
about CMake, so this may not apply here.

wes

[E. Wing]

The OS X installer packages are pretty nice. I admit, I hate
installers and almost never use them, but the complexity of
Mercurial is sufficient enough to warrant it.

Mercurial is the best tool for the job. CVS and SVN will never support
what we are doing.

You should see the infamous Linus Google Talk on Git:
http://www.youtube.com/watch?v=4XpnKHJAok8

Also good reference:
Bryan O'Sullivan on Mercurial:
http://www.youtube.com/watch?v=JExtkqzEoHY

Randal Schwartz also on Git:
http://www.youtube.com/watch?v=8dhZ9BXQgc4

On 2/3/08, Wesley Smith <wesle...@gmail.com> wrote:
>

[Wesley Smith]

The installers didn't work. For some reason they wouldn't let me
select my main hard drive. That's why I went with source. In any
case, I've got the repository on my system now. I'm reading up on
CMake.
wes

[Filipe Sousa]

Hi Eric, I'm Filipe Sousa and I have been using cmake since 2003. Lua is
a fantastic language (but not my favorite) for things like this. Lets
hope this can make cmake better.

It's time to learn lua again, my last contact with lua was with version
4.x (i think)

--
Filipe Sousa