On Sunday 24 January 2010 20:44:12 Alexander Neundorf wrote: > On Sunday 24 January 2010, Dario Freddi wrote: > > On Sunday 24 January 2010 18:58:01 you wrote: > > ... > > > > Ah, ok. > > > set(FOO " bar" ... CACHE) behaves as follows: > > > > > > If "FOO" is not in the cache, it is written in the cache with the value > > > "bar" (this happens during the first call in the first run). > > > > > > If FOO is already in the cache, set( ... CACHE ) basically does > > > nothing, it doesn't change the value in the cache. > > > > > > So, your first call basically says "put this value in the cache if it's > > > not there yet" > > > The second call basically does nothing. > > > > > > If you want to change the value of a variable which already is in the > > > cache, you need to add the "FORCE" option to the set() command. > > > > Gotcha. I'm adding force to the last call and committing it all > > Ok, go ahead. > I think this should also go in the 4.4 branch...
Yup, already backported :) > > Alex > -- ------------------- Dario Freddi KDE Developer GPG Key Signature: 511A9A3B
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
