Comment 5 for bug 613556

Revision history for this message
SirVer (sirver) wrote :

wonderfull! that's pretty much all then for us :)

or is there a nice little workaround we could sneak into our cmake files to avoid this situation in the future?