On Saturday, June 20, 2015 11:29:46 Stephen Kelly wrote:
Brad King wrote:
snip
I recommend the following guidelines:
1) Policies need to result in errors in a short timeframe. They are not
something to ignore for years, because allowing that makes them feature
toggles. Alex won't be
Hi,
There is a bug in CMake's export file generator where it does not
correctly escape Windows paths when generating export files . This was
originally reported on the LLVM mailing list [1]. I'm using CMake
3.2.3.
In a generated export file I see
```
# Create imported target LLVMDebugInfoPDB
Does anyone have a configuration for astyle which indents my code according to
the CMake coding rules? Would make my life much easier right now.
Directions where I can find a complete set of rules how the code should be
formatted would also suffice.
best regards
Michael Stürmer
--
Powered
Hi Brad,
Apologies for taking a little while with this. I've addressed those
points and added all the tests I think are appropriate for this, however
when I run one of them it fails because stderr is not as expected, but
the actual and expected values are identical. Why would this happen?
On 06/22/2015 03:36 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
Directions where I can find a complete set of rules how the
code should be formatted would also suffice.
We don't have it formally documented anywhere. Basics:
* 79 columns or less (only one that is enforced with a test)
* indent
Thanks, I think this should be enough for me to configure the visual studio
plugin accordingly.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Monday, June 22, 2015 3:43 PM
To: Stuermer, Michael SP/HZA-ZSEP; cmake-developers@cmake.org
Subject: Re:
