On 01/31/2018 03:14 AM, Wouter van der Beek (wovander) wrote: > Hi Thiago, > > Nice! > > Will this be github submodule in IOTivity, e.g. so that one does not have to > do an separate github pull to get this code? > Currently this is quite annoying to set up the IOTivity code base, one has to > download more than 1 repo seperatly.. > There is also another library that you have to pull down separately, which > also can be an github submodule in IOTivity. > > Kind Regards, > Wouter
there are actually a number of external projects that are downloaded using git, depending on configuration choices; the others are built from downloaded bundles, usually still from github: raxmpp, wksxmppxep and libstrophe are used by the "old" Remote Access code, that is, not at all. libcoap - the closer-to-upstream version (as opposed to the old fork in resource/ which we need to move away from) tinycbor mbedtls - this one is quite intentional, I believe, because of the implications: to make really clear that this is not iotivity code which is important since it contains encryption technology that could otherwise affect the ability to distribute iotivity (my understanding, perhaps Thiago will comment in more detail) the project does not use submodules, but could if whatever the current decision-making process concludes it's a good idea - it's something I've thought about also, without pursuing very hard. I have no clue at all how a project with submodules is treated for code export purposes. We could also flip any extlibs project that does not currently do so to build-from-bundle as those projects get more mature and we don't need to use some odd revision that doesn't match a release point. each change requires some plumbing adjustments in the CI system as well, not terribly difficult but something else to juggle. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
