Hi, A reorganization of the x86/PC configs is welcome (and needed in my view) - thanks.
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). A while back, I reorganized an ARM config directory to give it some structure. This went into the machinekit stuff which went into the UBC branches and I think that is just now getting merged (I haven't been watching the commit list all the time, so maybe someone can update me as to what the status of this is). What I don't know is if the machinekit stuff got included in the UBC stuff. If the machinekit / UBC stuff is has gotten that far, please take a look in linuxcnc/configs/arm for README-ARM-Dir-Structure.txt which describes the ARM dir structure. In short, we adopted a basic structure of linuxcnc/configs/<architecture>/<platform>/<hardware_interface>/<machine_config> Thus the Shapeoko configs I created for my bench test platform are in linuxcnc/configs/ARM/BeagelBoneBlack/K9/Shapeoko This got created as I was trying to address the same issue you pointed out - making it easy to find a config for the machine you happen to have. 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? If you do, then when it all does get merged together eventually, we will have a common config dir structure for multiple architectures. Dave On 12/17/2013 7:17 PM, Dewey Garrett wrote: > New users are typically introduced to linuxcnc by installing > from a CD (or USB) image and offered sample configurations to > try on their local machine. A user should be able to pick a > simulation configuration that will run and demonstrate basic > linuxcnc operation on a machine with no special hardware > requirements. Over time, the arrangement of the configurations > has grown and perhaps been confusing to new users. > > In antcipation of the next release, the configs directory for > linuxcnc has been updated to rearrange and simplify the presentation > of sample configurations in a hierarchical order with the > following toplevels: > > sim -- simulator configurations intended to startup as-is > on computers with no special hardware requirements > (e.g., no parport or interface cards) > > by_interface -- configurations based on particular interface > hardware > > by_machine -- configurations based on a particular machine > > attic -- obsolete or non-working configurations which > may still be useful for study or revival > > This structure is intended to present a simpler view of the > available configurations and provide more flexibility in arranging > configurations as they are added, modified, or relocated. > > The configuration picker has been updated so that it places > user selected configurations in a flat structure, so that the > config offered in the hierarchy as: > sim/axis/gladevcp > is stored in the user home directory as: > ~/linuxcnc/configs/sim.axis.gladevcp > > When a config is reselected, it is placed with a modified > name, for example: > ~/linuxcnc/configs/sim.axis.gladevcp-1 > > The configuration picker now supports copying a configuration > subdirectory subject to a few rules. Details are listed > in the file: > configs/maintainer.txt > > Any config directory can include a README that provides > some help or information for all the configurations in > the directory and any specific config can include a text > file that documents the specific config. For example > the config: > configs/sim/low_graphics > has a README: > configs/sim/low_graphics/README > and its example config: > configs/sim/low_graphics/keystick.ini > has a text file: > configs/sim/low_graphics/keystick.txt > > These text files are shown by the configuration picker when the > configuration tree is browsed by a user. Additions, clarifications, > and other improvements to these files are welcome. > > When configs are moved to the attic, it is probably a good idea > to note the reason in one of these documenting files. > > Both the configs directory structure and the configuration > picker have been designed with the intent that sim > configurations work in both RIP builds and deb installs. > > There are a few sim configs that do not start up, but > they did not start before these changes. These are > candidates for fixup, removal, or transfer to the attic. > > The design described above is live now on git master > and available in debs from the buildbot. > ------------------------------------------------------------------------------ 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
