-
Notifications
You must be signed in to change notification settings - Fork 155
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
Package built from source to a PC with no internet connection #1982
Comments
When installing packages from local files, you normally need to provide the full normalized path to that file -- otherwise The following seems to work on my Windows machine:
Does that help in your scenario? |
Sorry, when anonymizing the path, I didn't make it clear that I was using a full normalized path "C:\blah\blah..."
This is an option, but as I mentioned above, the library is 130MB when using that tar compared to the 7MB the library is when built from source. So I was hoping to find a way to get the 7MB library easily portable across machines. I also just tried archiving the folder to a tar.gz (via 7zip) and received a different error:
|
Goal: get a specific version of XGBoost onto a computer with no internet, and installable via
renv
. This is a bit of an edge case so I understand if there's no current solution. I have built XGBoost v.2.0.3.1 from source following their directions . Thus, I have a library folder with xgboost installed there. It was built rather than installed manually because building from source results in a package around 7MB instead of the ~130MB version that results fromrenv::install("https://s3-us-west-2.amazonaws.com/xgboost-nightly-builds/release_2.0.0/xgboost_r_gpu_win64_82d846bbeb83c652a0b1dff0e3519e67569c4a3d.tar.gz")
(link comes from here).What can I do so that I could copy this XGBoost version to the other PC that has no internet, and be able to run
renv::restore
orinstall
for new projects there?I have attempted zipping the xgboost folder into .zip archive, copying that to my cellar, and running
As always, thank you!
The text was updated successfully, but these errors were encountered: