TagLibAmalgam: A new way to use TagLib
vinnie.falco at gmail.com
Wed Apr 18 15:39:39 UTC 2012
I was just about to ask the same question.
You're right that TagLibAmalgam.cpp does not include TagLibAmalgam.h.
But I would like it if it did, since that would reduce the size of the
resulting amalgamation (by exactly the number of bytes in the file
TagLibAmalgam.h, since header material is duplicated).
I plan on correcting this, but in order to do so I need precisely the
information that you asked for. That is, a list of all the public
headers, and a list of all the private headers (which I hopefully can
assume is all of the headers, minus the public ones).
On Wed, Apr 18, 2012 at 8:34 AM, Manfred Schwind <lists at mani.de> wrote:
>>> Would it be wise to add all the headers? Is there a reference
>>> indicating which header files contain public interfaces?
>> All of them should be included. (The only private interfaces that are included will still be required for building the .cpp file.)
> The resulting TagLibAmalgam.cpp does not include the TagLibAmalgam.h file.
> The TagLibAmalgam.cpp builds fine, so I assume all needed header files are included automatically by the amalgamation tool.
> And therefore I think the private headers should NOT go into the TagLibAmalgam.h file.
> Is somewhere documented which header files are private?
More information about the taglib-devel