Hi Mike, thanks - will try that patch. Not sure if I have time either - in the end one would need to create an Xcode project to compile the stuff so that you can actually debug it?.
thanks Christian > On 8 Mar 2017, at 16:24, Finch, Mike - Michael <mike.f.finch at lowes.com> > wrote: > > Christian, > I had iotivity building on MAC and running the unit tests in > January. I created this patch https://gerrit.iotivity.org/gerrit/#/c/16333/8 > which had trouble for some of the unit tests, I could not figure out why. > Then master got updated and after the rebase I am having linking issues. > Jon Boone has made some effort on Mac also but I don't think he has succeeded. > I'm open to working in a smaller group to get mac supported, I only > have a couple of hours a week to dedicate to iotivity, so I am not making a > lot of progress by myself. I've got problems linking symbols out of the > stacktests, and when I don't build unittests I have more link troubles > rdclient. > > > I think marking the wiki as "community supported" is a good idea, I've made a > couple of minor edits there as I have learned things. I'm just not learning > that much that fast. > > Mike > > ________________________________________ > From: iotivity-dev-bounces at lists.iotivity.org [iotivity-dev-bounces at > lists.iotivity.org] on behalf of Christian Gran [gran at lynxtechnology.com] > Sent: Wednesday, March 08, 2017 9:45 AM > To: Dave Thaler; Mats Wichmann; iotivity-dev at lists.iotivity.org > Subject: Re: [dev] compile iotivity on Mac Sierra > > Hi, > > +1 for doing some cleanup :-) > > Christian > >> On 8 Mar 2017, at 15:43, Dave Thaler <dthaler at microsoft.com> wrote: >> >> I'm interested in feedback on that question. There are several platforms >> that are not supported but >> for which some code exists (darwin, arduino, etc.) >> >> In principle I agree it would be nice to remove unsupported code. >> >> Dave >> >>> -----Original Message----- >>> From: Christian Gran [mailto:gran at lynxtechnology.com] >>> Sent: Wednesday, March 8, 2017 6:40 AM >>> To: Dave Thaler <dthaler at microsoft.com>; Mats Wichmann >>> <mats at wichmann.us>; iotivity-dev at lists.iotivity.org >>> Subject: Re: [dev] compile iotivity on Mac Sierra >>> >>> Hi, >>> >>> this is good to know. Just started to try to use Mac - as there are >>> instructions >>> and subfolders which are labeled Mac. >>> Should we remove the non supported platforms from the code and Wiki, to >>> not annoy people? >>> I would prefer to have a clean tree and documentation for the supported >>> platforms only :-) >>> >>> thanks >>> Christian >>> >>>> On 8 Mar 2017, at 15:15, Dave Thaler <dthaler at microsoft.com> 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. >>>> >>>> Dave Thaler >>>> Platform Support Maintainer >>>> >>>>> -----Original Message----- >>>>> From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- >>>>> bounces at lists.iotivity.org] On Behalf Of Mats Wichmann >>>>> Sent: Wednesday, March 8, 2017 5:43 AM >>>>> To: Christian Gran <gran at lynxtechnology.com>; iotivity- >>>>> dev at lists.iotivity.org >>>>> Subject: Re: [dev] compile iotivity on Mac Sierra >>>>> >>>>> On 03/08/2017 06:12 AM, Christian Gran wrote: >>>>>> Hi, >>>>>> >>>>>> just tried to compile on Mac (macOSSierra) - but did not came very far. >>>>>> After fixing the scons script to detect that I?m on a Mac, found >>>>>> that couple >>>>> of headers are not included as the macros are not set correctly. >>>>>> Is there someone on this list who is working on Mac - or recently >>>>>> has >>>>> successfully compiled on Mac? >>>>> >>>>> We've just had someone else comment on some problems - they got to a >>>>> build but found some things did not actually get done. So I think >>>>> the answer is there's not been a /regular/ mac user for a while. >>>>> Suggestions for improvements of course welcome. >>>>> >>>>> I believe it was noted that in many places (some of) the unit tests >>>>> don't get built for Mac, due to sequences like this one: >>>>> >>>>> if (target_os in ['linux', 'windows']) and (test_env.get('SECURED') == >>>>> '1'): >>>>> >>>>> and some adaptation is likely needed to get that going. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> iotivity-dev mailing list >>>>> iotivity-dev at lists.iotivity.org >>>>> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > NOTICE: All information in and attached to the e-mails below may be > proprietary, confidential, privileged and otherwise protected from improper > or erroneous disclosure. If you are not the sender's intended recipient, you > are not authorized to intercept, read, print, retain, copy, forward, or > disseminate this message. If you have erroneously received this > communication, please notify the sender immediately by phone (704-758-1000) > or by e-mail and destroy all copies of this message electronic, paper, or > otherwise. > > By transmitting documents via this email: Users, Customers, Suppliers and > Vendors collectively acknowledge and agree the transmittal of information via > email is voluntary, is offered as a convenience, and is not a secured method > of communication; Not to transmit any payment information E.G. credit card, > debit card, checking account, wire transfer information, passwords, or > sensitive and personal information E.G. Driver's license, DOB, social > security, or any other information the user wishes to remain confidential; To > transmit only non-confidential information such as plans, pictures and > drawings and to assume all risk and liability for and indemnify Lowe's from > any claims, losses or damages that may arise from the transmittal of > documents or including non-confidential information in the body of an email > transmittal. Thank you.
