The following issue has been SUBMITTED. ====================================================================== http://cmake.org/Bug/view.php?id=12944 ====================================================================== Reported By: starseeker Assigned To: ====================================================================== Project: CMake Issue ID: 12944 Category: Modules Reproducibility: always Severity: feature Priority: normal Status: new ====================================================================== Date Submitted: 2012-02-07 20:36 EST Last Modified: 2012-02-07 20:36 EST ====================================================================== Summary: Feature enabling the CheckC*.cmake macros to use a path to source code as well as supplied source code Description: We often have our own .c file stored in our tree for TRY_RUN testing, and it is convenient to be able to use CHECK_C_RUNS_SOURCE for testing those .c files. At the moment, CHECK_C_RUNS_SOURCE assumes the incoming SOURCE variable actually holds the source code - our enhancement checks to see if SOURCE holds a valid file path first. If it DOES hold a valid file path, TRY_RUN then trys that .c file, otherwise the existing CHECK_C_RUNS_SOURCE is preserved. I don't know of any sane pathname that would be valid C code or vice versa, so there should be no danger of passing in a C source snippit and having it mistaken for a file path.
Additional Information: http://www.cmake.org/pipermail/cmake/2012-January/048921.html ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2012-02-07 20:36 starseeker New Issue 2012-02-07 20:36 starseeker File Added: 0001-Teach-CheckC.-modules-to-use-a-source-file-as-well-a.patch ====================================================================== -- 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
