keyboardr

#if (${PACKAGE_NAME} && ${PACKAGE_NAME} != "")package ${PACKAGE_NAME};#end

import android.app.Activity;
import android.app.Fragment;
import android.app.FragmentManager;

#parse("File Header.java")
public class ${NAME} extends Fragment {
    
  private static final String FRAG_TAG = ${NAME}.class.getCanonicalName();

wispborne

import android.content.Context
import android.content.SharedPreferences
import kotlin.reflect.KProperty

/**
 * Represents a single [SharedPreferences] file.
 *
 * Usage:
 *
 * ```kotlin

nisrulz

# I use ZSH, here is what I added to my .zshrc file (config file)
# at ~/.zshrc

# ------------------ Android ------------------ #

# Have the adb accessible, by including it in the PATH
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:path/to/android_sdk/platform-tools/"

# Setup your Android SDK path in ANDROID_HOME variable
export ANDROID_HOME=~/sdks/android_sdk

Ribesg

This gist demonstrates how to use a Kotlin MPP library which depends on an iOS Framework in a native iOS application (XCode project).

First, see [how the Kotlin MPP Library is built][lib-build].

Key ideas:

• We can currently only use a single Kotlin MPP library in an iOS project, so we need to create a MPP project local to our iOS XCode project whose sole purpose is to aggregate multiple MPP dependencies into a single Framework.
• To keep our working environment clean, we create the gradle project in a subdirectory instead of at the root of our iOS XCode project. I name my subdirectory mpp.
• We need to have the Frameworks used by our dependencies locally, as we only have bindings provided by the cinterop klibs, so we use [Carthage] again.
• As the only goal of our gradle project is to create a Framework, we only use ios* targets.
• Our project won't have any source code, but we NEED at least one source file, or Gradle will refuse to build anything, returning just a rude NO-SOURCE. Just create