How do I simply use flycheck in a huge project that's got a good deal of specific CPP options and different include dirs, all handled at the ./configure
phase? It's possible to get those paths from the config.log
, but I don't see in flycheck doc an option to forward arbitrary gcc options.
I think it's a common enough use case. Or do people always have to write parsing scripts to marshal gcc options into flycheck-gcc-include-path
(so flycheck can... translate it back into gcc options)?
flycheck-gcc-args lets you pass arbitrary options to GCC. You can add whatever compiler flags you want to this option.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.