Currently the binary archives from mingw.org and the automated builds from this project that I use put their artifacts in the top level of the archive, while the rubenvb builds place their artifacts in an intermediate 'mingw32' directory.
This difference complicates some of my current automated build juju, and I don't want to change my stuff :P Ruben...assuming this minimally tested patch works and doesn't break your build process, can I cajole you into accepting and changing your future releases? Jon --- blog: http://jonforums.github.com/ twitter: @jonforums Most people die of a sort of creeping common sense, and discover when it is too late that the only things one never regrets are one's mistakes. - Oscar Wilde
0001-No-archiving-to-intermediate-SHORT_NAME-dir.patch
Description: Binary data
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
