Wait... are you sure that's the appropriate configuration? Shouldn't
the xctoolchain destination be in /Library/Developer/Toolchains/ rather
than the xcode directory proper? Or is the actual end destination handled
entirely by `toolchain-installer'?
I’m sorry for the experience Travis, but this is certainly one of our
pain points. There’s a lot at play and we haven’t finished setting up our
public CI either. Here’s what I do locally to build a toolchain on OS X:
*function* build_osx_package() {
YEAR=$(*date* +"%Y")
MONTH=$(*date* +"%m")
DAY=$(*date* +"%d")
TOOLCHAIN_VERSION="swift-2.2-SNAPSHOT-${YEAR}-${MONTH}-${DAY}-a"
ARCHIVE_DIR="${TOOLCHAIN_VERSION}-${BUILD_NUMBER}"
ARCHIVE="${TOOLCHAIN_VERSION}-osx.tar.gz"
SYM_ARCHIVE="${TOOLCHAIN_VERSION}-osx-symbols.tar.gz"
BUNDLE_IDENTIFIER="org.swift.${YEAR}${MONTH}${DAY}"
DISPLAY_NAME="Swift 2.2 Development Snapshot"
TOOLCHAIN_NAME="${TOOLCHAIN_VERSION}"
SWIFT_SOURCE_ROOT="${SRC_DIR}"
SWIFT_BUILD_ROOT="${SRC_DIR}/build"
SWIFT_INSTALLABLE_PACKAGE="${SRC_DIR}/${ARCHIVE}"
SWIFT_INSTALL_DIR="${SRC_DIR}/swift-nightly-install"
SWIFT_INSTALL_SYMROOT="${SRC_DIR}/swift-nightly-symroot"
SWIFT_TOOLCHAIN_DIR=
"/Applications/Xcode.app/Contents/Developer/Toolchains/${TOOLCHAIN_NAME}.xctoolchain"
SYMBOLS_PACKAGE="${SRC_DIR}/${SYM_ARCHIVE}"
./swift/utils/build-script --preset="buildbot_osx_package"
install_destdir="${SWIFT_INSTALL_DIR}" installable_package=
"${SWIFT_INSTALLABLE_PACKAGE}" install_toolchain_dir="${SWIF\
T_TOOLCHAIN_DIR}" install_symroot="${SWIFT_INSTALL_SYMROOT}"
symbols_package="${SYMBOLS_PACKAGE}" darwin_toolchain_bundle_identifier=
"${BUNDLE_IDENTIFIER}" darwin_toolchain_display_n\
ame="${DISPLAY_NAME}" darwin_toolchain_xctoolchain_name=
"${TOOLCHAIN_NAME}" darwin_toolchain_version="${TOOLCHAIN_VERSION}"
}
It should work. If not, please file a bug with your output and
configuration and let us know about it.
- mish
On Dec 14, 2015, at 8:32 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:
+Mishal Awadah, Mishal Shah
On Mon, Dec 14, 2015 at 8:04 PM, Travis Tilley via swift-dev < >> swift-dev@swift.org> wrote:
Is there any documentation somewhere on what the exact commands are that
the buildbot CI performs and how the packages on swift.org are created?
I've noticed that:
1) LLDB doesn't compile on either OSX or ubuntu 15 via the normal script
for various reasons (codesign on OSX, no idea on ubuntu) in the default
configuration. This seems highly counter-intuitive.
2) The buildbot presets don't have sane defaults and I can't find any
documentation on what "sane" might mean for those builds.
3) I still can't build the full suite using the following command
(which, again, may or may not be sane):
nice ./swift/utils/build-script \
--preset=buildbot_osx_package \
installable_package=/tmp/swift.tar.gz \
install_destdir=/Library/Developer/Toolchains/swift-2.2-SNAPSHOT-2015-12-14/
\
install_toolchain_dir=/Library/Developer/Toolchains/swift-2.2-SNAPSHOT-2015-12-14.xctoolchain
\
install_symroot=/Library/Developer/Toolchains/swift-2.2-SNAPSHOT-2015-12-14/
\
symbols_package=/tmp/swift-symbols.tar.gz \
darwin_toolchain_bundle_identifier=org.swift.20151214 \
darwin_toolchain_display_name=20151214 \
darwin_toolchain_xctoolchain_name=swift
darwin_toolchain_version=swift
All that I actually -want- to do is start xcode using a freshly built
swift toolchain. That is it. I don't even need any of the SDKs other than
OSX built. But the build directory install structure doesn't have anything
like what `launch-with-toolchain` appears to expect...
Not sure where i'm going wrong. Please feel free to tell me to RTFM if
there is a FM to read.
-Travis Tilley
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr@gmail.com>*/
