William A. Hoffman wrote:
At 08:28 AM 6/12/2006, Brandon J. Van Every wrote:You know I spoke too soon. Once I changed that, I started getting semicolons in new places *inside of* quoted strings. There is a general problem of semicolons, double quotes, and spaces in filenames beating each other up, as they are passed around between lists and strings and replacements are performed. A list of defines like the following is highly problematic: I *am* configuring a file. CONFIGURE_FILE doesn't offer regex replacement, so I have to use a CMake script to do it. This is about extracting the results of ADD_DEFINITIONS, passing the results to a CMake script, then configuring a file. I'd love it if CONFIGURE_FILE had more replacement capabilities, but when I made that post last week, crickets chirped. You will like the philosophy of the consuming tool. csc.exe generates all these flags for you so that you don't have to do it on the comamand line. :-) Cheers, Brandon Van Every |
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
