Automake vs. CMake: mismatch in installed files

[amitdo]

DanBloomberg/leptonica@e8b670d9357c78a6

DanBloomberg/leptonica@29a33a364848f67d0

You didn't do the same for cmake/sw.

[amitdo]

BTW, it does not look right to me to install a file with _internal in its name.

[stweil]

The header files with _internal provide internal details of Leptonica structures.

Formerly those internal details were included with allheaders.h. Programs like the Tesseract training tools, but also others, could easily access member variables directly without using the available accessor functions. The drawback of that approach was that changing the internal details of Leptonica structures was difficult because it made modified versions of the Leptonica library incompatible.

Now programs which only include allheaders.h (and files included from that header file) are safe when Leptonica structures like struct Pix or struct Box are modified. They will also work with a newer Leptonica shared library Only programs which continue to use internal information by including _internal header files have a close dependency on compatible Leptonica library versions at run time.

[egorpugin]

Cmake (and sw) never were official build systems. People contribute their needs. They may differ from usual make behavior.

[amitdo]

This difference in behavior between the build systems is bad. We talked about this in the past (liblept vs. libleptonica, which Dan recently fixed).

[egorpugin]

I think project rules should be defined in some doc so all build systems will try to follow them:

1. binary (lib and exe) naming
2. .so naming
3. header installation process
4. else...