Spliting atomic test compilation from library compilation
do we split creation of the lib and atomic test.
- when you want to integrate a new feature in lib A you can progress in your work without getting blocked by atomic test not already updated by your work. Instead of modifying the cmakefile of lib A to avoid compilation of atomic test you just comment the line here => more clean
- separate cmakefile : there is no more stuff needed by atomic test in cmakefile of the library => more clear
- this may induce bad practice : never run atomic test ever and commit feature which are not compatible