Okay, one question for the experts, whomever that may be in this area.
One script contains this stanza:
# Easysetup provides reference implemenation of Arduino Enrollee.
# Mediator applications developed on different platforms will be default
defining the
# flag 'REMOTE_ARDUINO_ENROLEE'. If the target Enrollee is not Arduino,
the below commented
# modifications must be enabled instead (and the existing define must be
commented).
#
##### The following lines must be uncommented, if target Enrollee is not
Arduino
target_enrollee = env.get('ES_TARGET_ENROLLEE')
if target_enrollee == 'arduino':
print("REMOTE_ARDUINO_ENROLEE flag is defined.")
print("The Mediator application will be working only with Arduino
Enrollee.")
easy_setup_env.AppendUnique(CPPDEFINES=['REMOTE_ARDUINO_ENROLEE'])
for reference the script is service/easy-setup/mediator/richsdk/SConscript
this seems to refer not to building for arduino, but building so that
arduino can be the other end of what is built. So I'm not sure of the
status of this section of the build with respect to "remove Arduino".
any wisdom or suggestions?
(ES_TARGET_ENROLLEE seems currently only to be set in auto_build.py if
targeting tizen, and only a tizen sample build adds it to the help
variables so anyone could figure out there was such a thing to set.
However, it is mentioned a few places on the wiki which I have not
examined yet)
On 12/05/2017 12:21 PM, Dave Thaler wrote:
> Yes on Arduino. When I was platform maintainer (which is now Dan Mihai), the
> decision was to delete it after 1.3, since Arduino support was moved to
> iotivity-constrained.
> So that would be good to do now.
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Mats Wichmann
> Sent: Tuesday, December 5, 2017 11:00 AM
> To: IoTivity Developer List <[email protected]>
> Subject: [dev] iotivity master branch cleanup?
>
>
> The iotivity coding guidelines recommend that unused code should not be left
> lying around, but rather deleted.
>
> Since git allows fishing out old revisions so nothing will be "lost", is it
> worth simplifying the build structure by stripping out the Arduino support
> from the iotivity project (master branch)?
>
> Similarly, though it is less intrusive to the build, should the old remote
> access (WITH_RA and WITH_RA_IBB) be stripped out?
>
> _______________________________________________
> iotivity-dev mailing list
> [email protected]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Cdthaler%40microsoft.com%7C4bf41d43087a4c21211708d53c125d13%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636480971947191334&sdata=Q55MobB1P9S9WndPpuvV6j%2Fnh93CUP%2FLU7k5TpkbsH0%3D&reserved=0
>
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
