yasm 1.1 for windows for SAFESEH compatibility...

yasm 1.1 for windows for SAFESEH compatibility
BUG=63567
TEST=libvpx and ffmpeg build on windows.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=66803

[fbarchard, 2010-11-19 19:03:31]

Updated yasm for Windows and licensing (LGPL)

[Mark Mentovai, 2010-11-19 19:10:43]

http://codereview.chromium.org/5145007/diff/3001/README.chromium
File README.chromium (right):

http://codereview.chromium.org/5145007/diff/3001/README.chromium#newcode16
README.chromium:16:
http://www.tortall.net/projects/yasm/releases/yasm-1.1.0-win32.exe
Are you actually checking in a binary that you didn’t build from source
yourself?

[fbarchard1, 2010-11-19 19:53:53]

http://codereview.chromium.org/5145007/diff/3001/README.chromium
File README.chromium (right):

http://codereview.chromium.org/5145007/diff/3001/README.chromium#newcode16
README.chromium:16:
http://www.tortall.net/projects/yasm/releases/yasm-1.1.0-win32.exe
yes.
On http://www.tortall.net/projects/yasm/wiki/Release1.1.0
They say "For Windows and DOS users, we recommend downloading the prebuilt
binaries"

Would you prefer the .exe I build from 1.1 source?
The file size is smaller, which I think comes from me using VS2008 and they use
2005.
I've tested libvpx and ffmpeg build with their binary.

[Mark Mentovai, 2010-11-19 19:55:41]

If you have to check in a binary, it should at least be one you built yourself.

[fbarchard1, 2010-11-19 20:07:14]

On 2010/11/19 19:55:41, Mark Mentovai wrote:
> If you have to check in a binary, it should at least be one you built
yourself.

Done.

>yasm --version
yasm 1.1.0.2352
Compiled on Nov 19 2010.
Copyright (c) 2001-2010 Peter Johnson and other Yasm developers.
Run yasm --license for licensing overview and summary.

[Mark Mentovai, 2010-11-19 20:13:20]

OK, looks good then.