Re: Code-Architecture questions while compiling OpenSSL for STM32-processors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ping !!!

Upon code-browsing, I am beginning to feel that OpenSSL uses program-buffer, which is used for malloc/free.
Am I right?

If yes, is there a place where the maximum-size of "in-program-buffer-heap" is defined?

On Tue, Nov 22, 2016 at 7:33 PM, Ajay Garg <ajaygargnsit@xxxxxxxxx> wrote:
Hi All.

I wish to compile openssl libraries for a STM32-processor (which would then be linked statically with our application-framework code).


Now. I believe that OpenSSL uses tonnes of "malloc"s and "free"s. But for bare-metal-systems (without any formal OSes), we generally don't have any heap-memory.

So, what is the protocol for compiling OpenSSL for such systems?
I am sorry, but this is the first time I would be compiling for a non-OS entity.


Will be thankful for inputs.


Thanks and Regards,
Ajay



--
Regards,
Ajay
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux