07-10-2016, 01:13 PM
Porting the new pilight version to windows seems to be a lot harder than i expected. The biggest drawback is that in linux, everything can be polled by poll (e.g. sockets, serial, files, pipes, etc) but in windows only sockets work through select (poll is not supported). So get console input, socket communication, serial io, in a non-blocking manner to work major work needs to be done.
I tried to walk that path to port the pilight eventing system to windows, but i'm currently investigating if libuv does what i need. libuv is the main eventing library used in NodeJS and does nearly everything we need. To speed up this investigation is trying to make proof of concepts or even port parts of the new pilight rewrite code to libuv.
The biggest problem at this moment is getting the pilight usb nano to work on windows. If someone can create a proof of concept for the 433nano hardware module in libuv that would greatly reduce my development time.
Creating multiplatform proof-of-concepts for the threadpool, socket communication, console input is also appreciated.
At least you guys know what i'm working on at the moment.
But first, i'm going to enjoy my holiday vacation.
I tried to walk that path to port the pilight eventing system to windows, but i'm currently investigating if libuv does what i need. libuv is the main eventing library used in NodeJS and does nearly everything we need. To speed up this investigation is trying to make proof of concepts or even port parts of the new pilight rewrite code to libuv.
The biggest problem at this moment is getting the pilight usb nano to work on windows. If someone can create a proof of concept for the 433nano hardware module in libuv that would greatly reduce my development time.
Creating multiplatform proof-of-concepts for the threadpool, socket communication, console input is also appreciated.
At least you guys know what i'm working on at the moment.
But first, i'm going to enjoy my holiday vacation.