nativeCompile and nativeLink have to share some state. The state can be described by path locations though, without the need of a configuration file or additional arguments.
The objectfiles generated by nativeCompile are needed by nativeLink, but the locations are in non-repeatable directories, e.g.
./target/client/arm64-ios/gvm/tmp/SVM-1575056164225/hellofx.hellofx.o
./target/client/arm64-ios/gvm/tmp/SVM-1575056164225/llvm.o
Therefore, it would be better if nativeCompile at the end of the compile step copies the objectfiles to e.g. ./target/client/arm64-ios/gvm/obj or similar, where nativeLink can find them
nativeCompile and nativeLink have to share some state. The state can be described by path locations though, without the need of a configuration file or additional arguments.
The objectfiles generated by nativeCompile are needed by nativeLink, but the locations are in non-repeatable directories, e.g. ./target/client/arm64-ios/gvm/tmp/SVM-1575056164225/hellofx.hellofx.o ./target/client/arm64-ios/gvm/tmp/SVM-1575056164225/llvm.o
Therefore, it would be better if nativeCompile at the end of the compile step copies the objectfiles to e.g. ./target/client/arm64-ios/gvm/obj or similar, where nativeLink can find them