[En-Nut-Discussion] include/crypto/bigint.h vs ./include/contrib/crypto/bigint.h

Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
Fri Apr 25 10:59:40 CEST 2014

>>>>> "Ole" == Ole Reinhardt <ole.reinhardt at embedded-it.de> writes:

    Ole> You run into trouble caused by the same naming of some header
    Ole> files, which I was not aware of, when adding the TLS library code
    Ole> to the repo.

    Ole> These are two totally different libraries. The one from Daniel Otte
    Ole> (GPL), which now lives in nut/contrib/arm-crypto-lib, and the axTLS
    Ole> library (BSD), which lives int nut/crypto and nut/tls.

For totally different things or for teh same thing done differently. Is
there any need or profite to keep both?

    Ole> When enabling the GPL support, the GPLed arm-crypto-lib is
    Ole> compiled, which includes its own headers of the same naming scheme.

    Ole> My changes on "Fri Oct 25 20:18:33 2013 +0000" have been made to
    Ole> make the arm-crypto-lib to compile along with Nut/OS at all, before
    Ole> it had to be compiled seperately.

    Ole> I suppose that we have to look over the makefiles and includes ones
    Ole> again to make sure, the right files are included in the
    Ole> arm-crypto-lib.  Very likely the main problem is -I
    Ole> nut/include/contrib, added somewhere in the makefiles.

Uwe Bonnes                bon at elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

More information about the En-Nut-Discussion mailing list