darkmoon_uk
02/15/2021, 5:29 AMserialization-core
and not serialization-json
as the documentation advises 🙃 .
😞 1.4.30
during either:
• linkDebugFrameworkIosArm64
or
• linkDebugFrameworkIosX64
(compile
alone, for either platform, succeeds):
Compilation failed: Unbound symbols not allowed
More in thread 👉darkmoon_uk
02/15/2021, 5:30 AMdarkmoon_uk
02/15/2021, 5:43 AM--debug
but none of the output seems to indicate an area of my code that's causing the problem (if it even is my code).Yernar Mendigarin
02/15/2021, 7:12 AMdarkmoon_uk
02/15/2021, 7:57 AMkotlin.mpp.enableGranularSourceSetsMetadata=true
yes. It hasn't been a problem until now. I could devolve the configuration into manually configured platform-dependency tree to remove the need for this... but I am not seeing the connection.Yernar Mendigarin
02/15/2021, 7:58 AMIvan Kubyshkin [JetBrains]
02/15/2021, 8:36 AMArtyom Degtyarev [JB]
02/15/2021, 8:49 AM--info
gradle flag to reveal the compiler arguments.darkmoon_uk
02/15/2021, 10:13 AMserialization-core
and not serialization-json
as advised.
However it's interesting that this was working prior to 1.4.30
. Also that the Android target still compiled, only the Native compile broke; though I guess they have totally different dependency linking mechanisms.Daniele B
02/16/2021, 11:33 AMimplementation("org.jetbrains.kotlinx:kotlinx-serialization-core:1.0.1")
so, is that wrong?darkmoon_uk
02/16/2021, 10:10 PMcore
doesn't include any serialization method, and this manifest in my first 1.4.30
builds throwing an error about unlinked symbols in the K/N build.darkmoon_uk
02/16/2021, 10:11 PM-json
artifact alone, to cover the common use case, and this indeed fixed my build.Daniele B
02/16/2021, 11:25 PMdarkmoon_uk
02/16/2021, 11:32 PM