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.
 

>
> 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.
>
>
>
>> 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 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.
>>>
>>>
>>> -- 
>> 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.
>>
>>
>> -- 
> 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] <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit 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 [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to