-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Linux CLI-only setup #20
Comments
Hah, an anti-request is still a feature! It'll likely need to be a build-time option, otherwise the compiled binary will get linked against WebKitGTK and require it as a dependency. I'll see what I can do to add that in. Just as a heads up - it may be some time before this is implemented- my current dev priority is getting onedriver to sync server-side changes to the local client. In the meantime, you can delete the contents of the |
Hey @rcarmo, I've rewritten things so that you can exclude WebKitGTK from the build by disabling CGo. If you build onedriver with Closed by #27 |
This would be great to document, as it greatly simplifies the CLI-only build:
I am not sure how to configure a drive instance though... |
It's no longer documented because you can just use |
But it's nice not to have to install X and all kinds of packages that you don't need. I can't use the go binary that I built somewhere else, it will not work on a headless system if I use But I am glad to report that building without CGO still works! After issuing |
Hi there!
I'd like to leave an "anti-request" here, since I would like to be able to use the Linux client without a GUI (or X, or anything else) and right now authorisation is hard-coded with an
#ifdef(__linux__)
to pop up a browser.Could there be an option (build or run time) not to use WebKitGTK at all?
The text was updated successfully, but these errors were encountered: