On 12/21/2013 6:53 AM, Dewey Garrett wrote: >> ... >> From what you wrote, I'm inferring that you are maybe thinking only of >> the x86 configs (which until recently has been the entire set). > It's all i know about -- I have only worked in the master branch of g.l.o: > > http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=summary > > addressing Item 8 of the todo list for the future 2.6 release: > > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Todo-2.6 > >> ... >> In short, we adopted a basic structure of >> linuxcnc/configs/<architecture>/<platform>/<hardware_interface>/<machine_config> > sorry, i don't know who the 'we' is or where this repository is, > you didn't provide a link. Sorry about that. Let me fix that omission -
I believe the latest unified binary stuff is now in the LCNC "unified-build-candidate-3" branch: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/unified-build-candidate-3 I think that the UBC branch is what accomplishes #3 of the todo list for 2.6. I understand that the branch is slated to be merged into master "by year end" (the target date set last June in Wichita) - I can't speak to exact timing, but I think that this is still slated for "any day now". I'm personally hoping to see that soon, as the UBC branch is effectively a prerequisite to running LinuxCNC on something other than an X86 platform (which is my personal interest in this). Those of us on non-x86 platforms can't use 2.6 until UBC is merged. LCNC on alternate platforms (like a BeagleBone) requires UBC (for non-RTAI, non-x86 RT support) + some other stuff; for BeagleBones that combination is referred to as the "MachineKit". Charles Steinkuehler initially whipped it up; Here's a link to his latest MachineKit announcement : http://bb-lcnc.blogspot.com/2013/09/new-machinekit-image-available.html and the MachineKit repro is here: https://github.com/cdsteinkuehler/linuxcnc/tree/MachineKit-ubc >> The file I referred to notes that we hoped to see (post merge) some >> additional top level config branches. for example: >> linuxcnc/configs/x86/ >> linuxcnc/configs/x86/PC >> linuxcnc/configs/x86/SIM >> My thought is that what you've done could fit into this nicely and then >> we'd have a consistent config structure that supports multiple >> architectures and platforms. >> Would you consider using this structure to hold the x86 configs you're >> reorganized? > It seems reasonable. I would imagine that there should be a level > of sim that works on any architecure to mitigate maintenance of > redundant configs: > linuxcnc/configs/sim That sounds like a reasonable improvement to me. I admit to having been BeagleBone focused at the time and probably didn't think about the Sims as much. > The config-cleanup has already changed hundreds of files and > directories and has some residual broken configs -- but if the > 2.6 release manager endorses for 2.6 I would work on this. When the UB stuff and ARM support was discussed last June in Wichita, the eventual consensus was to include UB in 2.6 and let stuff built on top of it go into 2.7. Since the non-x86 dir structure I mentioned went in the MachineKit branch, it probably won't show up until after 2.6. However it seems to me that adding/using a compatible dir structure for 2.6 will make 2.7 easier re the non-x86 configs. There is significant non-x86 LCNC use today and non-x86 configs just don't fit very well into a "flat all x86" config organization structure. I don't see any down side to this for 2.6, and it seems a natural fit to what you've already done for 2.6 todo #8. I also really appreciate your offer to consider this. Seb - what's your opinion re this? ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
