https://sourceforge.net/p/valgrind4win/wiki/CommitPolicy/Recent changes to CommitPolicyenFri, 10 Aug 2012 04:19:02 -0000https://sourceforge.net/p/valgrind4win/wiki/CommitPolicy/<pre>--- v1 +++ v2 @@ -1,5 +1,6 @@ ## Commit Policy ## * no warnings: the code must compile without warnings. The "-Werror" compiler option is used to enforce that. +* code must build with both MinGW32 and MinGW64 tool chains * Linux builds from the Valgrind4Windows code must yield exactly the same binaries as builds from the respective original source. This means that all Windows-related changes must be enclosed in "#ifdef VGO_windows" or "#ifdef VGP_xxx_windows". * stick with the formatting rules in use, if possible use the Eclipse project that comes with defined formatters * do not reformat existing code </pre>Christoph SchwarzFri, 10 Aug 2012 04:19:02 -0000https://sourceforge.netfaf0ac5247aba587211166b6e782e3b56f6ca79bhttps://sourceforge.net/p/valgrind4win/wiki/CommitPolicy/## Commit Policy ## * no warnings: the code must compile without warnings. The "-Werror" compiler option is used to enforce that. * Linux builds from the Valgrind4Windows code must yield exactly the same binaries as builds from the respective original source. This means that all Windows-related changes must be enclosed in "#ifdef VGO_windows" or "#ifdef VGP_xxx_windows". * stick with the formatting rules in use, if possible use the Eclipse project that comes with defined formatters * do not reformat existing code * do not make changes to files that are not on the list of [CreatedAndModifiedFiles], without prior consultation with project management * see also "Development guidelines" on page [DevelopmentOverview] Christoph SchwarzThu, 12 Jul 2012 22:33:29 -0000https://sourceforge.net6235dcb4911eca3526a371e9f72fdd290e8e4bf5