lol c++20 modules IF users use them modules is just pain in
the ass for developers I hope that real developers will simply ignore
them headers are here for a good reason, and stupid languages like
python that use modules are just stupid it will make more
complicated for
The history behind the makefile generator and the custom dependency
tracking logic was that it was written before
the majority of compilers offered a robust way to generate the list of
header dependencies.
As it stands now we want to remove all this custom dependency scanning
logic, not extend it
I am not an user of ctags. But CMake supports generating a
`compile_commands.json` for the Makefile and Ninja generator (
https://cmake.org/cmake/help/latest/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html
). That will have all the include directories for each target.
On Sun, Jul 7, 2019 at 10:27 AM
ok, thanks
by the way what about my ctags rule? how can i get the include path of an
app? so that i can pass it to ctags and have my tags produced?
thanks and regards
jlm
Le mer. 3 juil. 2019 à 16:52, Robert Maynard a
écrit :
> I completely forgot that the Makefiles based generators in CMake
I completely forgot that the Makefiles based generators in CMake have
a separate heuristic for determining system headers.
If you use the Ninja generator I see the expected behavior:
~/W/t/nbuild $ sudo touch /usr/include/c++/7/array
~/W/t/nbuild $ ninja -d explain -v
ninja explain: output
thanks for the anwer
quite not... I'm using cmake 3.14.2 (so, far away from 3.6) and have a
look, in main.cpp, there is #include :
$ find /usr/include/ -name filesystem
/usr/include/c++/5/experimental/filesystem
/usr/include/c++/7/experimental/filesystem
/usr/include/c++/8/filesystem
It look that starting with CMake 3.6 modification of system headers
will cause CMake to recompile projects. What version of CMake and your
compiler are you using?
On Mon, Jun 17, 2019 at 9:40 AM jl forums wrote:
>
> Hi,
> I want to create a full tag file and for this require to know the compiler
