diff --git a/src/ysclass/src/CMakeFiles b/src/ysclass/src/CMakeFiles deleted file mode 100644 index fa775f6..0000000 --- a/src/ysclass/src/CMakeFiles +++ /dev/null @@ -1,8 +0,0 @@ -This file prevents accidental in-source build from this directory. - -What's horrible about cmake is if I accidentally type cmake where CMakeLists.txt exists, cmake happily considers it as an in-source build, and contaminate the directory with the build-related files. There seems to be no way of preventing accidental massive file contamination. Just one mistake is enough. It's as bad as accidental "rm -r *", because a lot of "rm -r something" follows to de-contaminate the source directory. - -However, cmake needs to create a directory called CMakeFiles to set up build-related files. It stops after creating CMakeCache.txt. - -Probably, creating a directory called CMakeCache.txt is also as effective. - diff --git a/src/ysgebl/src/gui/CMakeFiles b/src/ysgebl/src/gui/CMakeFiles deleted file mode 100644 index fa775f6..0000000 --- a/src/ysgebl/src/gui/CMakeFiles +++ /dev/null @@ -1,8 +0,0 @@ -This file prevents accidental in-source build from this directory. - -What's horrible about cmake is if I accidentally type cmake where CMakeLists.txt exists, cmake happily considers it as an in-source build, and contaminate the directory with the build-related files. There seems to be no way of preventing accidental massive file contamination. Just one mistake is enough. It's as bad as accidental "rm -r *", because a lot of "rm -r something" follows to de-contaminate the source directory. - -However, cmake needs to create a directory called CMakeFiles to set up build-related files. It stops after creating CMakeCache.txt. - -Probably, creating a directory called CMakeCache.txt is also as effective. - diff --git a/src/ysgebl/src/kernel/CMakeFiles b/src/ysgebl/src/kernel/CMakeFiles deleted file mode 100644 index fa775f6..0000000 --- a/src/ysgebl/src/kernel/CMakeFiles +++ /dev/null @@ -1,8 +0,0 @@ -This file prevents accidental in-source build from this directory. - -What's horrible about cmake is if I accidentally type cmake where CMakeLists.txt exists, cmake happily considers it as an in-source build, and contaminate the directory with the build-related files. There seems to be no way of preventing accidental massive file contamination. Just one mistake is enough. It's as bad as accidental "rm -r *", because a lot of "rm -r something" follows to de-contaminate the source directory. - -However, cmake needs to create a directory called CMakeFiles to set up build-related files. It stops after creating CMakeCache.txt. - -Probably, creating a directory called CMakeCache.txt is also as effective. - diff --git a/src/ysgebl/src/kernelutil/CMakeFiles b/src/ysgebl/src/kernelutil/CMakeFiles deleted file mode 100644 index fa775f6..0000000 --- a/src/ysgebl/src/kernelutil/CMakeFiles +++ /dev/null @@ -1,8 +0,0 @@ -This file prevents accidental in-source build from this directory. - -What's horrible about cmake is if I accidentally type cmake where CMakeLists.txt exists, cmake happily considers it as an in-source build, and contaminate the directory with the build-related files. There seems to be no way of preventing accidental massive file contamination. Just one mistake is enough. It's as bad as accidental "rm -r *", because a lot of "rm -r something" follows to de-contaminate the source directory. - -However, cmake needs to create a directory called CMakeFiles to set up build-related files. It stops after creating CMakeCache.txt. - -Probably, creating a directory called CMakeCache.txt is also as effective. - diff --git a/src/ysgebl/src/main/CMakeFiles b/src/ysgebl/src/main/CMakeFiles deleted file mode 100644 index fa775f6..0000000 --- a/src/ysgebl/src/main/CMakeFiles +++ /dev/null @@ -1,8 +0,0 @@ -This file prevents accidental in-source build from this directory. - -What's horrible about cmake is if I accidentally type cmake where CMakeLists.txt exists, cmake happily considers it as an in-source build, and contaminate the directory with the build-related files. There seems to be no way of preventing accidental massive file contamination. Just one mistake is enough. It's as bad as accidental "rm -r *", because a lot of "rm -r something" follows to de-contaminate the source directory. - -However, cmake needs to create a directory called CMakeFiles to set up build-related files. It stops after creating CMakeCache.txt. - -Probably, creating a directory called CMakeCache.txt is also as effective. - diff --git a/src/ysport/src/CMakeFiles b/src/ysport/src/CMakeFiles deleted file mode 100644 index fa775f6..0000000 --- a/src/ysport/src/CMakeFiles +++ /dev/null @@ -1,8 +0,0 @@ -This file prevents accidental in-source build from this directory. - -What's horrible about cmake is if I accidentally type cmake where CMakeLists.txt exists, cmake happily considers it as an in-source build, and contaminate the directory with the build-related files. There seems to be no way of preventing accidental massive file contamination. Just one mistake is enough. It's as bad as accidental "rm -r *", because a lot of "rm -r something" follows to de-contaminate the source directory. - -However, cmake needs to create a directory called CMakeFiles to set up build-related files. It stops after creating CMakeCache.txt. - -Probably, creating a directory called CMakeCache.txt is also as effective. -