Android NDK r10c build error for arm64-v8a: No such file or directory #include <sha1.h> -

-

I have a native C code, which calculates SHA1 digest, it is compiled without problems with NDK R10b But I get this error with NDK R10C: 

  [compiled compiled by: my library & lt; = My-library-jni.c {PATH_TO_THE_FILE} / my-library-jni .c: 3: 18: Fatal error: sha1.h: No such file or directory # is included & lt; Sha1.h & gt;

I am updating NDK R10 C to compile for 64-bit platform. It seems that the 64-bit header does not include sha1.h. Why? And how can I fix it? Can I get some implementation of SHA1 and include it in my project?

Edit

I ended up using the code. It worked fine for me.

I think you have NDK R10b in 64 bit mode because me sha1.h for arm64-v8a The header is not even found.

It seems that SHA1 was not explicitly supported - it was not mentioned anywhere in the document. And it is not mentioned in the "static API" documentation (and I think it can be technically not considered as part of the library). You also include MD5 functions in libc.so which link to 32 bit mode, which do not appear at all in the header, which makes everyone more unexpected / unplanned.

Even if it is not originally intended, they have kept it in 32-bit mode for compatibility, but in 64-bit mode, we have chosen the option to remove such unexpected stuff.

Make a link to clarify something:

Yes, your solution is to find an existing implementation of SHA1 (Fortunately many different available under different types of licenses - are different) and include it instead most of them are similar or nearly identical APIs.


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more