Skip to content

[android] Fix some parts of Bundle in Android. #2120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2019

Conversation

drodriguez
Copy link
Contributor

@drodriguez drodriguez commented Apr 15, 2019

While Android does not follow FHS, and it doesn't seem to have something
similar published, it follows some conventions of Unix. One of them
is that libraries are normally named prefixed with "lib" and suffixed
with ".so" like Linux. Executables are also normally named without any
prefix nor suffix.

The changes in this commit lift up restrictions that were in place for
Android, and allow some of the Bundle tests to pass on Android (and lift
another restriction in TestObjCRuntime).

While bundles might never be a common construct in Android, these
changes at least allow to test some of the scenarios, in case someone
needs this behaviour.

This allows TestBundle, TestNSError, TestPropertyListSerialization, TestObjCRuntime, and TestNSKeyedUnarchiver to pass on Android devices.

@compnerd
Copy link
Member

The library/executable naming is not part of the FHS, its part of the Unix heritage.

@compnerd
Copy link
Member

@swift-ci please test

While Android does not follow FHS, and it doesn't seem to have something
similar published, it follows some conventions of Unix. One of them
is that libraries are normally named prefixed with "lib" and suffixed
with ".so" like Linux. Executables are also normally named without any
prefix nor suffix.

The changes in this commit lift up restrictions that were in place for
Android, and allow some of the Bundle tests to pass on Android (and lift
another restriction in TestObjCRuntime).

While bundles might never be a common construct in Android, these
changes at least allow to test some of the scenarios, in case someone
needs this behaviour.
@drodriguez drodriguez force-pushed the android-bundle-executable branch from 3642004 to fdddfbe Compare April 16, 2019 01:09
@drodriguez
Copy link
Contributor Author

Incorporated the feedback from Lily and reworded the commit/PR message to not imply that libraries or executable naming are related to FHS (from the comments in the code I thought they were).

@spevans
Copy link
Contributor

spevans commented Apr 16, 2019

@swift-ci test

@compnerd
Copy link
Member

@swift-ci please test macOS platform

@millenomi millenomi merged commit bd23c5a into swiftlang:master Apr 16, 2019
@drodriguez drodriguez deleted the android-bundle-executable branch July 16, 2019 22:42
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.

4 participants