[karchive] /: Show how qmake integration can be done.

[David Faure]

On Sunday 05 January 2014 00:28:42 Nicolás Alvarez wrote:
> 2014/1/4 David Faure <faure at kde.org>:
> > On Saturday 04 January 2014 23:13:49 Stephen Kelly wrote:
> >> David Faure wrote:
> >> > I'd be happy to hear about how I can do it in a nice way: ideally I'd
> >> > want
> >> > to automatically get the "VARIABLE_PREFIX" passed to ecm_setup_version,
> >> > since I need that to get the version numbers.
> >> 
> >> It seems odd to me to use UPPERCASE KARCHIVE_* for those variables
> >> instead
> >> of KArchive_*.
> > 
> > No no, I only need VARIABLE_PREFIX to be able to get
> > ${${VARIABLE_PREFIX}_VERSION_MAJOR}
> > For instance ${KARCHIVE_VERSION_MAJOR}, which is where the version number
> > is stored.
> > Everything else uses KArchive_*.
> 
> You're asking to make ecm_setup_version() store the VARIABLE_PREFIX in
> a framework-name-agnostic variable, so you can get it later and do
> ${${VARIABLE_PREFIX}_VERSION_MAJOR}.
> Instead, what about making ecm_setup_version() store the version
> number in a set of framework-name-agnostic variables, in addition to
> the framework-name-prefixed veriables? PROJECT_VERSION_MAJOR? Maybe
> FRAMEWORK_VERSION_*?

Excellent point. It's what I was trying initially, even, using ECM_VERSION_* 
as set by ECMSetupVersion internally. But in fact these variables clash with 
the version number of ECM istelf (0.0.9) so better rename them.

What about the attached patch, then?

(Tested, works)

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: framework_version.diff
Type: text/x-patch
Size: 2777 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-buildsystem/attachments/20140105/d9c6eade/attachment-0001.diff>