Hi,
I have CMake modules that can share resources between different
instances. For now I manage it by invoking `mkdir
<shared-dir>/lock-directory` and checking the result, then removing this
directory so the next instance can do the modification. The problem
occurs when somebody terminate CMake. Since I can't set handler (e.g.
SIGINT) to CMake, directory will not be removed and will be "locked"
forever.
So it can't be resolved without some low-level management. I'm thinking
about `file` command sub-option like LOCK_DIRECTORY:
`file(LOCK_DIRECTORY "/path/to/shared-dir")`. Does it sounds doable?
Thanks, Ruslo
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
