On 20/02/17 23:29, mung kie wrote:
On Saturday, February 18, 2017 at 11:40:46 AM UTC, Schooner
wrote:
Hi
Just a straw poll, to see if anyone is using webtalk and if
they are,
from packages or a RIP?
There is an opportunity to reduce the dependencies for
Machinekit, by
making webtalk an optional extra in a build.
Only if selected would libwebsockets be required.
This would speed up builds slightly, plus reduce the
dependencies and
binary footprint for the vast majority of users.
Affirmative responses only required
Thanks
I would say keep it in the build, it is a possibly useful
piece of infrastructure, I have tried using it but it did not
seem very userfriendly and so never went further than trying
to compile it.
..... Keep it in the dist if at all possible.
It will not be disappearing from the code, just not built by default
for all packages, if no-one uses it.
./configure --enable-webtalk is the proposed way to build it if
required
--
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.
|
