mirror of
https://github.com/openssl/openssl.git
synced 2024-12-25 01:43:57 +08:00
fe9aa7642c
One of the reasons for why masm/ml64 is not [fully] supported is that it's problematic to support multiple versions. But latest one usually works and/or it's lesser problem to make it work. So idea here is to have a "whistle" when it breaks, so that problems can be evaluated as they emerge. It's kind of "best effort" thing, as opposite to "full support". Reviewed-by: Richard Levitte <levitte@openssl.org>
23 lines
1.0 KiB
Plaintext
23 lines
1.0 KiB
Plaintext
# We can't make commitment to supporting Microsoft assembler,
|
|
# because it would mean supporting all masm versions. This in
|
|
# in turn is because masm is not really an interchangeable option,
|
|
# while users tend to have reasons to stick with specific Visual
|
|
# Studio versions. It's usually lesser hassle to make it work
|
|
# with latest assembler, but tweaking for older versions had
|
|
# proven to be daunting task. This is experimental target, for
|
|
# production builds stick with [up-to-date version of] nasm.
|
|
|
|
%targets = (
|
|
"VC-WIN64A-masm" => {
|
|
inherit_from => [ "VC-WIN64-common", asm("x86_64_asm"),
|
|
sub { $disabled{shared} ? () : "x86_64_uplink" } ],
|
|
as => "ml64",
|
|
asflags => "/c /Cp /Cx /Zi",
|
|
asoutflag => "/Fo",
|
|
sys_id => "WIN64A",
|
|
bn_asm_src => sub { return undef unless @_;
|
|
my $r=join(" ",@_); $r=~s|asm/x86_64-gcc|bn_asm|; $r; },
|
|
perlasm_scheme => "masm",
|
|
},
|
|
);
|