On Tuesday, October 6, 2015 at 1:11:43 PM UTC-4, jean-pierre.muench wrote: > > Am 06.10.2015 um 19:00 schrieb Jeffrey Walton: > > Hi Everyone, > > I want to add some post-build sanity checks to Visual Studio builds. For > example, to ensure AES-NI intrinsics were actually used during the build, > we can perform the following. But I don't know how we can incorporate it as > a QA step. > > How can we add this (and similar) as a QA step somewhere in the process? > > Visual Studio supports builds events (look in the property page for "build > events" in the left column). > You can put them pre-build, pre-link and post-build. > IIRC if the scripts / programs return "1" as opposed to "0" this triggers > a build error, so we could use this to run some QA scripts. I think we > shouldn't make them default for everyone though, but rather use them for > our internal testing / for the RCs. >
Yeah, it looks like MSBuild with a script is the way to go. From https://msdn.microsoft.com/en-us/library/dd393574.aspx: The following examples illustrate when you might run builds by using an MSBuild command line instead of the Visual Studio IDE. * Preprocess files before they reach the compiler. * Copy the build outputs to a different place. * Create compressed files from build outputs. * Do a post-processing step. For example, you might want to stamp an assembly with a different version. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
