The cmake build (on OS X) produces different set of binaries (and with different names) compared to the auto tools build

[DBankov]

The cmake build produces and installs (on OS X):

• include/IL/il.h
• INSTALL_RECEIPT.json
• lib/libDevIL.dylib
• README.md

while the auto tools script produces:

• AUTHORS
• bin/ilur
• ChangeLog
• COPYING
• include/IL/devil_cpp_wrapper.hpp
• include/IL/il.h
• include/IL/ilu.h
• include/IL/ilu_region.h
• include/IL/ilut.h
• INSTALL_RECEIPT.json
• lib/libIL.1.dylib
• lib/libIL.a
• lib/libIL.dylib
• lib/libILU.1.dylib
• lib/libILU.a
• lib/libILU.dylib
• lib/libILUT.1.dylib
• lib/libILUT.a
• lib/libILUT.dylib
• lib/pkgconfig/IL.pc
• lib/pkgconfig/ILU.pc
• lib/pkgconfig/ILUT.pc
• NEWS
• README
• share/info/DevIL_manual.info
• TODO

I'd ultimately like the cake build to produce exactly the same output as the auto tools one but for starters would like just the name of the libraries to be the same.

[bcampbell]

Hi there - I've been working on the cmake build. The current intention is to phase out the autotools build altogether. The rationale being that maintaining two build systems is a pain, and that cmake is more friendly on windows (and can generate project files for XCode, Visual Studio etc..)

As you've seen, it's not quite 100% yet :-) I've been working in: https://github.com/bcampbell/DevIL/tree/cmake_cleanup

Regarding your points:

1. Yes, it should be libIL instead of libDevIL! I've just pushed a change to restore this
2. I haven't added cmake install steps for ILU and ILUT yet, but I don't think that'll be too hard
3. I plan to make sure valid pkgconfig files are generated (and installed)
4. Not sure what README/Changelog files should be included in the install step - I'll investigate and see what conventions other libraries use.

Hope that helps!