Hello David,
It didn't worked. I end up passing -wno-cpp to the cmake flags to finally
get over this issue.
I don't get how CTEST_CUSTOM_WARNING_EXCEPTION works.
How does this compare the regex when it gets a warning?
How do I disable all warnings from a directory? eg:
So using *.#warning.*deprecated.* should work?
I will test this and let you know.
On Thu, Nov 5, 2015 at 4:49 PM, David Cole wrote:
> Looks to me like it might be (I'm hopeful) working at ignoring the
> line which matches the expression ".*vcl_deprecated_header.h.*" ...
>
>
Does your ctest -S script call ctest_read_custom_files
https://cmake.org/cmake/help/v3.4/command/ctest_read_custom_files.html
after ctest_configure?
On Thursday, November 5, 2015, Rashad M wrote:
> Hello all,
>
> I have CTestCustom.cmake.in file in source tree with
Hello all,
I have CTestCustom.cmake.in file in source tree with the following contents
https://git.orfeo-toolbox.org/otb.git/blob/refs/heads/develop:/CMake/CTestCustom.cmake.in
during ctest build CTestCustom.cmake file is getting generated inside the
build tree.
But however the warnings are
Looks to me like it might be (I'm hopeful) working at ignoring the
line which matches the expression ".*vcl_deprecated_header.h.*" ...
But then, the following line is:
# warning "deprecated"
Since that line does not match any of your expressions, maybe that's
the one triggering this
yes.
On Thu, Nov 5, 2015 at 1:46 PM, David Cole wrote:
> Does your ctest -S script call ctest_read_custom_files
> https://cmake.org/cmake/help/v3.4/command/ctest_read_custom_files.html
> after ctest_configure?
>
>
> On Thursday, November 5, 2015, Rashad M