Mac OS X port

[henriclinden]

Port to Mac OS X = added cmake configuration "darwin".
Other minor fixes;

• some type casts, inits, etc.
• local includes should be declared using "" instead of <> (which searches the system includes first)
• gtest not longer mandatory.

[mheden]

Please squash all commits that has to to with the OSX-port to one.

[henriclinden]

All changes has been pushed (to my fork) already. How can I squash pushed commits?

[henriclinden]

Commits now squashed. A "git push origin master --force" did the trick.

[tjacobs]

What's the status of SOEM-NG? Can we use this for detecting ethercat slaves, reading sensor values, and sending commands? We'd like to run SOEM on MacOS.

[henriclinden]

Hi Tom, Thanks for writing. The status of SOEM-NG for Mac OS is somewhat unknown at the moment. It is 2-3 years ago since I used it.It might not even compile on the latest Mac OS. Have you tried it and found it does not work? If so, what version of Mac OS did you use and on what HW? Kind regards, Henric Den lör 22 dec. 2018 kl 08:24 skrev Tom Jacobs <[email protected]>:

…

What's the status of SOEM-NG? Can we use this for detecting ethercat slaves, reading sensor values, and sending commands? We'd like to run SOEM on MacOS. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQh8jMJoljI35wRUphxkq1gEFS-dw8Ddks5u7d4ggaJpZM4ISYMX> .

[tjacobs]

Cool, thanks for replying. I see. It does compile fine, but then I'll need to decide on using this one and porting our code vs the SOEM one which we already have working on other systems.

I guess the SOEM-NG is a next generation version of SOEM, and has a different way of doing the hardware and OS abstraction?

For our case, we just need to:

• List and choose ethernet interface with ethercat devices
• Detect slaves
• Read sensor values
• Write commands

I guess the NG version has the ability to do these things?

[tjacobs]

Or is my best bet to bring the Darwin.cmake and some of the osal/darwin code back into SOEM? It was just the netpacket.h stuff that needed changing to net_ifdl.h AF_LINK in oshw/linux/nicdrv.c that was different on darwin.

[henriclinden]

Hi. I would go for the porting to SOEM option. I don’t think soem-ng is ready for real use yet. /Henric sön 23 dec. 2018 kl. 00:10 skrev Tom Jacobs <[email protected]>:

…

Or is my best bet to bring the Darwin.cmake and some of the osal/darwin code back into SOEM? It was just the netpacket.h stuff that needed changing to net_ifdl.h AF_LINK in oshw/linux/nicdrv.c that was different on darwin. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQh8jOqYTtOPfzogQHJeqCmbx60Oi-woks5u7rvMgaJpZM4ISYMX> .