Skip to content

Conversation

@ffried
Copy link

@ffried ffried commented Apr 14, 2017

I've refactored the scripts a little bit. 😃
The following changes were made:

  • All scripts now ensure that they are working in the correct directory by doing a pushd before all work and a popd at the end.
  • Merged get.sh into update.sh: If the swift directory does not yet exist, update.sh behaves like get.sh did previously. Otherwise it updates the existing sources just like update.sh did previously.
  • Added possibility to specify which origin and branch should be used for cloning and updating the sources.
  • The package.sh now uses a build bot which can be configured using the etc/arm_buildbots.ini file.
  • Added ninja to .gitignore and distclean.sh since it's now also cloned by update-checkout.
  • The README.md has been updated to match the new prerequisites as well as describing the refactored scripts.
  • Also, I've merged the swift-3.0 into master. It's probably a good idea to create a swift-3.1 branch now from master.

All changes have been tested. I successfully built a Swift 3.1 package today.

Note:
Since there's currently no swift-3.1-branch in the swift-arm fork of Swift, the update.sh script will fail when $SWIFT_SOURCE is not set to e.g. apple.

iachievedit and others added 30 commits August 1, 2016 20:33
Updates for building for ARM
- Use custom buildbot for ARM builds
- Abort when swift build-script failed
- Make whitespaces in paths less of a problem
- Move fixing package into function
- Ensure correct directory by wrapping into pushd/popd
- Ensure correct directory by wrapping into pushd/popd
- Only call update-checkout if git clone succeeded
- Consistent logging in all scripts
- Add possibility to specify swift version branch by setting $SWIFT_VERSION before calling update.sh
- Update default swift version to Swift 3.1
- Merge get.sh into update.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants