Brad King wrote: > On 11/12/2013 09:40 AM, Brad King wrote: >> The compile feature tests are basically doing the same kind of tests >> as the compiler id, so the same approach should work. > > Note that the Modules/CompilerId/* project files do have some content > specific to the compiler id step. Therefore a separate set should > be used for this feature. > > I suggest the following steps: > > 1. Revert the target_compile_features topic until this is resolved.
Done. Rebased to master and pushed to my clone. > 2. Create a new topic that adds a *test* in which you build the > new infrastructure. (This way all the trial and error will be > isolated to a single test and other topics can proceed without > interference.) > > 3. Once the test works everywhere, the actual infrastructure can > be ported over to the Modules directory and the test can just > exercise it. I'm not claiming these tasks, so they're up for grabs (Eike?). I'm refocusing on cross-compiling-toolchain-variables, because for me it is a higher priority to get that "done done". I also have other topics which can be done in parallel, but I'll defer them until that topic is in to eliminate distraction (at least as far as it comes from me :) ). Thanks, Steve. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
