Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Running engines which are runnable jar files #1022

Open
erberj opened this issue Sep 22, 2024 · 2 comments · May be fixed by #1023
Open

Enable Running engines which are runnable jar files #1022

erberj opened this issue Sep 22, 2024 · 2 comments · May be fixed by #1023

Comments

@erberj
Copy link

erberj commented Sep 22, 2024

My engine is written in Scala and has no binary (exe) but a runnable jar file

Instead of dir and name of the engine, I suggest to have a run-command variable, where i can enter something like:
run-command = "java -jar myengine.jar [parameters]"

Best Regards
Jakob Erber

@MarkZH
Copy link
Collaborator

MarkZH commented Sep 23, 2024

This is probably a good idea. We'll have to think about how to implement it. In the meantime, you can create an executable with a batch script.

Make a text file with the command to run your engine:

java -jar myengine.jar [parameters]

Save it to the lichess-bot/engines/ folder as myengine.bat if on Windows or myengine.sh on Linux/Mac.

If on Linux/Mac, give that batch script execution permission: chmod +x myengine.sh.

Finally, in your config.yml file, use the name and location of this script.

engine:
  dir: engines
  name: myengine.bat # or .sh

Everything else in config.yml is the same. I picked the engines/ directory in the lichess-bot folder for convenience.

@erberj
Copy link
Author

erberj commented Sep 23, 2024 via email

@AttackingOrDefending AttackingOrDefending linked a pull request Sep 23, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants