> On 15 Aug 2017, at 10:40, thangle <lethang12...@gmail.com> wrote: > > Thank for your answer. > > > Because you have changed one but not the other. > You have 2 different machinekit installations, one in the binary file system > and another, which you built, in your home directory. > > If you want to test your new *kins, run the one which contains it, in your > home dir, from a terminal. > > i have a problem that I cant find the executable file of new kins after built > it.
use some google-fu, it’s bound to bring up something like “sudo find / -name trivkinstest” > > > I won't even try to explain how to add your new module to the binary file > system, there is no need to do it. > > The whole point about a RIP build is that it is self contained and you can > experiment without messing up the main installation. > But as schooner stated, you should be able to run your compiled version independent of the pre-installed binaries. Taken from http://www.machinekit.io/docs/developing/machinekit-developing/ : However, if you are installing a RIP build onto a system that already has a version of Machinekit installed as a binary install from packages say, or has other RIP builds, you should invoke from the root dir of the RIP, . ./scripts/rip-environment so open a new terminal, cd to where installed your compiled version, (for example ~/machinekit if you installed in your home directory) and run the above command before you start machinekit from _that same_ terminal. >> >> >> Either that or copy the new module to your binary install and run ldconfig >> manually and check it is in the cache >> >> i dont know where is the new module, binary place? how to check it in cache >> by ldconfig? >> >> thank you for your help very much. >> >>> rpath=/usr/lib/linuxcnc/xenomai >>> See /var/log/linuxcnc.log for more information. >>> 10047 >>> PID TTY STAT TIME COMMAND >>> Stopping realtime threads >>> Unloading hal components >>> >>> i'm using BBB and machinekit. sorry for my trash English. >>> >>> Vào 15:41:12 UTC+7 Thứ Hai, ngày 14 tháng 8 năm 2017, Schooner đã viết: >>> Going to need a lot more info than that and to see the source. >>> >>> You basically need to know how to write Makefiles, to alter the existing >>> ones to build your stuff too, assuming it is compatible. >>> >>> On 14/08/17 03:39, thangle wrote: >>>> Hi, >>>> >>>> Does anyone know how to compile a new source? example, i coppy a new C >>>> project from an old project in machinekit src and rename, what should i do >>>> to make it work. please help me. tks >>>> -- >>>> website: http://www.machinekit.io <http://www.machinekit.io/> blog: >>>> http://blog.machinekit.io <http://blog.machinekit.io/> github: >>>> https://github.com/machinekit <https://github.com/machinekit> >>>> --- >>>> You received this message because you are subscribed to the Google Groups >>>> "Machinekit" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to machinekit+...@googlegroups.com <>. >>>> Visit this group at https://groups.google.com/group/machinekit >>>> <https://groups.google.com/group/machinekit>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> -- >>> website: http://www.machinekit.io <http://www.machinekit.io/> blog: >>> http://blog.machinekit.io <http://blog.machinekit.io/> github: >>> https://github.com/machinekit <https://github.com/machinekit> >>> --- >>> You received this message because you are subscribed to the Google Groups >>> "Machinekit" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to machinekit+...@googlegroups.com <>. >>> Visit this group at https://groups.google.com/group/machinekit >>> <https://groups.google.com/group/machinekit>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> -- >> website: http://www.machinekit.io <http://www.machinekit.io/> blog: >> http://blog.machinekit.io <http://blog.machinekit.io/> github: >> https://github.com/machinekit <https://github.com/machinekit> >> --- >> You received this message because you are subscribed to the Google Groups >> "Machinekit" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to machinekit+...@googlegroups.com <javascript:>. >> Visit this group at https://groups.google.com/group/machinekit >> <https://groups.google.com/group/machinekit>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > website: http://www.machinekit.io <http://www.machinekit.io/> blog: > http://blog.machinekit.io <http://blog.machinekit.io/> github: > https://github.com/machinekit <https://github.com/machinekit> > --- > You received this message because you are subscribed to the Google Groups > "Machinekit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to machinekit+unsubscr...@googlegroups.com > <mailto:machinekit+unsubscr...@googlegroups.com>. > Visit this group at https://groups.google.com/group/machinekit > <https://groups.google.com/group/machinekit>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
