[CMake] CMAKE_USE_PTHREADS_INIT cleanup

I recently added pthreads to my cmake program. When I run valgrind, I get a "blocks still reachable" warning, coming from dl_init. I suspect that pthreads is not cleaning up properly. Is there a way of ensuring that the shared library for pthreads gets cleaned up correctly via cmake? i.e. a

Re: [CMake] CMAKE_USE_PTHREADS_INIT cleanup

On Sun, Mar 20, 2016 at 8:46 AM, Aaron Boxer wrote: > I recently added pthreads to my cmake program. > When I run valgrind, I get a "blocks still reachable" warning, > coming from dl_init. > > I suspect that pthreads is not cleaning up properly. Is there a way > of ensuring

[CMake] How to suppress valgrind errors reported by NightlyMemCheck ?

My program links to libstdc++. It turns out there is a well-known false positive from valgrind regarding libstdc++ memory pools. http://valgrind.org/docs/manual/faq.html#faq.reports How may I suppress this error when running ctest -D NightlyMemCheck ? Thanks, Aaron -- Powered by

Re: [CMake] How to suppress valgrind errors reported by NightlyMemCheck ?

Hi Xavier, On Sun, Mar 20, 2016 at 1:50 PM, Xavier Besseron wrote: > Hi Aaron, > > I don't know if that's what you're looking for, > but you can try to set Valgrind options using an environment variable or > a cmake variable > > set(VALGRIND_OPTS

Re: [CMake] find_package REQUIRED ignores OPTIONAL_COMPONENTS

On Tuesday 08 March 2016, 10:00:00 wrote Nicholas Braden: > Jakob, I don't think there is any confusion about what REQUIRED means. > Whether or not REQUIRED is provided, the list of OPTIONAL_COMPONENTS > should not be required under any circumstances. The example error > message seems pretty clear

[Cmake-commits] CMake branch, master, updated. v3.5.0-268-gbbab373

_VERSION_MINOR 5) -set(CMake_VERSION_PATCH 20160320) +set(CMake_VERSION_PATCH 20160321) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, master, updated. v3.5.0-238-gf5eda70

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via f5eda7069027790a73f2e7f72d81bd5c0db46eae (commit) via

Re: [cmake-developers] Using CMake generated ninja file as a subninja file

On Wed, Mar 9, 2016 at 9:41 PM, Ben Boeckel wrote: > On Tue, Mar 08, 2016 at 12:36:31 +0100, Nicolas Desprès wrote: > > Did you have a chance to review my patches? > > So I looked at it today, and it looks good overall. A few niggles: > Thanks > > +inline bool

Re: [cmake-developers] Patch to only consider build dependencies between files in the source directory

Brad's point with "/" or null terminator was that the directory name **must** be the directory itself, or a sub-directory of the one in question. i.e. if it's "my/src" then it should either be exactly "my/src" or "my/src/someSubDir" , not "my/srcSiblingDir" On Fri, Mar 18, 2016 at 11:52 AM,

[cmake-developers] [CMake 0016026]: CMake provides no reliable variable for 'the file a function is declared in'

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=16026 == Reported By:Stephen Kelly Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.0-517-gbd79937

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via bd7993730e2f96e8899a1670ccfe71744e1f5c90 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-472-g50c0287

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 50c0287ee22e19da6a6c4fb5c9e5ed752e717073 (commit) via