Moby Dam
Re: Moby Dam
Thank you. The option: -march=native works
Re: Moby Dam
Hello,
this is my first message here
Have used MinGW to compile Mobydam.exe for non-popcnt processors (non-popcnt)
Here is the link:
http://rghost.net/6gVZVhl2V
Enjoy!
Michael Taktikos
P.S. Had not success to compile Scan 20 for non-popcnt, the MinGW compiler doesn't support pthread with std:mutex. Can someone who has a VC++ -Compiler compile it? Thx
this is my first message here
Have used MinGW to compile Mobydam.exe for non-popcnt processors (non-popcnt)
Here is the link:
http://rghost.net/6gVZVhl2V
Enjoy!
Michael Taktikos
P.S. Had not success to compile Scan 20 for non-popcnt, the MinGW compiler doesn't support pthread with std:mutex. Can someone who has a VC++ -Compiler compile it? Thx
-
- Posts: 22
- Joined: Wed Mar 19, 2014 12:59
- Real name: Arthur Kalverboer
- Location: Groningen, The Netherlands
Re: Moby Dam
Harm,
Just a question that I would like an answer.
WebSockets represent a big step in the evolution of the internet.
Can Moby Dam run as a WebSocket server?
If not, do you plan to facilitate this change by the opensource-community?
Arthur
Just a question that I would like an answer.
WebSockets represent a big step in the evolution of the internet.
Can Moby Dam run as a WebSocket server?
If not, do you plan to facilitate this change by the opensource-community?
Arthur
-
- Posts: 43
- Joined: Thu Sep 24, 2009 18:17
Re: Moby Dam
Hmm, I imagine WebSocket to be suitable for a draughts GUI in a web browser, talking to an engine on a server.
On the server side you would need a web server that sends the GUI Javascript/HTML5 code to the browser and then keeps a WebSocket channel open to communicate.
The web server could connect to the draughts engine through CGI pipes, so the engine would not need to know about WebSocket and GUI stuff.
Changing Moby Dam to use pipes instead of sockets is easy.
That leaves open the question of what protocol to use between GUI and engine.
DamExchange is very minimalistic, I imagine you would want a richer set to handle configuration/setup, progress info, etc.
Have a look at the "Protocols and Tools" topic here on the board.
On the server side you would need a web server that sends the GUI Javascript/HTML5 code to the browser and then keeps a WebSocket channel open to communicate.
The web server could connect to the draughts engine through CGI pipes, so the engine would not need to know about WebSocket and GUI stuff.
Changing Moby Dam to use pipes instead of sockets is easy.
That leaves open the question of what protocol to use between GUI and engine.
DamExchange is very minimalistic, I imagine you would want a richer set to handle configuration/setup, progress info, etc.
Have a look at the "Protocols and Tools" topic here on the board.
-
- Posts: 22
- Joined: Wed Mar 19, 2014 12:59
- Real name: Arthur Kalverboer
- Location: Groningen, The Netherlands
Re: Moby Dam
Subject: Moby Dam as WebSockets server.
I think instead of CGI pipes you can use the Websockets daemon as described at http://websocketd.com/
This program turns any program (written in whatever language) that uses STDIN/STDOUT into a WebSocket server.
For this to work, Moby Dam has to be changed to an input/output program (handling incoming and outgoing messages).
Or am I wrong?
Maybe the biggest challenge is to define and implement a new extended damexchange protocol for websockets. The design must be based on a browser client that does not need to know the rules of draughts. So a request to Moby Dam like "what are the legal moves" must be part of it.
I also worry how to handle multiple browser clients (maybe it must be limited to one?).
I have to study what is known at the "Protocols and tools" topic.
I think instead of CGI pipes you can use the Websockets daemon as described at http://websocketd.com/
This program turns any program (written in whatever language) that uses STDIN/STDOUT into a WebSocket server.
For this to work, Moby Dam has to be changed to an input/output program (handling incoming and outgoing messages).
Or am I wrong?
Maybe the biggest challenge is to define and implement a new extended damexchange protocol for websockets. The design must be based on a browser client that does not need to know the rules of draughts. So a request to Moby Dam like "what are the legal moves" must be part of it.
I also worry how to handle multiple browser clients (maybe it must be limited to one?).
I have to study what is known at the "Protocols and tools" topic.
Re: Moby Dam
Hello friends!
Can someone kindly make a compilation for MobyDam to work on a 32-bit system?
I'm making the same request do Scan engine.
Thank you very much.
Can someone kindly make a compilation for MobyDam to work on a 32-bit system?
I'm making the same request do Scan engine.
Thank you very much.
-
- Posts: 43
- Joined: Thu Sep 24, 2009 18:17
Re: Moby Dam
A new version of Moby Dam is now available for your perusal.
This is the version that I used past weekend in the Computer Olympiad 2016.
Go to http://hjetten.home.xs4all.nl/mobydam/mobydam.html
See the bottom of the page, "second release."
The zip file contains the source as well as a 64-bit Windows executable.
Enjoy!
This is the version that I used past weekend in the Computer Olympiad 2016.
Go to http://hjetten.home.xs4all.nl/mobydam/mobydam.html
See the bottom of the page, "second release."
The zip file contains the source as well as a 64-bit Windows executable.
Enjoy!
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Moby Dam
We sincerely thank you for sharing Harm.
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Moby Dam
Hi Harm.
I have a question about the program WinTail. Is there a possibility that when you run a program shortcut WinTail, the program directly open the file engine. Do you have to show the engine every time and then the program will open that file.
Krzysztof.
I have a question about the program WinTail. Is there a possibility that when you run a program shortcut WinTail, the program directly open the file engine. Do you have to show the engine every time and then the program will open that file.
Krzysztof.
-
- Posts: 22
- Joined: Wed Mar 19, 2014 12:59
- Real name: Arthur Kalverboer
- Location: Groningen, The Netherlands
Re: Moby Dam
I try to compile mobydam with Linux Mint.
I get an error:
==============================================
arthur@pluto ~/mobydam/main $ make
gcc -g -O3 -Wall -mpopcnt -flto -DPF -DETC -DLMR -DKIL -DCUT -DCFLAGS="-g -O3 -Wall -mpopcnt -flto -DPF -DETC -DLMR -DKIL -DCUT" -c dxp.c
In file included from main.h:20:0,
from dxp.c:22:
../core/core.h:26:22: fatal error: sys/time.h: Bestand of map bestaat niet
#include <sys/time.h>
^
compilation terminated.
Makefile:24: recept voor doel 'dxp.o' is mislukt
make: *** [dxp.o] Fout 1
arthur@pluto ~/mobydam/main $
==============================================
How can I solve this problem?
I get an error:
==============================================
arthur@pluto ~/mobydam/main $ make
gcc -g -O3 -Wall -mpopcnt -flto -DPF -DETC -DLMR -DKIL -DCUT -DCFLAGS="-g -O3 -Wall -mpopcnt -flto -DPF -DETC -DLMR -DKIL -DCUT" -c dxp.c
In file included from main.h:20:0,
from dxp.c:22:
../core/core.h:26:22: fatal error: sys/time.h: Bestand of map bestaat niet
#include <sys/time.h>
^
compilation terminated.
Makefile:24: recept voor doel 'dxp.o' is mislukt
make: *** [dxp.o] Fout 1
arthur@pluto ~/mobydam/main $
==============================================
How can I solve this problem?
Re: Moby Dam
Did you install the linux-libc-devel package?
Lasst die Maschinen verhungern, Ihr Narren...
Lasst sie verrecken!
Schlagt sie tot -- die Maschinen!
Lasst sie verrecken!
Schlagt sie tot -- die Maschinen!
-
- Posts: 22
- Joined: Wed Mar 19, 2014 12:59
- Real name: Arthur Kalverboer
- Location: Groningen, The Netherlands
Re: Moby Dam
I have checked it.
linux-libc-devel Installed version 4.4.0-62.83
linux-libc-devel Installed version 4.4.0-62.83
-
- Posts: 22
- Joined: Wed Mar 19, 2014 12:59
- Real name: Arthur Kalverboer
- Location: Groningen, The Netherlands
Re: Moby Dam
I fix the problem with the compile error on my Linux Mint system.
The compiler gives an error at: #include <sys/time.h> (not found)
Clearly a lot of files were missing.
The problem is solved by installing the package build-essential.
Now it compiles mobydam with no errors and I could start it succesfully.
I hope this helps others with the same kind of problem.
The compiler gives an error at: #include <sys/time.h> (not found)
Clearly a lot of files were missing.
The problem is solved by installing the package build-essential.
Now it compiles mobydam with no errors and I could start it succesfully.
I hope this helps others with the same kind of problem.
Re: Moby Dam
Did a Mint install in a VM, and found out that the package which contains sys/time.h (to be found in /usr/include/x86_64-linux-gnu) is libc6-dev.
Lasst die Maschinen verhungern, Ihr Narren...
Lasst sie verrecken!
Schlagt sie tot -- die Maschinen!
Lasst sie verrecken!
Schlagt sie tot -- die Maschinen!
-
- Posts: 1722
- Joined: Wed Apr 14, 2004 16:04
- Contact:
Re: Moby Dam
build-essential is a package that bundles modern versions of gcc/g++, make, and the low-level libc libraries.ildjarn wrote:Did a Mint install in a VM, and found out that the package which contains sys/time.h (to be found in /usr/include/x86_64-linux-gnu) is libc6-dev.