sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SIS-366) sis-gdal module should not write native file in the temporary directory
Date Fri, 27 Oct 2017 12:37:00 GMT

     [ https://issues.apache.org/jira/browse/SIS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Desruisseaux updated SIS-366:
------------------------------------
    Fix Version/s:     (was: 0.8)
                   1.0

> sis-gdal module should not write native file in the temporary directory
> -----------------------------------------------------------------------
>
>                 Key: SIS-366
>                 URL: https://issues.apache.org/jira/browse/SIS-366
>             Project: Spatial Information Systems
>          Issue Type: Bug
>          Components: Storage
>    Affects Versions: 0.8
>         Environment: Linux, MacOS
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>             Fix For: 1.0
>
>
> The {{sis-gdal}} module uses Java Native Interface (JNI) for accessing the Proj.4 library.
Currently, the JNI are pre-compiled in {{storage/sis-gdal/src/main/resources/native/<OS>/libproj-binding.so}}
files where {{<OS>}} is {{linux}} or {{darwin}}. The file size is about 14 kb. Since
we can not load a library from a JAR file, we have to copy it as a regular file somewhere.
Current implementation copies it in the temporary directory.
> Problem is that some environments do not give execution permission in the temporary directory.
Consequently we should save the {{libproj-binding.so}} files somewhere else. Some possibilities
are:
> 1. Platform-specific directory like {{<user directory>/Library}} on MacOS.
> 2. A sub-directory of {{$SIS_DATA}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message