Packages
mob_new
0.4.7
0.4.20
0.4.19
0.4.18
0.4.17
0.4.16
0.4.15
0.4.14
0.4.13
0.4.12
0.4.11
0.4.10
0.4.9
0.4.8
0.4.7
0.4.6
0.4.5
0.4.4
0.4.3
0.4.2
0.4.1
0.4.0
0.3.16
0.3.15
0.3.14
0.3.13
0.3.12
0.3.11
0.3.10
0.3.9
0.3.8
0.3.7
0.3.6
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.0
0.1.45
0.1.44
0.1.43
0.1.42
0.1.40
0.1.33
0.1.30
0.1.29
0.1.28
0.1.27
0.1.26
0.1.25
0.1.24
0.1.23
0.1.21
0.1.20
0.1.19
0.1.18
0.1.17
0.1.16
0.1.15
0.1.14
0.1.12
0.1.11
0.1.10
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
Project generator for the Mob mobile framework
Current section
Files
Jump to
Current section
Files
lib/mob_new/ndk_version.ex
defmodule MobNew.NdkVersion do
@moduledoc """
Mirror of `MobDev.NdkVersion`'s `@recommended` constant.
`mob_new` ships as a Mix archive and cannot depend on `mob_dev` at
project-generation time, so the recommended NDK version has to be
duplicated here to feed into the generated `android/app/build.gradle`
template.
A drift test (`test/mob_new/ndk_version_test.exs`) asserts this stays
in lockstep with `MobDev.NdkVersion.recommended/0` by reading the
source file at `../mob_dev/lib/mob_dev/ndk_version.ex`. When you bump
the NDK there, bump it here too — CI will catch it if you forget.
See `~/code/mob_dev/lib/mob_dev/ndk_version.ex` for the rationale
(libc++ inline-namespace ABI mismatch between NDK 25 and 27).
"""
@recommended "27.2.12479018"
@doc "The NDK version Mob's bundled OTP tarballs were cross-compiled with."
@spec recommended() :: String.t()
def recommended, do: @recommended
end