KF5 Update Meeting Minutes 2013-w31
Kevin Ottens
ervin+bluesystems at kde.org
Thu Aug 22 11:18:47 UTC 2013
On Wednesday 21 August 2013 17:27:12 Nicolás Alvarez wrote:
> 2013/8/21 Kevin Ottens <ervin+bluesystems at kde.org>:
> > And that's exactly the point, in the case of dependencies management at
> > build time I don't like how cmake handles variables at all[*] (and I
> > don't think I'm alone in that, most of the people touching our cmake
> > files have problems with it at some point... except you because you
> > breath and live cmake for good reasons). That's why another more secure
> > tool is more than welcome for that case, this way we can use something
> > else than variables when we want to.
> >
> > [*] If it had a strict mode like perl for instance, I'd have a different
> > position on that matter I think. But I don't think it has anything like
> > that.
> There's cmake --warn-uninitialized: "Print a warning when an
> uninitialized variable is used."
Now that's interesting... Any way to control that from the CMakeLists.txt or
to turn that into an error? (just wondering how far that can be pushed)
Cheers.
--
Kévin Ottens, http://ervin.ipsquad.net
Sponsored by BlueSystems and KDAB to work on KDE Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20130822/ac101677/attachment.sig>
More information about the Kde-frameworks-devel
mailing list