Andreas Pakulat wrote:
On 26.03.08 18:35:27, Matthew Woehlke wrote:
Andreas Pakulat wrote:
On 26.03.08 17:25:58, Matthew Woehlke wrote:
In addition, I'm used to environment variables being all-caps. Is
FindBoost intentionally deviating here, or was this a
search-and-replace oops? If not, how would people feel about
applying this?
Thats intentional as per the cmake module documentation. That suggest to
use the same capitalization as for the part between "Find" and ".cmake".
...for CMake variables, this is true, and I already knew that. I'm not
sure how much sense applying it to *environment* variables makes,
however, as I believe those are traditionally all-caps.
Wow, huge cross-posting (just noticed it now).
Well, I wasn't sure who would care :-). kdevelop owns the one I'm
fiddling with, but cmake probably cares and k-c-d might also. I took out
k-c-d for now, though.
Hmm, actually you're right. I guess either I was confused when I wrote
the module or I just wanted everything to look the same :)
Search-and-replace error indeed. Thought that might be it ;-).
Will change that tomorrow when I work on the FindBoost.cmake for CMake
2.6
Ok, thanks. (At which point I'll have conflicts; whee! But that's ok ;-).)
--
Matthew
I'm anti-ascii. Probably because I once worked with a guy who sent EVERY
BLOODY DESIGN SCHEMA as an ascii art thing. A year into that job and I
just about wanted to punch him in the head with an ascii fist. He
totally ruined ascii porn for me even. -- Aaron Seigo
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
