On 11/30/2015 12:31 AM, Alec Ari wrote: > Hello everybody, I've been following the RTAI project closely for the > past few years and noticed some more activity on their mailing list > the past few weeks in regards to LinuxCNC. I was just curious if the > goal now is to make LinuxCNC work with the mainline RTAI tree, their > new math changes, and dropping legacy IPIPE support (HAL_NR_FAULTS -> > IPIPE_NR_FAULTS etc) and whatever other changes since RTAI 3.x. > without modifying the RTAI source and using the official CVS tree > instead.
Hi Alec, I decided to see what it would take to support the current mainline RTAI (Vulcano, aka 5.0-test1) in LinuxCNC, and surprisingly it wasn't that hard. See the rtai-5 branch on git.linuxcnc.org for details: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/rtai-5 On the RTAI side, i'm building newlib's libm from source as part of the RTAI build. You can see the details of that here: https://github.com/SebKuzminsky/rtai/commits/vulcano-debs I know the RTAI dev community is pretty fractured at the moment (for various reasons), and that's a bummer. You know RTAI better than most any of us, what are your thoughts on this approach? -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
