So far this seems to be working: build-swift-script.sh RELEASE=swift-2.2.1-RELEASE
mkdir apple-swift cd apple-swift git clone https://github.com/apple/swift.git cd swift utils/update-checkout --clone for D in *; do if [ -d "${D}" ]; then echo "checkout $RELEASE of ${D}" (cd ${D} && git checkout tags/$RELEASE) fi done cd ../swift utils/build-script -R ------ will see if it completes a build -tim On 5/6/16, Tim Prepscius <timprepsc...@gmail.com> wrote: > Ok download says it does not work > > silver:swift tprepscius$ utils/update-checkout --clone > --- Cloning 'swift' --- > fatal: destination path 'swift' already exists and is not an empty > directory. > utils/update-checkout: command terminated with a non-zero exit status > 128, aborting > silver:swift tprepscius$ utils/update-checkout > --- Updating '/Users/tprepscius/Documents/Projects/llvm' --- > Current branch stable is up to date. > --- Updating '/Users/tprepscius/Documents/Projects/clang' --- > Current branch stable is up to date. > --- Updating '/Users/tprepscius/Documents/Projects/cmark' --- > Current branch master is up to date. > --- Updating '/Users/tprepscius/Documents/Projects/lldb' --- > Current branch master is up to date. > --- Updating '/Users/tprepscius/Documents/Projects/swift-integration-tests' > --- > Current branch master is up to date. > --- Updating '/Users/tprepscius/Documents/Projects/swift' --- > fatal: Not a git repository (or any of the parent directories): .git > utils/update-checkout: command terminated with a non-zero exit status > 128, aborting > > however I think, that it might build anyways. will check. > > > I wonder if there is a command that I should be using instead of > utils/update-checkout > > > Btw, I'm not writing this to be annoying. I'm writing it so someone > googling in the future can find the path I take to get things > building. > (I googled a *lot* trying to find Swift without Xcode on OS X) > > -tim > > On 5/6/16, Tim Prepscius <timprepsc...@gmail.com> wrote: >> Hmm actually that doesn't work at all: >> >> --- Updating '/Users/tprepscius/Documents/Projects/swift' --- >> First, rewinding head to replay your work on top of it... >> Applying: [Build system] Add presets for Swift inside the LLDB tree. >> Using index info to reconstruct a base tree... >> M utils/build-presets.ini >> Falling back to patching base and 3-way merge... >> Auto-merging utils/build-presets.ini >> CONFLICT (content): Merge conflict in utils/build-presets.ini >> Failed to merge in the changes. >> Patch failed at 0001 [Build system] Add presets for Swift inside the LLDB >> tree. >> >> >> I will try using the download instead of the clone of swift >> >> On 5/6/16, Tim Prepscius <timprepsc...@gmail.com> wrote: >>> Cool. >>> >>> Working on this now. >>> >>> Out of curiosity: >>> Let's say I clone and checkout the 2.2.1 release tag >>> and then run the update-checkout util >>> >>> git clone https://github.com/apple/swift.git >>> cd swift >>> git checkout tags/swift-2.2.1-RELEASE >>> ./utils/update-checkout --clone >>> >>> >>> Will this update-checkout command clone the llvm & clang & etc >>> and then move to the correct tag for 2.2.1? (if there even is one) >>> or will it use HEAD all of the time? >>> >>> -tim >>> >>> On 5/6/16, Joe Groff <jgr...@apple.com> wrote: >>>> >>>>> On May 6, 2016, at 1:14 PM, Tim Prepscius via swift-users >>>>> <swift-users@swift.org> wrote: >>>>> >>>>> Greetings, >>>>> >>>>> Is it possible to build swift using Xcode, and then distribute swift >>>>> without Xcode? >>>>> Or, does there already is exist some link to swift on OS X which is >>>>> not contained in Xcode? >>>>> >>>>> I need a swift compiler/executable that will run on all versions of >>>>> MacOSX, not just the latest. >>>> >>>> A Swift app built with Xcode is self-contained and can be distributed >>>> independent of Xcode. You can target back to OS X 10.9. >>>> >>>> -Joe >>> >> > _______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
