Closed HeroCC closed 6 years ago
This issue seems a bit half-and-half in terms of what's causing the problem. On one hand, we state in the README that ./gradlew install
will install native binaries to /usr/local by default unless overridden, with is a root-required directory.
On the other hand, why does Jitpack run ./gradlew install
instead of ./gradlew uploadArtifacts
, which doesn't conflict with the native platform?
I'm not certain it's a good idea to host a complex multi-project repo like Pathfinder on jitpack, since the nativeplatform backs the entire project. Maven may be supported at some point, Pathfinder isn't very high on my projects list at this time.
With the new year build season upon us, I'm curious if this if the anything's changed regarding this issue.
Pathfinder has some releases on http://dev.imjac.in/maven They are currently unstable, I'm working on getting them stable today
With GradleRIO 2018.01.11 you can use the following:
compile pathfinder()
lib library: "pathfinder"
Should this info be added to the README?
I will after work
When trying to use JitPack (a free maven repository for any public github repo) to download Pathfinder, the build fails with this error log. It looks like it is trying to install the libraries to a prefix only accessible by root. Is there a way to have it build correctly when it can't access that location? (Dumping the built objects into a local directory instead of the default global?) I made a similar ticket on JitPack here
Alternatively, is there a maven repo setup to host Pathfinder artifacts?
Thanks!