[swift-dev] Android: Build error: No such module "SwiftGlibc"

[Brian Gesiak]

Swift Android builds successfully for me. Following all the preliminary
steps from https://github.com/apple/swift/blob/master/docs/Android.md, such
as building libicu, I can successfully build with the following command on
the master branch of apple/swift this morning:

utils/build-script -R \
    --android \
    --android-ndk ~/android-ndk-r12b \
    --android-api-level 21 \
    --android-icu-uc ~/GitHub/apple/libiconv-libicu-android/armeabi-v7a \
    --android-icu-uc-include
~/GitHub/apple/libiconv-libicu-android/armeabi-v7a/icu/source/common \
    --android-icu-i18n ~/GitHub/apple/libiconv-libicu-android/armeabi-v7a \
    --android-icu-i18n-include
~/GitHub/apple/libiconv-libicu-android/armeabi-v7a/icu/source/i18n \
    -- --reconfigure

I haven't tried building --lldb and --foundation, so I'm not sure about
those. I also haven't tried checking out the swift-3.0-release branch.
(It'd be handy if utils/update-checkout could checkout a particular tag
across all repositories!)

I'd recommend using `--reconfigure` to ensure CMake isn't carrying over
values from previous builds. Also, keep in mind that only an Ubnutu 15.10
host is currently supported, as per the documentation. If you're still
having trouble despite all that, let me know as much about your build
environment as you can, and I'll try to help!

- Brian Gesiak


On Sun, Sep 18, 2016 at 10:52 PM, william via swift-dev <swift-dev at swift.org
> wrote:

> I've finally succeeded in re-creating the process for building (not on the
> Android port, mind).
>
> The trick this time was to build without the install options:
>
> ./swift/utils/build-script -R
>
> This should SUCCEED
>
> Then, delete the swift build directory:
>
> rm -rf build/Ninja-ReleaseAssert/swift-linux-armv7
>
> Then, build swift again *with* the install options:
>
> ./swift/utils/build-script -R -- --install-swift --install-prefix=/usr
> '--swift-install-components=autolink-driver;compiler;
> clang-builtin-headers;stdlib;swift-remote-mirror;sdk-overlay;dev'
> --build-swift-static-stdlib --build-swift-static-sdk-overlay
> --skip-test-lldb --install-destdir=swift-install
> --installable-package=swift.tar.gz
>
> If that succeeds, go ahead and build the whole project:
>
> ./swift/utils/build-script -R --llbuild --lldb --foundation --xctest
> --swiftpm --libdispatch -- --install-libdispatch --install-swift
> --install-lldb --install-llbuild --install-foundation --install-swiftpm
> --install-xctest --install-prefix=/usr '--swift-install-components=
> autolink-driver;compiler;clang-builtin-headers;stdlib;
> swift-remote-mirror;sdk-overlay;dev' --build-swift-static-stdlib
> --build-swift-static-sdk-overlay --skip-test-lldb --install-destdir=swift-install
> --installable-package=swift.tar.gz
>
> I hope that helps.
>
> - Will
>
> > On Sep 14, 2016, at 3:51 PM, Eric Wing <ewmailing at gmail.com> wrote:
> >
> > On 9/14/16, william <william at housedillon.com> wrote:
> >> I'm so glad someone else is hitting this problem!
> >>
> >> I've been seeing this relatively often.  I have a set of superstitions
> that
> >> allow me to get past it, and once I do, I try very hard not to delete
> >> anything in my build directory.
> >>
> >> - Will
> >>
> >
> > Can you suggest some mirrors to break or rabbit feet to rub, because I
> > have no idea where to start for this.
> >
> > Thanks,
> > Eric
>
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20160919/c6023a7e/attachment.html>