On Sunday 30 June 2019 08:29:56 Nathan Hartman wrote: > On Fri, Jun 28, 2019 at 4:52 PM Gene Heskett <[email protected]> wrote: > > On Friday 28 June 2019 15:08:01 Nathan Hartman wrote: > > > Studying the build system and I'm stumped on how motmod gets > > > built. > > > > > > I see in src/Makefile, motmod-objs > > > gets emc/motion/motion.o, emc/motion/command.o, etc., but where > > > are these object files being built from the .c files? Submakefile > > > under emc/motion only copies headers to ../includes. There is > > > nothing to compile these source files. > > > > > > Thanks > > > > Beats me Nathan, but it worked for me for a full stretch and is > > running my lathe, from Wed evening to about 2 hours ago when I > > thought maybe I'd see if RealtimePi would build me a working > > realtime buster image. On the pi no less. So I went out and shut > > down LCNC, and its munching along on that process now. > > Well that's great but it doesn't help me!! > > Does anyone else know? > > I see where the .o files are listed but somewhere in the makefile or > submakefiles there must be instructions to compile from .c or .cc to > form those .o files. And I don't see it anywhere. > I think theres some minor confusion that is mixing RealtimePi and linuxcnc here.
They are 2 separate builds. You use RealtimePi to make a realtimepi out of a std raspian stretch-full. I worked on a 60GB ssd plugged into the pi to do that, and I added a 10GB swap partition to its fstab. I moved that image to a u-sd, rebooted the pi to it and made everything work, then followed the directions from the linuxcnc.org site to build your own copy of master, making sure the set the arch to arm. That will need more stuff installed by apt to make lcnc, and that makes a deb that will need a few more things installed before you're done and as a final step you'll probably need to sudo apt --fix-broken, which didn't take long. And I have a 99.999% working LCNC on a full stretch install. But the new video drivers are not in the 4.14.nn-rt-v7 kernel, so the video is still slow. They will be partially supported in the 4.9.50-rt-v7 kernel that should be in buster. LCNC has had a css bug since forever, and this didn't fix it. The problem is it will NOT reload the exact same code unless the css mode is exited, or lcnc is restarted. It will rerun it ok, but you can't edit it, save it, and reload it without first going to the midi commandline and issueing a G95 first which apparently forces it out of css mode. Not a huge bug, but the error msg is wrong. Accusing one of leaving out the S value when the command to enable css is encountered in known good gcode. Not a huge deal unless you use css a lot. The lathe.pawn is a prime candidate to exercise that code if you add it, its not in the examples shipped. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
