| Re: [wakaama-dev] dtls (tinyDTLS) integration |
|
Hi Julien, thanks for the information! So I have to wait contributing, until tinyDTLS is part of eclipse : - ). Is there a eclipse page to look up, which thirdparty libraries got a CQ for other projects? I searched, but I didn’t found one (or I got a 404). I’m asking, because I would also like to add some cunit tests,
which also relay on thirdparty stuff and therefore may also be not possible in the near future. @Olaf Bergmann Did you have progress in bringing tinyDTLS under the hood of Eclipse? Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ESY4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn Von: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Julien Vermillard We need to open a CQ if we want to use/depend on tinydtls. Le jeu. 5 mars 2015 12:12, Navarro, David <david.navarro@xxxxxxxxx> a écrit : Hi, tests/utils is a fine place for your code. It is for piece of code useful for test apps and objects. Regards, David Navarro From:
wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kraus Achim (INST/ESY4) Hi all, I currently started a DTLS addon for wakaam using tinyDTLS. Currently tests/utils seems to be “standalone” source. Would it be OK, to add sources, which depend on tinyDTLS and Wakaama core to tests/utils or
should this be better placed in something like “test/dtls” (to avoid adding dependencies to tests/utils)? Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ESY4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Tel. +49 711 811-58139 Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn --------------------------------------------------------------------- This e-mail and any attachments may contain confidential material for _______________________________________________ |