Improve offline build experience for developers#3162
Merged
9prady9 merged 2 commits intoarrayfire:masterfrom Sep 24, 2021
Merged
Improve offline build experience for developers#31629prady9 merged 2 commits intoarrayfire:masterfrom
9prady9 merged 2 commits intoarrayfire:masterfrom
Conversation
9prady9
force-pushed
the
improv_offline_build
branch
from
022c987 to
10bb3a5
Compare
Member
Author
|
Lets wait for microsoft/vcpkg#19166 to be merged so that arrayfire master doesn't break for developers who use vcpkg manifest file. |
The following common scenarios(majority we think) are covered with this change. - Developer has cloud connection always. - Developer has cloud connection for initial cmake run, but not later. - Developer has lost cloud connection for a while after the initial successful cmake run but regained the connection later. - Developer is doing an completely disconnected build using the source tarball we generate and attach to our release assets. When the developer wants to do an offline build for a specific commit other than release tags, they would have to generate the relevant source tarball themselves. The commands required to do the same can be found from the following ci workflow file in our repository. .github/workflows/release_src_artifact.yml The source tarball generation CI job has also been changed to reflect the change in external dependencies location.
9prady9
force-pushed
the
improv_offline_build
branch
from
10bb3a5 to
3ff1018
Compare
9prady9
force-pushed
the
improv_offline_build
branch
from
3ff1018 to
e80abde
Compare
umar456
approved these changes
Sep 24, 2021
9prady9
added a commit
to 9prady9/arrayfire
that referenced
this pull request
Sep 24, 2021
* Improve offline build experience for developers The following common scenarios(majority we think) are covered with this change. - Developer has cloud connection always. - Developer has cloud connection for initial cmake run, but not later. - Developer has lost cloud connection for a while after the initial successful cmake run but regained the connection later. - Developer is doing an completely disconnected build using the source tarball we generate and attach to our release assets. When the developer wants to do an offline build for a specific commit other than release tags, they would have to generate the relevant source tarball themselves. The commands required to do the same can be found from the following ci workflow file in our repository. .github/workflows/release_src_artifact.yml The source tarball generation CI job has also been changed to reflect the change in external dependencies location. * Update vcpkg commit in windows github action to required (cherry picked from commit 7995750)
syurkevi
pushed a commit
that referenced
this pull request
Dec 28, 2021
* Improve offline build experience for developers The following common scenarios(majority we think) are covered with this change. - Developer has cloud connection always. - Developer has cloud connection for initial cmake run, but not later. - Developer has lost cloud connection for a while after the initial successful cmake run but regained the connection later. - Developer is doing an completely disconnected build using the source tarball we generate and attach to our release assets. When the developer wants to do an offline build for a specific commit other than release tags, they would have to generate the relevant source tarball themselves. The commands required to do the same can be found from the following ci workflow file in our repository. .github/workflows/release_src_artifact.yml The source tarball generation CI job has also been changed to reflect the change in external dependencies location. * Update vcpkg commit in windows github action to required (cherry picked from commit 7995750)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The following common scenarios(majority we think) are covered with this change.
When the developer wants to do an offline build for a specific commit other than release tags, they would have to generate the relevant source tarball themselves. The commands required to do the same can be found from the following ci workflow file in our repository.
The source tarball generation CI job has also been changed to reflect the change in external dependencies location.
Changes to Users
None to users, but Offline development made more easy for developers.
Checklist
[ ] Functions added to unified API[ ] Functions documented