Re: [Emc-users] making a new component

[lloyd w. <llw...@ro...>]

Curious - I still have a previous source environment (emc2-dev), as well 
as a new environment
(linuxcnc-dev). Running 'which comp' from new environment gives null 
response:

    lloyd@lloyd-acer:~/linuxcnc-dev$ which comp
    lloyd@lloyd-acer:~/linuxcnc-dev$

  running from old environment finds comp - in the new environment :

      lloyd@lloyd-acer:~/emc2-dev$ which comp
      /home/lloyd/linuxcnc-dev/bin/comp

seems there is some environment variable out of alignment - and my *nix 
experience is at least a decade out of date


On 06/16/2012 10:03 PM, Kirk Wallace wrote:
> On Sat, 2012-06-16 at 19:22 -0400, lloyd wilson wrote:
>> Thanks for the quick reply; all files are in the same directory, which
>> I've tried placing in linuxcnc root and in the src directory; no change.
>> The find* scripts exist&  are executable; find-modinc is the script that
>> goes thud, even if run from the command line. Since this is a C program,
>> not a comp, is that step needed in the make process?
>>
>> -ldw
> > From this link:
> http://git.mah.priv.at/gitweb/vfs11-vfd.git/blob/master:/find-modinc
>
> it looks like it uses "which" to try to find "comp". if successful, it
> sets the "bindir" shell variable, with other variables dependent on
> "bindir".
>
> "which comp" at the command line should be equivalent, or "whereis
> comp", or just "comp" to see if comp is found.
>
> I noticed here:
> http://www.linuxcnc.org/index.php/english/component/kunena/?func=view&catid=10&id=18963
>
> that LinuxCNC 2.5 now has comp in the linuxcnc-dev package rather than
> the older emc2-dev.
> http://www.linuxcnc.org/docview/html/hal/comp.html
>
> It looks like you will need to get comp running first, so find-modinc
> can find it.
>
>