Maybe select a date which is not to far in future and see what's really
coming in.
If it's only few things, go for RC1 early, and use RC2 / 3 /...
If nothing's coming in anymore in terms of bugs, release might not be to
far away.
Daniel
Am Do., 30. Mai 2019 um 20:16 Uhr schrieb Chris Morley <
Possibly more frequent and scheduled releases (e.g. twice a year) would be
the vehicle to get more developers on board and also allow easier
stabilization due to less amount of big changes.
However the efforts for a release need to be small (best case zero due to
automation or distribution of
Hi all,
the link-time optimization as such is highly dependant on the target
architecture (as well as the compiler/linker suite of course).
While on smaller, more simple core architectures, e.g. small µCs, the
effect can be quite large, on µP architectures with complex multi level
caches,
>2) Python / GTK / that sort of stuff. Touchy / gscreen / gmoccapy don't
>work on my Stretch VM or my Stretch test machine (No Glade). Is that just
>me?
GScreen works fine for me on Stretch.
However gmoccapy complaints at start about gladevcp/iconview.py:179 and
stops.
Regards,
Daniel
Am
Hello folks,
I am currently playing with the recent 2.8 and merged my branch for a tool
changer support into the C-part of linuxcnc.
In axis all is proper, then I started to use gmoccapy and I faced a strange
situation there.
In my change.ngc macro, I show the interesting values by these lines:
are merged on the latest
2.8 branch. You can find them here:
https://github.com/mydani/linuxcnc/tree/2.8-pocket-fix
Am Mi., 18. Dez. 2019 um 07:29 Uhr schrieb mydani :
> Hello folks,
>
> I am currently playing with the recent 2.8 and merged my branch for a tool
> changer support into
Hello guys,
wish all of you a happy and healthy new year.
Hoped someone can tell me how I can run a foreign branch through the
linuxcnc build bot (or whether that's even possible).
Regards,
Daniel
___
Emc-developers mailing list
Hello Rene
Did u run all the tests successfully in your rebase? I put some changes on
top of your work, to totally distinguish between tool table index and
pocket.
Regards
Daniel
Rene Hopf via Emc-developers schrieb
am Di. 7. Apr. 2020 um 16:14:
> Hi,
> There are a few things I would like to
Hi all,
currently trying to fix some failing tests, ended up with 5 in the
tool-info folder.
Started to fix things starting from the old .ini and .hal (axis=>joints),
but now I am stuck.
Execution of the test gives mentioned error (see subject) - no additional
info, neither in any log file.
Do
+1 for focussing on quality over quantity.
1 UI is minimum due to having a reference implementation for the interfaces
as well as being able to test the overall complete SW system once before it
goes into release. Axis could be this reference UI. Then put the one fancy
most promising UI with big
Hi Reinhard,
if you have an encoder installed, in the encoder you should find a velocity
/ velocity-rpm pin with the raw encoder values.
They should be linked to spindle.0.speed-in.
Regards,
Daniel
Am Do., 14. Mai 2020 um 09:07 Uhr schrieb Reinhard <
reinha...@schwarzrot-design.de>:
> Hi,
Maybe you should also check-out NativeCAM, which is basically a UI and
wizards made of O-code.
Regards,
Daniel
Am Mo., 7. Juni 2021 um 04:22 Uhr schrieb Feral Engineer <
theferalengin...@gmail.com>:
> I'm gonna look at your project to help wrap my head around C. It might be
> helpful for me
>
12 matches
Mail list logo
