I got PortMidi to build and run on Linux today and just put new release 
files on SourceForge. The major change is that CMake is now used to 
build Makefiles and project files for Win32 and Xcode, and libraries are 
named with _s and _d for static and dynamic because otherwise library 
selection can be ambiguous in Xcode.

Probably there will be some snags here and there, so please report any 
problems. There's an opportunity now to unify the build files for MinGW, 
FreeBSD, and other systems through relatively small changes to the CMake 
files.

In retrospect, I'm not sure the CMake conversion was worth it. On the 
plus side, there will be no more fiddling with project files trying to 
get them to be consistent with flags, etc., and one can easily support 
parallel sets of projects and Makefiles. On the down side, while CMake 
can generate Makefiles and project files, it's really using these in 
very non-standard ways that are hard to understand. Also, while Xcode 
and Visual C++ projects can be made to be portable to different machines 
and directories, CMake wires in full paths. I wrote some awk scripts to 
strip out a lot of CMake "extras" and insert relative path names. I 
think this is all working now, but what a pain.

-Roger

_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api

Reply via email to