CS253 Compiled Header Files

Simple Example

Consider this simple program. It gets π from a header file:

    % cat main.cc
    #include "pi.h"
    #include <iostream>
    int main() {
        std::cout << pi << '\n';
        return 0;
    }
    % cat pi.h
    constexpr auto pi = 3.14;
    % g++ -Wall main.cc
    % ./a.out
    3.14
    % ls
    a.out  main.cc  pi.h

Note that pi.h is not mentioned in the compile command.

What if we try to compile `pi.h`?

    % g++ -Wall main.cc pi.h
    % ls
    a.out  main.cc  pi.h  pi.h.gch
    % ./a.out
    3.14

Let’s improve the value of π:

    % echo "constexpr auto pi = 3.14159;" >pi.h
    % g++ -Wall main.cc 
    % ./a.out
    3.14

Hey, why didn’t it work?

    % rm pi.h.gch 
    % g++ -Wall main.cc 
    % ./a.out
    3.14159

Moral of the story

When the compiler sees #include "pi.h", it first looks for pi.h.gch, and uses that precompiled header file if it’s present.
This means that, if you change pi.h, it doesn’t matter, because the compiler uses pi.h.gch if it’s there. Ack!
Same principle as having foo.cc and foo.o.
This can be a powerful tool, if used properly with a well-written Makefile.
My attitude: It ain’t worth it. Stay away from it.

CS253: Software Development with C++

Spring 2018

Compiled Header Files

CS253 Compiled Header Files

Simple Example

What if we try to compile `pi.h`?

Moral of the story

CS253: Software Development with C++

Spring 2018

Compiled Header Files

CS253 Compiled Header Files

Simple Example

What if we try to compile pi.h?

Moral of the story

What if we try to compile `pi.h`?