[cmake-developers] RFC: CMake precompiled header support and custom compiler based implementation

Taylor Braun-Jones taylor at braun-jones.org
Sat Dec 5 02:21:38 EST 2015


Thanks Daniel!

I've just started playing with your pch branch. I like the implementation
approach.

It looks like precompiled headers for an INTERFACE IMPORTED target are not
supported. Is that right?

`cmake --help target_precompile_headers` doesn't work.

I'll come back with more questions/comments as I continue to play with this
pch branch.

On Fri, Dec 4, 2015 at 5:50 PM, Daniel Pfeifer <daniel at pfeifer-mail.de>
wrote:

> On Fri, Dec 4, 2015 at 11:32 PM, David Cole <DLRdave at aol.com> wrote:
> > Makes sense.
> >
> > Can I inject my own "#include <notNormallyIncludedSystemHeader>" into
> > the generated stream, or otherwise inject something into it?
>
> You should be able to do:
>
> target_include_directories(your_target
>   PUBLIC public
>   PRIVATE private
>   )
> target_precompile_headers(your_target
>   PUBLIC
>     public_header1.h
>     public_header2.h
>   PRIVATE
>     private_header1.h
>     private_header2.h
>   )
>
> Does that answer your question? Do you think this could solve your
> use-case?
>
> > Specifically, for me, I want to include some, but not ALL VTK headers
> > for a VTK-based project.
>
> I don't see a problem for that.
>
> > Thanks for working on this.
>
> You are welcome. :-)
>
> > Let me know if you want me to be a Visual Studio tester for you.
>
> Yes, please. My main working environment is Linux. I appreciate any
> feedback from different platforms.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20151205/1f42919b/attachment-0001.html>


More information about the cmake-developers mailing list