objectbox / objectbox/objectbox-java
Changing destination directory of native libraries
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.6k
- Forks
- 311
- PR merge metrics
- No merged PRs in 30d
Description
Description
I use ObjectBox as a database in a Java Desktop App. My build tool is gradle and I add ObjectBox dependencies manually without dedicated plugin.
Code fragment I use to add dependency is like:
dependencies {
implementation(group = "io.objectbox", name = "objectbox-java", version = "2.9.1")
implementation(group = "io.objectbox", name = "objectbox-windows", version = "2.9.1")
annotationProcessor(group = "io.objectbox", name = "objectbox-processor", version = "2.9.1")
}
After project build I can use library without any problems, but in my root directory file objectbox-jni-windows-x64.dll with native library is added and I cannot change the output path for the native library file.
Requested feature
Possibility to configure custom directory, where native libraries will be placed after dependency import. Best option would be to configure it in gradle script during import as I can configure model path and MyObjectBox package.
Thanks in advance for all help and tips.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the manual Gradle dependency setup described in the issue and trace where objectbox-jni-windows-x64.dll is placed during the build. Identify the relevant native-library extraction or packaging entry point; done means the destination can be configured in the Gradle script and the library is placed there without breaking use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100