Has the time come to get rid of the "delivering" of public headers?
bjoern.michaelsen at canonical.com
Wed Feb 22 16:31:54 PST 2012
On Wed, Feb 22, 2012 at 03:09:49PM +0100, Lubos Lunak wrote:
> Could not the windows build be helped by having only one location for include
> files where a script would at the beginning of the build create for each .hxx
> file a small wrapper with the same name only doing #include of the real one,
> with the right path to it?
An _additional_ file to open? I highly doubt it will increase windows
performance. I would assume the opposite, but of course, I am open to hard
> And, since I'm already asking, is the Windows performance the reason include
> files are scattered this way? E.g. in sw/ I find this actually rather
> annoying, some .hxx files are in inc/, some next to .cxx sources, Writer
> AFAIK does not really export anything anyway, and I always have to jump
> around just to find the right header file :(.
No its just historic mess. Never attribute to malice ...
More information about the LibreOffice