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.

Sign up for GitHub

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

Jump to bottom

Use different library for CPPNWIN than multineat #233

Closed
surgura opened this issue May 25, 2023 · 1 comment · Fixed by #260
Closed

Use different library for CPPNWIN than multineat #233

surgura opened this issue May 25, 2023 · 1 comment · Fixed by #260
Assignees
@surgura @BannoPostma
Labels
refactor
Milestone
beta2

Comments

@surgura
Copy link
Contributor

surgura commented May 25, 2023

No description provided.

@surgura surgura added this to the beta2 milestone May 25, 2023
@surgura surgura self-assigned this Sep 5, 2023
@surgura
Copy link
Contributor Author

surgura commented Sep 5, 2023

See #259 . for now we will build multineat in the ci so that at least most problems are gone.

@surgura surgura linked a pull request Sep 6, 2023 that will close this issue
Depend on multineat from pypi (we ourselves added that deployment in our multineat fork) instead of building it from source. #260
Merged
@surgura surgura closed this as completed Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@surgura surgura

@BannoPostma BannoPostma

Labels
refactor
Projects
None yet
Milestone
beta2
2 participants
@surgura @BannoPostma