On 9/24/06, Joël Vennin <[EMAIL PROTECTED]> wrote:

This macro is a copy of the original CMake macro, however, the detection of
SWIG depends on a valid distribution architecture. So, my SWIG location is
not standard, and the default macro is unable to detect SWIG.

Same here, except that mine is in /usr/local. And we'll have more
problems once SWIG 1.3.30 is released. Maybe we can change the macro
to use a more reliable method of detecting SWIG?


You're right that is really faster, we can do interesting thing using CMake,
even if I'm not a CMake expert, I'm sure that we can compile all adonthell
related stuff.

I've got some linking issues on OS X, but otherwise it works really
good. When I find the time, I'll have to compare the autotool link
command with the cmake-generated one and figure out what the
difference is. From there, a fix should be straightforward.


Regarding the problems on Windows, I've started a thread on the cmake
mailing list: 
http://public.kitware.com/pipermail/cmake/2006-September/011296.html
Not sure what will come of it; don't think they will change the way
cmake works for us, but one guy was extremely helpful. He sent me a
.cmake macro that uses pkg-config to obtain all the information we
need. I expect that to work much better, as a lot of the packages
cmake fails to find provide a .pc file:

   $ ls /usr/local/lib/pkgconfig/
   freetype2.pc   libpng12.pc    ogg.pc         vorbis.pc      vorbisfile.pc
   libpng.pc      libxml-2.0.pc  sdl.pc         vorbisenc.pc

I guess I will update the CMakeList.txt files in a way that pkg-config
becomes a fallback if the default find* mechanism fails (or the other
way round). That should give us maximum compatibility.

So I don't think that there is more need to harass cmake people with
this specific issue. At least they seem to be a fairly helpful bunch,
and fast to respond too :-)

Kai


_______________________________________________
Adonthell-devel mailing list
Adonthell-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/adonthell-devel

Reply via email to