gpu / JOCLBlast

JOCLBlast - Java bindings for CLBlast
Other
14 stars 4 forks source link

Release 1.5.1 #16

Closed gpu closed 3 years ago

gpu commented 4 years ago

Version 1.5.1 of CLBlast has been released: https://github.com/CNugteren/CLBlast/releases/tag/1.5.1

This issue is intended as a tracker/"todo" for the corresponding JOCLBlast update. (No timeline yet, I currently have some other time-critical tasks, but as usual, the update will be done "ASAP"...)

gpu commented 3 years ago

There has not been any change in the API for 1.5.1. This indicates proper semantic versioning, but also means that there is no excuse for the fact that the ""update"" of JOCLBlast took so long...

The release candidate for 1.5.1 is at https://github.com/gpu/JOCLBlast/tree/1.5.1-RC00

@blueberry If you are still willing to build the binaries, despite all the delays on my side, note that this version is supposed to be built against https://github.com/CNugteren/CLBlast/releases/tag/1.5.1 (which is not the latest one).

The update for 1.5.2 will follow soon. (I didn't want to put this update on top of the current state, to prevent Maven from messing up version numbers during the release...)

blueberry commented 3 years ago

@gpu Thank you! Yes, I will build it. I just need some time to do it since I'm on a different computer now and I'll need to do the setup too, and the following week will be extremely busy. But I hope the next weekend is not too late.

blueberry commented 3 years ago

Hi @gpu Here's the linux build of JOCLBlast 1.5.1. Sorry for the delay. Fortunately, now I have everything set up for this build, so I'll be able to build 1.5.2 as soon as you release it.

[jocl-blast-1.5.1-SNAPSHOT.zip](https://github.com/gpu/JOCLBlast/files/5975507/jocl-blast-1.5.1-SNAPSHOT.zip)
gpu commented 3 years ago

@blueberry Thanks. The archive apparently does not contain the corresponding CLBlast library. (The internal process is to first load the CLBlast DLL/SO from the JAR, and then load the JOCLBlast DLL/SO from the JAR, which requires the CLBlast one to be loaded already). You should already have that in your CLBLast build folder. If you can provide it, I'll create the release ASAP.

blueberry commented 3 years ago

Sorry, I must have missed some step in the build process. I thought that libclblast would be bundled automatically. Anyway, here's the libclblast binary. libclblast.zip

gpu commented 3 years ago

@blueberry Sorry for bugging you, but last time you also provided the MacOS binaries, but it was already a bit complicated.... I'm not entirely up to date, but from your perspective (and your experience with your libraries, and the users of these libraries): Do you think that there is demand for JOCL(Blast) on Mac? Otherwise, we could consider dropping the support, and do a Win+Linux release only this time....

blueberry commented 3 years ago

Sorry, I totally forgot about that. I'll try to build it. My old Mac is on its deathbed and I only use it rarely, so I'll have to see how I did it last time, but I think it's definitely worth supporting, since there are lots of Mac users that would at least like to use OpenCL support for learning and experimenting.

gpu commented 3 years ago

I can imagine that "reviving" a retired PC just for a compilation is a bit of a hassle. We could ask the guy who recently provided the (core) JOCL natives libs for MacOS (even though he would have to set up CLBlast for that). Do you think that this could make sense?

blueberry commented 3 years ago

I'll try to work on this later this evening

blueberry commented 3 years ago

JOCLBlast-1.5.1-macos.zip

gpu commented 3 years ago

Version 1.5.1 is on its way into Maven Central, to be available at

<dependency>
    <groupId>org.jocl</groupId>
    <artifactId>jocl-blast</artifactId>
    <version>1.5.1</version>
</dependency>

As usual, thanks @CNugteren for CLBlast, and thanks @blueberry for your continued support and providing the Linux- and Max binaries!

I'll leave this issue open until a basic test for the actual Maven dependency is done. But assuming that all went smoothly and there are no problems reported with the current release, I'd initiate the release of 1.5.2 during the weekend. It's also only a version update (and thanks to CNugteren for taking semantic version serious, by the way), and I locally already prepared everything for that, so that release could follow quickly.