-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore: add outline-go-tun2socks, except android #1744
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1744 +/- ##
======================================
Coverage 32% 32%
======================================
Files 45 45
Lines 2609 2609
Branches 337 337
======================================
Hits 859 859
Misses 1750 1750
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove the Intra code from this PR.
Only the Outline code should be here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @daniellacosse for the contribution, I have a question, after removing intra, shall we just embed the building process within client's npm build
action?
I was planning on adding it to the build process in the next PR. I guess with that in consideration, I can simply not add it to CI yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Daniel! This will be very helpful. The code LGTM, please remember to add a TODO comment of running go tests in the GitHub workflow.
src/tun2socks/build.action.mjs
Outdated
'.' | ||
); | ||
|
||
return spawnStream('cp', `${buildDir}/tun2socks-windows-386.exe`, `${buildDir}/tun2socks.exe`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, maybe add a TODO in case anyone in the future would like to investigate into that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome. Thanks for the change! Once we have tun2socks fully in the client it will enable a lot more progress!!! No more need to release outline-go-tun2socks!
IMPORT_HOST=github.com | ||
IMPORT_PATH=$(IMPORT_HOST)/Jigsaw-Code/outline-client |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, IMPORT_HOST just hurts readability. I see it was already there, no need to change in this PR.
IMPORT_HOST=github.com | |
IMPORT_PATH=$(IMPORT_HOST)/Jigsaw-Code/outline-client | |
IMPORT_PATH=github.com/Jigsaw-Code/outline-client |
@fortuna Do you mind if I modify the Makefile such that it uses Also trying to figure out what happened to the Android NDK. |
That's fine for now. Perhaps add a TODO to build windows directly without xgo when on windows. |
Ah, my old friend, Thanks @bemasc ! |
This reverts commit e8dcd79.
For now we're not copying the Android build over until we figure out what's going on there.
Issues
is it because it's also
package main
?