jnr / jffi

Java Foreign Function Interface
Apache License 2.0
168 stars 78 forks source link

Corrected RTLD-accessing logic needs to be in a major release #16

Open headius opened 9 years ago

headius commented 9 years ago

I just reverted the changes in b6d8a9f (via 9c5a0771884179b0b57dafa2063f6402eb190bab) by @tduehr, not because they weren't the right thing to do, but because they will require us to rebuild the native library across all platforms. This was preventing us from releasing jffi 1.2.8 and bumping upstream projects to depend on it, which has in turn blocked numerous important jffi fixes from getting into the hands of users.

We'll need to talk about a strategy for making this change and getting all our binaries rebuilt, and any changes to the native bits probably needs to happen in a major release (a 1.3 or 2.0, depending on what our versioning considers major).

cc @enebo

tduehr commented 9 years ago

well... it's not a breaking change, but corrects a bug. so 1.3?

I should have VMs almost ready to go for rebuilding these I just need to figure out java for them i think.

The only ones I can't do are the sparc ones and aix. everything else should be supported by debian and easy to get up and running.

headius commented 9 years ago

@tduehr 1.3 sounds fine, and it will force us to get a set of build VMs for future platform support.

Let me know if there's anything I can do to help with the VM setup. I will poke around about sparc and aix. Worst case we could book some time occasionally on a sparc-based cloud provider, and there's probably something similar for AIX. In any case, we're at least reducing the number of libs we need third parties to build for us.

tduehr commented 9 years ago

I know Solaris does it for Sparc and I'm pretty sure IBM does the same for AIX. Perhaps we can set something up with them directly?

DemiMarie commented 8 years ago

Can the native library be cross-compiled from a common architecture?