Would be great to have!

This branch has conflicts and would need rebased. Also, I'd like a couple people who know this technology in order to vouch for the patch (I don't know it personally)

It seems that the only different w.r.t. the current master are the first two lines

libdir=@CMAKE_INSTALL_FULL_LIBDIR@includedir=@CMAKE_INSTALL_FULL_INCLUDEDIR@

I've tried on my system: They new implementation gives a finaldocopt.pc that reads

libdir=/Users/tdegeus/miniconda3/envs/test/libincludedir=/Users/tdegeus/miniconda3/envs/test/includeName: docopt.cppDescription: C++11 port of docoptVersion: 0.6.2Libs: -L${libdir} -ldocoptCflags: -I${includedir}

In contrast, the old implementation gives

libdir=/Users/tdegeus/miniconda3/envs/test/libincludedir=/Users/tdegeus/miniconda3/envs/test/include/docoptName: docopt.cppDescription: C++11 port of docoptVersion: 0.6.2Requires:Libs: -L${libdir} -ldocoptCflags: -I${includedir}

The difference being that with the new implementation one can

#include<docopt/docopt.h>

As one would also do when using CMake.

The old implementation would require

#include<docopt.h>

That being said, the readme is may not entirely clear on this point?

Update

I was wrong about the CMake behaviour. With CMake one should

#include<docopt.h>

@jaredgrubb Can you clarify?

I one in fact should use#include <docopt.h> with CMake, I guess the original pkgconfig behaviour is correct, and this PR should be closed. However, this point should be clarified in the readme.