Michał Geszkiewicz pravi:
> How to use git: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Git
>
> Let say you have clean 'git clone' source.
>
> Latest stable release is 2.3.5 and it's officaly released.
> To get it in our source dir:
>   git branch --track v2_3_branch origin/v2_3_branch
>   git checkout v2_3_branch
>
>
> New stable release will be 2.4.0 (it's stable but there is no official 
> release and packages yet).
> - Here I've fixed bugs you've reported.
> - Here is halui unhome functionality.
> To get it in our source dir:
>   git branch --track v2.4_branch origin/v2.4_branch
>   git checkout v2.4_branch
>
>
> New developments are done in unstable branch master.
> - Here I've fixed bugs you've reported.
> - Here is halui unhome functionality.
> - Here is stepgen you're need.
> Notice: you have already master branch when you 'git clone'
> To get it in our source dir:
>   git checkout master
>
>
> regards,
> Michael
>   
As you already know I have custom stepgen and is only in 2.5~
Is there some way to include that in nex release of 2.4?

For now I copy stepgen.c from master.
There is another bug in estop latch. I have already fixed in 2.3.5 (it's 
downloaded in own folder) and works
But I cant make it work with 2.4_branch

 git branch --track v2.4_branch origin/v2.4_branch
 git checkout v2.4_branch

and I edit the estop_latch.comp and change one line to be right.
but after compiling

make clean
make
sudo make setuid

the estop latch doesn't function as should. (ie change are not applied)

What I do wrong?!?



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to