Ok Russell, I concede, the make file is much better and robust. I will be using that for now I think. The main reason that I say this is because it is very easy for me to now store stuff in related directories and then just retrieve them with paths set up in the make file :) And I understand makefiles a bit better that scripts, I think.
On 2014-02-13 11:59, Marius Liebenberg wrote: > All true as you said. I am sure that makefile will work as well I just > thought the script will be very easy for non programmers to use. > I will test the make file route as well and see what is the easier > solution to use. Or offer both. > > > > On 2014-02-13 11:36, Russell Brown wrote: >> Quoth Marius Liebenberg..... >>> Sorry to bug you with this but I am not well versed with the scripting >>> stuff. >> Aren't all these scripts just reinventing the wheel? >> >> Make(1) has existed for decades so put sommat like the following into a >> file called 'makefile': >> >>> # >>> #My Makefile for INI files >>> # >>> INIPARTS1=motion.ini display.ini emc.ini wibble.ini >>> INIPARTS2=steppermotion.ini display.ini emc.ini >>> >>> machine1.ini: $(INIPARTS1) >>> cat $(INIPARTS1) > machine1.ini >>> >>> machine2.ini: $(INIPARTS2) >>> cat $(INIPARTS2) > machine2.ini >> Twiddle with your file content, type 'make' to build machine1.ini (the >> default in the above) or 'make machine2.ini' to build that. >> >> Just a thought. >> -- Regards /Groete Marius D. Liebenberg +27 82 698 3251 +27 12 743 6064 ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
