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

Not all library aliases tested #406

Closed
operutka opened this Issue May 30, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@operutka

operutka commented May 30, 2013

Hi,
I found this issue inside the BridJ.findNativeLibraryFile() method. Following code prevents iteration over all elements inside the possibleNames list:

            try {
                File f;
                if (isAndroid())
                    f = new File("lib" + name + ".so");
                else
                    f = extractEmbeddedLibraryResource(name);

                if (f == null || !f.isFile())
                    throw new FileNotFoundException(StringUtils.implode(possibleNames, ", "));

                return f;
            } catch (IOException ex) {
                throw new RuntimeException(ex);
            }

ochafik added a commit that referenced this issue May 30, 2013

@ochafik

This comment has been minimized.

Show comment
Hide comment
@ochafik

ochafik May 30, 2013

Member

Hi @DaemonXY ,

Thanks a lot for spotting this!
I've pushed a fix in the latest 0.7-SNAPSHOT, please let me know if you face any issue :-)

Cheers

Member

ochafik commented May 30, 2013

Hi @DaemonXY ,

Thanks a lot for spotting this!
I've pushed a fix in the latest 0.7-SNAPSHOT, please let me know if you face any issue :-)

Cheers

@ochafik ochafik closed this May 30, 2013

@operutka

This comment has been minimized.

Show comment
Hide comment
@operutka

operutka May 31, 2013

Thanks for the fix. My library is built upon the latest stable BridJ version 0.6.2 and this bug makes it unusable on Win32/64 platform. Are you going to release a fix also for this version?

operutka commented May 31, 2013

Thanks for the fix. My library is built upon the latest stable BridJ version 0.6.2 and this bug makes it unusable on Win32/64 platform. Are you going to release a fix also for this version?

@ochafik

This comment has been minimized.

Show comment
Hide comment
@ochafik

ochafik Jun 5, 2013

Member

Hi @DaemonXY ,
I expect to be able to perform a release in the next week.
Cheers

Member

ochafik commented Jun 5, 2013

Hi @DaemonXY ,
I expect to be able to perform a release in the next week.
Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment