digikam 4.3.0 (was: depends_build on minimal version?)

[Lawrence Velázquez]

On Sep 18, 2014, at 7:55 PM, René J.V. Bertin <rjvbertin at gmail.com> wrote:

> Now there is another thing with this new digikam version. I comes with a newer copy of libkgeomap. The cmake system is supposed to add the path to the included header files to the compiler options, but apparently the script finds the headers from the previous, 4.0.0 version that were installed in /opt/local/include/libkgeomap . At least, the command line for the files that failed to compile didn't have the -I pointer to the included header directory. This was with clang++-mp-3.4 . What would be the best way to prevent this from the Portfile? Delete or move aside /opt/local/include/libkgeomap in pre-configure and then move it back in post-build or post-destroot (if it was moved aside)? Deactivate the (or all) previous versions, if that's possible? Detect the situation and bail out with a message to the user?

So does the CMake build add -I arguments for the included headers or not? Can you add them?

vq