>The thread-safe library w/ the C++ wrappers is not a supported configuration. >This is enforced >when built with the autotools, where --enable-unsupported must be used if you >want this >combination. We've been slowly bringing CMake into line with the more official >autotools build >options and preventing C++/thread-safe was a part of that.
Thanks for the information Dana. I was not aware of this limitation. > If you want to build this combination with CMake, you can edit the top-level > CMakeLists.txt file. > The salient bits are near line 715. Keep in mind that this is an untested and > unsupported > combination. Ok. Then I will attempt to modify CMakeLists.txt and take my chances on the unsupported configuration. > The biggest potential problem is that the thread-safe locking mechanism that > we use does not > extend into the C++ wrappers. Addressing this is a fairly high-priority task > for us. Pending > funding, we'd like to get it into the library as soon as possible. This sounds a bit odd to me. There is usually no need to thread-safe a thin "wrapper"-library separately if the underlying library is already thread-safe. Are there some specific problems that I should be aware of, like e.g. shared state between C++ objects or deadlocks? _______________________________________________ Hdf-forum is for HDF software users discussion. Hdf-forum@lists.hdfgroup.org http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
