2014-05-20 2:01 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com>:
> Em seg 19 maio 2014, às 23:10:10, André Pönitz escreveu: > > > It's due to the hash randomisation. This was done to avoid DoS attacks > > > that > > > can be performed by tweaking data to ensure it always falls into the > same > > > hash bucket. > > > > Do we think this is useful to have for the specific case of rcc, or, > > rather, that this outweighs the benefits of reproducible build results? > > I'd say that reproducible builds are more important. There's no hashing > left > in the generated code; this is only something that rcc does on its own. > > I'd recommend then that we reset the hash seed in rcc. > > See: https://codereview.qt-project.org/85806 > > That'd be nice actually! The reason I asked to begin with was that I had some trouble avoiding re-builds in a custom scons-based toolchain. Cheers, Ola
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
