There are projects which have include files outside the current source directory. For example if the project has an include and an src folder, and the current CMake file is in the src folder.
In these cases, the pch file has to be referenced as ../include/pch.h.
While this works with the FORCEINCLUDE option (it doesn't without that), it also creates files outside the _pch_binary_dir.
I think the best approach to resolve this would be the addition of another optional parameter, PCH_PATH, such as:
There are projects which have include files outside the current source directory. For example if the project has an
includeand ansrcfolder, and the current CMake file is in thesrcfolder.In these cases, the pch file has to be referenced as
../include/pch.h.While this works with the
FORCEINCLUDEoption (it doesn't without that), it also creates files outside the_pch_binary_dir.I think the best approach to resolve this would be the addition of another optional parameter,
PCH_PATH, such as:Most likely this parameter should be required if the header path starts with "..", or if it an absolute path.
This would solve both this issue, and the other I reported.