Hi all.
Does anybody know what is a logic behind putting openssl headers and libraries into /etc in staging dir?
I see that for new routers openssl is present in toolchain, so there are no problems (but probably there could be a mismatch between headers in toolchain and headers of openssl library that will actually be installed to target).
But for RT-AC66U there is no openssl in toolchain, so I need to provide -L$(STAGEDIR)/etc/lib and -I$(STAGEDIR)/etc/include flags for my program to make it compilable.
Moreover, specifying --with-ssl=$(TOP)/openssl doesn't always work. For example, for curl-7.25.0 it leads to disabled HTTPS in libcurl, as configure searches for libraries in $(TOP)/openssl/lib while they are in $(TOP)/openssl.
Thanks,
Sergey.
Does anybody know what is a logic behind putting openssl headers and libraries into /etc in staging dir?
I see that for new routers openssl is present in toolchain, so there are no problems (but probably there could be a mismatch between headers in toolchain and headers of openssl library that will actually be installed to target).
But for RT-AC66U there is no openssl in toolchain, so I need to provide -L$(STAGEDIR)/etc/lib and -I$(STAGEDIR)/etc/include flags for my program to make it compilable.
Moreover, specifying --with-ssl=$(TOP)/openssl doesn't always work. For example, for curl-7.25.0 it leads to disabled HTTPS in libcurl, as configure searches for libraries in $(TOP)/openssl/lib while they are in $(TOP)/openssl.
Thanks,
Sergey.
