Ed,
I was considering the use of EOC, but I use my engine on
Windows and Linux. It seems you coded the tools for DOS.
This may not be a problem. I don't mind editing the EOC
databases on MS as long as I can access the database
for an opening book from my engine when it runs on Linux.
This comes down to - can eoc.c (which is what I think integrates
with the engine) be compiled an run on Linux?
Charles
EOC Databases and Linux
Moderators: hgm, Rebel, chrisw
-
- Posts: 2055
- Joined: Mon Mar 13, 2006 2:31 am
- Location: North Carolina, USA
Re: EOC Databases and Linux
C should be C. But I don't know if Linux C = MS C. I would say, just compile the thing and if the test stuff in main() works it is ok.
Ed
Ed
CRoberson wrote:Ed,
I was considering the use of EOC, but I use my engine on
Windows and Linux. It seems you coded the tools for DOS.
This may not be a problem. I don't mind editing the EOC
databases on MS as long as I can access the database
for an opening book from my engine when it runs on Linux.
This comes down to - can eoc.c (which is what I think integrates
with the engine) be compiled an run on Linux?
Charles
Re: EOC Databases and Linux
Hi Ed
I was thinking of using the EOC data as well, and wanted to know if it would be ok with you if I were to port your code to Java?
Regards,
Vince
I was thinking of using the EOC data as well, and wanted to know if it would be ok with you if I were to port your code to Java?
Regards,
Vince
Re: EOC Databases and Linux
No problem, good luck.mambofish wrote:Hi Ed
I was thinking of using the EOC data as well, and wanted to know if it would be ok with you if I were to port your code to Java?
Regards,
Vince
Ed
-
- Posts: 2055
- Joined: Mon Mar 13, 2006 2:31 am
- Location: North Carolina, USA
Re: EOC Databases and Linux
Hi Ed,
Thanks for the response. Actually, Unix C != MS C.
It should but, MS lets you cut corners. One example is the opening
of files as binary. MS lets you cut that corner and Unix doesn't.
My experience is that if it is not a GUI and it works in Unix then
it will work in MS. But, the reverse is not true. There are a few
exceptions.
Thanks, I'll give it a go.
Charls
Thanks for the response. Actually, Unix C != MS C.
It should but, MS lets you cut corners. One example is the opening
of files as binary. MS lets you cut that corner and Unix doesn't.
My experience is that if it is not a GUI and it works in Unix then
it will work in MS. But, the reverse is not true. There are a few
exceptions.
Thanks, I'll give it a go.
Charls