Fwiw, I would likely not pursue oic if it meant excluding my osx users.
Here are my experiences so far with iotivity and osx.

I played with iotivity 1.2.1 on osx. The standard build completed, not
secure. The lib/header locations included an incomplete framework. I had to
add the following to my makefile to compile a test app.

IOTIVITY = lib/iotivity-1.2.1
IOT_BULD = ${IOTIVITY}/out/darwin/x86_64/release
IOT_FRAMEWORK = ${IOTIVITY}/out/darwin/iotivity-csdk.framework/
LIBS += -lc_common -lcoap -lconnectivity_abstraction -llogger -locsrm
-loctbstack -lresource_directory -lroutingmanager
IOT_LDFLAGS = -L${IOT_BULD}
IOT_CFLAGS = -I${IOT_BULD}/include/resource/
-I${IOT_BULD}/include/c_common/ -I${IOT_FRAMEWORK}/Versions/A/Headers/

The HEAD built with secure, but not all ( stack ) tests passed. The
locations of libs/headers are more in line with linux build so that is
cool. The example client discovered my linux i-c server.

Gregg, https://github.com/iotk/iochibity looks great. Nice and clean. I
especially like this insight:

"Remove dependency on xcode and OS X version etc. This should be a strictly
Darwin build. An OS X specific build - e.g. to support an OS X Framework -
should be a separate project."

Iotivity-constrained should be an easy port - also nice and clean. This is
what I am currently using for test servers.

Jay

On Wed, Mar 8, 2017 at 2:16 PM Gregg Reynolds <dev at mobileink.com> wrote:



On Mar 8, 2017 8:15 AM, "Dave Thaler via iotivity-dev" <
iotivity-dev at lists.iotivity.org> wrote:

Mac is not a currently supported platform (i.e., you're on your own).
If someone wants to step up and make it work, and wants to volunteer to be
the sub-maintainer for MacOS, let me know.

There's an initial wiki page at
https://wiki.iotivity.org/macosx_build_instructions but it doesn't have
much real info at the moment.


fyi https://github.com/iotk/iochibity supports darwin. people interested in
adding darwin support to iotivity are welcome to take a look and ask
questions (it involves many changes to the build system and some serious
reorganization of the source tree, but the code is pretty much the same as
iotivity).  unfortunately i've had to attend to other matters for a few
months, but i expect to get back to iotivity in the next few days.


gregg
_______________________________________________
iotivity-dev mailing list
iotivity-dev at lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170312/f16a0ea3/attachment.html>

Reply via email to