Might I make a suggestion? I manage a few rather large cross platform projects which include embedded targets, Windows OS w/ multiple Visual Studio targets (2003, 2005, and 2008), and some Linux flavors. In the past we hand built all the makefiles and manually maintained the Visual Studio project / solution files, which has always been a pain. Recently we've made a successful partial migration to a CMake driven environment. This lets us manage one set of quasi-make text files, and CMake does a surprisingly nice job of generating VS2003 and VS2005 project / solution files along with our Linux and other target make files. We've had some success adding other related automations like doxygen configs that get passed the per-library source file lists. CMake even lets us generate source / header folders within the Visual Studio projects so we could maintain the way we previously organized our larger libraries. That said, going on the assumption that nobody will want to migrate to yet another build system (I know I would resist such a suggestion), CMake would at the very least provide a very clean way of generating the VS2003/VS2005 project solution files from a simple set of text files which could be maintained along with the basic make files. I know from experience that once created, they're pretty easy to keep in sync. I'm guessing that VS2008 support should be here soon, if not already. I'll be looking into the build issue a little more tomorrow, and I'm glad to help here. I'll be managing speex in our project from this point on, and while VS2005 isn't our only target, its the one that pays the bills, so I have to make it build clean. Kerry
Kerry Bonin wrote:> Recently we've made a successful partial migration to a CMake driven > environment.I've looked at Cmake and I was completely underwhelmed. The autotools are very flawed, but in my opinion they are still far more capable than Cmake.> That said, going on the assumption that nobody will want to migrate to > yet another build system (I know I would resist such a suggestion), > CMake would at the very least provide a very clean way of generating the > VS2003/VS2005 project solution files from a simple set of text files > which could be maintained along with the basic make files.I know of one other project doing this, but its too early to tell if its going to work out or not. Erik -- ----------------------------------------------------------------- Erik de Castro Lopo ----------------------------------------------------------------- "Data is not information, Information is not knowledge, Knowledge is not understanding, Understanding is not wisdom." -- Clifford Stoll
Please note that I'm not advocating CMake as a replacement for autotools or another build environment - what I was postulating is that CMake may provide an easier to maintain option for generation of Visual Studio project and solution files, which unless I'm mistaken the GNU autotools suite does not support. Used in this manner they provide the ability to generate these for at least VS2003 and VS2005 from a make style text file, which could probably be generated by autotools with a little work. This would be an easier option for generating these project files than cranking them out by hand, which I suspect is how they have been maintained. I should add that not too many developers I know attempt cross platform that includes Visual Studio, but CMake is the ONLY tool I've tried that has been able to generate both Visual Studio and Linux make files of sufficient quality to be used in a production environment. There may be lots of better choices for a Linux / embedded house, but CMake is a nice solution in this particular niche. I'll spend a little time on this next week and see what I can come up with. On a tangentially related issue, could Jean-Marc (or someone else in the know) comment on the status and future of the Git > Xiph SVN updating? It would be nice if this were maintained for those of us stuck with managing speex in a larger project already in SVN. It seems it wouldn't be difficult to automate this, but Xiph certainly seems like the proper home for the updated SVN... Kerry Erik de Castro Lopo wrote:> Kerry Bonin wrote: > > >> Recently we've made a successful partial migration to a CMake driven >> environment. >> > > I've looked at Cmake and I was completely underwhelmed. > > The autotools are very flawed, but in my opinion they are still > far more capable than Cmake. > > >> That said, going on the assumption that nobody will want to migrate to >> yet another build system (I know I would resist such a suggestion), >> CMake would at the very least provide a very clean way of generating the >> VS2003/VS2005 project solution files from a simple set of text files >> which could be maintained along with the basic make files. >> > > I know of one other project doing this, but its too early to tell > if its going to work out or not. > > Erik >