On Wed, Feb 11, 2009 at 1:03 AM, Tyler Roscoe <ty...@cryptio.net> wrote:
> Bumping this one time. Any thoughts? Is there a better place to ask this > sort of question? Sorry, my eyes glazed over the first time I read this sentence and I think I was pretty tired so not knowing what these acronyms went I think I just archived the thread. > OTOH, it would be nice to gain some of the benefits of TDD (e.g., > fearless refactoring) in the build system > One approach I've thought of is a simple script that simply makes > > sure that each CMake project deposits an expected list of files in a > > certain place. I have a hierarchy of "buildables" so it might be nice to > > know that the header at the bottom of the dependency tree is built > > correctly, and that the libraries that use it find that header and build > > correctly, and that the executable that use those libraries find > > everything and build correctly. > > > > Does anyone do anything like this? Are there tools around to help? Is > > this a worthwhile thing to think about? > If you want to guarantee your library works externally as shipped you could effect a "make install" and then build your test code against the "make installed" copy of the library. I'm not sure how many issues you'd discover this way though, perhaps the occasional header file someone forgot to add to the INSTALL list if your unit tests are good enough? Not sure if it would be worth it. -- Philip Lowman
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
