Closed GoogleCodeExporter closed 9 years ago
Original comment by ya...@google.com
on 22 Aug 2014 at 6:00
x64/win64 should be synonyms since at least 0.8.0; Johann took a patch [1]
which went from win${bits}->x64 in configure, but it looks like bits being set
might have been the problem, not the format name specifically.
The command is generated separately with VS (gen_msvs_proj.sh,
gen_msvs_vcproj.sh), using the platform name thus the 'Win32'. I haven't tested
1.3.0, but in that case I guess it became case-sensitive.
[1] https://gerrit.chromium.org/gerrit/#/c/11263
Original comment by jz...@google.com
on 22 Aug 2014 at 8:04
I have tried yasm 1.3.0 64 bit windows binary, got:
yasm: FATAL: unrecognized object format `x64'
In visual studio build.
Replacing the yasm binary with 1.2.0 release, everything works fine.
Original comment by ya...@google.com
on 22 Aug 2014 at 8:37
This was merged some time ago:
c5795d8 gen_msvs_(vcx)proj.sh: set yasm format explicitly
https://gerrit.chromium.org/gerrit/#/c/71328/
Original comment by jz...@google.com
on 22 Sep 2014 at 9:42
Original issue reported on code.google.com by
ya...@google.com
on 19 Aug 2014 at 11:44