mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3461] Java library #2768
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2768
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tecnicosya on GitHub (May 29, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3461
Describe the feature request
I want to build a tool in Java using your frp.
Currently I'm using shell to call frp from my app
Describe alternatives you've considered
No response
Affected area
@fatedier commented on GitHub (May 30, 2023):
I am not familiar with Java and do not have any plans in this area.
@tecnicosya commented on GitHub (May 30, 2023):
I read frp will compile to library. But I don't know where is the documentation for it. Maybe I will used with dotnet
@Bellegar commented on GitHub (May 30, 2023):
I am not so good familiar with go, but it may helps.
Maybe it is possible to include jni dependency to cgo build for shared library. Or maybe exists some 'go-builder' for java.
For example gomobile creates AAR for android for using java interface, by pulling jni shared libraries, built by gomobile.
You can use gomobile' generated shared libs in your java code, also gomobile produces source code 'header' with 'native' directives to build jni methods.
Here is my comment about building FRP library, frp needs to change some code for minimal working as library.
@tecnicosya commented on GitHub (May 30, 2023):
@github-actions[bot] commented on GitHub (Jun 30, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.