|
On 15/08/17 03:29, thangle wrote:
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 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.
-- 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 [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. |
- [Machinekit] how to compile source in machinekit thangle
- Re: [Machinekit] how to compile source in m... [email protected]
- Re: [Machinekit] how to compile source ... thangle
- Re: [Machinekit] how to compile sou... [email protected]
- Re: [Machinekit] how to compile... thangle
- Re: [Machinekit] how to compile... thangle
- Re: [Machinekit] how to co... [email protected]
- Re: [Machinekit] how t... thangle
- Re: [Machinekit] h... Bas de Bruijn
- Re: [Machinekit] h... thangle
