Re: Enable asm for OpenSSL

I made the following changes and tried building [debug] [|x64|arm64] 
binaries (ie, 6 combinations in total). There were no build errors and I 
could successfully test the x86 and x64 versions (no acccess to an arm 
machine).

[[[
Index: build.txt
===================================================================
--- build.txt   (revision 29575)
+++ build.txt   (working copy)
@@ -33,6 +33,7 @@
                                    
 https://www.activestate.com/products/perl/
 - WiX 3.10(\b 1)                    http://wixtoolset.org/
 - NAnt 0.92(\b 1)                   http://nant.sourceforge.net
+- NASM 2.16 (or later)              https://nasm.us/

 (\b 1) Add the paths of the binaries to the PATH environment variable. You 
may have to
     logoff/logon to make the new environment variables take effect!
Index: ext/build/OpenSSL.build
===================================================================
--- ext/build/OpenSSL.build     (revision 29575)
+++ ext/build/OpenSSL.build     (working copy)
@@ -52,7 +52,6 @@
     <exec program="perl" workingdir="${targetDir}">
       <arg value="..\Configure" />
       <arg value="${targetName}" />
-      <arg value="no-asm" />
       <arg value="no-gost" />
       <arg value="no-shared" />
       <arg value="no-autoload-config" />
]]]


Based on Stefan's statement above:

> So basically, I won't object if someone wants to enable the asm code in 
the build. But I myself won't do it.

I can commit it to trunk. But we need to make sure NASM is installed on the 
nightly build machine and that Stefan is OK to add use this for the public 
releases (when the time comes).

Kind regards,
Daniel Sahlberg

-- 
You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/97194556-db20-4ea7-b26d-f7a4d09a70a0n%40googlegroups.com.