That is what I have been told multiple times... Yet, thread:getError() *still* returns the last error message from a thread forever. if not data.updated then -- need that flag to bypass updates - simple and hackable print("[Server]:","Client ".. data.nick .." needs to be upd...

Is there a way to know the progress of data transmitting? Say, I'm sending a file of 10Mb. I need to give some feedback to a client. Currently it's just a flashing message "Getting updates", but how about a progress bar? I'm sending data like this: client:send("here's your data",...

Can I do something about it on a ./configure stage? Maybe "ln -s" every other header to where it should be on Debian-based (one of those where love2d understands where and what to search) systems?

I have api-headers installed alright. It didn't want to build some module/lib w/o that (forgot which). Also, greping was successful. grep -rF EINPROGRESS /usr/include /usr/include/X11/Xtrans/Xtranssock.c:#define EINPROGRESS WSAEINPROGRESS /usr/include/X11/Xtrans/Xtranssock.c: * If the error was EWOU...

Or, you could have passed full path to gcc in configure flags, or in config file. That said, having foreign compiler as default indicates that your installation is botched. You may want to try again, more carefully. Ah.... No offense, but do you even have a copy of slitaz installed? All I did was ....

I've removed mingw (although I'll need it later for a different project) and tried again.
Automagic and configure went just fine.
Here's make output: click (Warning! VERY huge.)
Now it uses g++ O_o

raidho36 wrote: ↑Wed Jul 12, 2017 7:54 pm readme info

Sorry, but I'm able to read readmes. What you've mentioned is exactly what I've done. All goes well up until make stumbles upon enet.

Edit: I *do* have mingw installed, could it be mingw is being "chosen" to build love?

Since I have found no ready-to-use package and debian packages require newer core libs (like libc) I started my struggles to build love2d for SliTaz rolling. Note: I'm using a 0.9.2 codebase. The first step was to build DevIL. Done that (w/o libsquash). Then there were several dependency-related iss...

A thread is "killed" when it returns; that should be enough. Except when an error occurs in a thread. Then it (a thread) seems to not exit at all. I can do thread:getError() as many times as I want till the rest of the lifespan of the main app that has created that thread in the first pla...

I believe that, once you've yielded the coroutine... I'm using love.thread rather than coroutines. Actually, there's no way to kill a server too - no server:stop() or any other equivalent. Not sure nilling will do the job and underlying eNet will acknowledge the fact that the nilled server is no mo...