Skip to content

Conversation

itzjakm
Copy link

@itzjakm itzjakm commented Dec 20, 2023

Basically, just some of the "id's" (I don't know how they are called) of the interfaces changed.

@3isme
Copy link

3isme commented Jan 2, 2024

confirm this works. no issues so far.

@etdr
Copy link

etdr commented Feb 2, 2024

Really frustrating that despite the great efforts of the team here the latest 22631-compatible release doesn't work with 22635 (just four more numbers! lol). Hope this gets merged soon

EDIT: Are there instructions on how to build the DLL myself from source? I am running cargo build in both the main directory and in the dll directory and don't see it output. Maybe a different cargo command?

EDIT 2: Ok I'm dumb, the current version labeled for 22631 does work on 22635. I thought I had downloaded it and replaced the previous DLL but Chrome blocked the download originally. My bad (but damn that's frustrating).

@Catalyn45
Copy link

Catalyn45 commented Mar 1, 2024

Really frustrating that despite the great efforts of the team here the latest 22631-compatible release doesn't work with 22635 (just four more numbers! lol). Hope this gets merged soon

EDIT: Are there instructions on how to build the DLL myself from source? I am running cargo build in both the main directory and in the dll directory and don't see it output. Maybe a different cargo command?

EDIT 2: Ok I'm dumb, the current version labeled for 22631 does work on 22635. I thought I had downloaded it and replaced the previous DLL but Chrome blocked the download originally. My bad (but damn that's frustrating).

You need to go into the dll directory and run cargo build --release there, and the dll should be in the target\release dir.

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 this pull request may close these issues.

4 participants