Please consider adding the feature of exporting cmake targets about exiv2

[clanmills]

Jason. I've assigned this to @piponazo who is the team's CMake expert.

[piponazo]

Hi Jason, thanks for reporting this. I think I tried to add this feature and there was something about the current autotools design that block me to do it. Currently we are maintaining both configuration systems, and sometimes it is not easy to apply a change in cmake without breaking things in the autotools.

I will revisit this point ASAP and I will let you know if it's feasible to implement this feature fit the next 0.26.1 release. ;)

[piponazo]

I am investigating a bit and it seems that it is possible to add this feature without breaking things in the autotools part.

@jasjuang I will create a Pull Request soon so you can check my branch and test the final implementation ;)

[clanmills]

Jason and Luis: Thanks for your work on this. I own the Exiv2 autotools support and will investigate.

Jason:
Thanks for agreeing to work with us on vcpkg support in v0.26.1 Let's work together to ensure v0.26.1 fixes all your concerns. The v0.26.1 release was intended to be a minor effort. However the scope has extended and I have just started a 2 month trip away from home. I hope we'll achieve v0.26.1 RC1 in December and GM early 2018.

[Kicer86]

@clanmills do we still need autotools?

[piponazo]

@Kicer86 I asked him the same question few weeks ago :). The idea is to keep everything as it is for 0.26.1, while we try to improve the CMake support. Afterwards, for the next stable version, I will propose deeper changes in the code base that could break the autotools support. In that case we could deprecate the autotools and just focus in the CMake code, if we can guarantee that we can build Exiv2 in all the platforms that the autotools do it nowadays.

I am in favour of just maintaining one system (CMake) instead of keeping the support for the mix of approaches we are maintaining today (autotools, cmake, Visual Studio Solution files ...)

[clanmills]

Yes. We don’t know anything about users build scripts. We should announce our intention to deprecate autotools before doing so. Additionally, I am still working on C++11 support. And I’m working on support for Adobe’s XMPsdks (2013/2014/2016). The plan is to get those features working correctly with autotools and msvc/, then modify CMake appropriately. I am unwilling to remove either autotools or msvc/ support until: 1 We have given fair notice that we intend to deprecate those environments. 2 We are have 100% confidence that CMake support builds Exiv2 really well. I use CMake/Xcode to develop Exiv2. So I am close to feeling OK about CMake being a replacement for autotools on MacOS-X, Cygwin and Linux. I have little confidence in CMake/Visual Studio as a replacement for our msvc/ solution & project files. CMake/Visual Studio dependency support is awful. I have high hopes of Conan to address that, however It is too early to be adopted as our only build support for Visual Studio. Robin http://clanmills.com Not sent from my iPhone

…

On 1 Oct 2017, at 09:34, Michał Walenciak ***@***.***> wrote: @clanmills do we still need autotools? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.