Initial Commit

AndroidManifest.xml

@@ -0,0 +1,34 @@
+<?xml version="1.0"?>
+<!-- Replace org.libsdl.app with the identifier of your game below, e.g.
+     com.gamemaker.game
+-->
+<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="org.ancurio.mkxp" android:versionCode="1" android:versionName="1.0" android:installLocation="auto">
+
+    <!-- Create a Java class extending SDLActivity and place it in a
+         directory under src matching the package, e.g.
+         	src/com/gamemaker/game/MyGame.java
+
+         then replace "SDLActivity" with the name of your class (e.g. "MyGame")
+         in the XML below.
+
+         An example Java class can be found in README-android.txt
+    -->
+    <application android:label="@string/app_name" android:icon="@drawable/ic_launcher" android:allowBackup="true" android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:hardwareAccelerated="true">
+        <activity android:name="MKXPActivity" android:label="@string/app_name" android:configChanges="keyboardHidden|orientation" android:screenOrientation="sensorLandscape">
+            <intent-filter>
+                <action android:name="android.intent.action.MAIN"/>
+                <category android:name="android.intent.category.LAUNCHER"/>
+            </intent-filter>
+        <meta-data android:name="android.app.lib_name" android:value=""/>
+        </activity>
+    </application>
+
+    <!-- Android 2.3.3 -->
+    <uses-sdk android:minSdkVersion="10" android:targetSdkVersion="12"/>
+
+    <!-- OpenGL ES 2.0 -->
+    <uses-feature android:glEsVersion="0x00020000"/>
+
+    <!-- Allow writing to external storage -->
+    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
+</manifest>

README

@@ -0,0 +1 @@
+This is port is currently unstable and should only be used for development purposes

assets/Game.ini

@@ -0,0 +1,7 @@
+[Game]
+Library=RGSS102E.dll
+Scripts=Data\Scripts.rxdata
+Title=TemplXP
+RTP1=Standard
+RTP2=
+RTP3=

assets/mkxp.conf

@@ -0,0 +1,9 @@
+overlayPath=overlay_desc.json
+subImageFix=true
+smoothScaling=true
+syncToRefreshRate=true
+
+RTP=TemplXP.zip
+RTP=RGSS1-RTP.zip
+
+# Temporary workaround so saves work

assets/overlay_desc.json

@@ -0,0 +1,83 @@
+{
+	"image": "touch_overlay.png",
+	"buttons": [
+	{
+		"id": "DPad up",
+		"target": "Up",
+		"shape": "triangle",
+		"x": 92,
+		"y": 366,
+		"x1": -14,
+		"y1": 260,
+		"x2": 200,
+		"y2": 260
+	},
+	{
+		"id": "DPad down",
+		"target": "Down",
+		"shape": "triangle",
+		"x": 92,
+		"y": 366,
+		"x1": -14,
+		"y1": 472,
+		"x2": 200,
+		"y2": 472
+	},
+	{
+		"id": "DPad left",
+		"target": "Left",
+		"shape": "triangle",
+		"x": 92,
+		"y": 366,
+		"x1": -14,
+		"y1": 260,
+		"x2": -14,
+		"y2": 472
+	},
+	{
+		"id": "DPad left extension",
+		"target": "Left",
+		"shape": "rectangle",
+		"x": -60,
+		"y": 290,
+		"width": 46,
+		"height": 182
+	},
+	{
+		"id": "DPad right",
+		"target": "Right",
+		"shape": "triangle",
+		"x": 92,
+		"y": 366,
+		"x1": 200,
+		"y1": 260,
+		"x2": 200,
+		"y2": 472
+	},
+	{
+		"id": "DPad right extension",
+		"target": "Right",
+		"shape": "rectangle",
+		"x": 200,
+		"y": 290,
+		"width": 46,
+		"height": 182
+	},
+	{
+		"id": "A button",
+		"target": "C",
+		"shape": "circle",
+		"x": 570,
+		"y": 310,
+		"radius": 60
+	},
+	{
+		"id": "B button",
+		"target": "B",
+		"shape": "circle",
+		"x": 470,
+		"y": 400,
+		"radius": 60
+	}
+	]
+}

build.xml

@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- This should be changed to the name of your project -->
+<project name="mkxp" default="help">
+
+    <!-- The local.properties file is created and updated by the 'android' tool.
+         It contains the path to the SDK. It should *NOT* be checked into
+         Version Control Systems. -->
+    <property file="local.properties" />
+
+    <!-- The ant.properties file can be created by you. It is only edited by the
+         'android' tool to add properties to it.
+         This is the place to change some Ant specific build properties.
+         Here are some properties you may want to change/update:
+
+         source.dir
+             The name of the source directory. Default is 'src'.
+         out.dir
+             The name of the output directory. Default is 'bin'.
+
+         For other overridable properties, look at the beginning of the rules
+         files in the SDK, at tools/ant/build.xml
+
+         Properties related to the SDK location or the project target should
+         be updated using the 'android' tool with the 'update' action.
+
+         This file is an integral part of the build system for your
+         application and should be checked into Version Control Systems.
+
+         -->
+    <property file="ant.properties" />
+
+    <!-- if sdk.dir was not set from one of the property file, then
+         get it from the ANDROID_HOME env var.
+         This must be done before we load project.properties since
+         the proguard config can use sdk.dir -->
+    <property environment="env" />
+    <condition property="sdk.dir" value="${env.ANDROID_HOME}">
+        <isset property="env.ANDROID_HOME" />
+    </condition>
+
+    <!-- The project.properties file is created and updated by the 'android'
+         tool, as well as ADT.
+
+         This contains project specific properties such as project target, and library
+         dependencies. Lower level build properties are stored in ant.properties
+         (or in .classpath for Eclipse projects).
+
+         This file is an integral part of the build system for your
+         application and should be checked into Version Control Systems. -->
+    <loadproperties srcFile="project.properties" />
+
+    <!-- quick check on sdk.dir -->
+    <fail
+            message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable."
+            unless="sdk.dir"
+    />
+
+    <!--
+        Import per project custom build rules if present at the root of the project.
+        This is the place to put custom intermediary targets such as:
+            -pre-build
+            -pre-compile
+            -post-compile (This is typically used for code obfuscation.
+                           Compiled code location: ${out.classes.absolute.dir}
+                           If this is not done in place, override ${out.dex.input.absolute.dir})
+            -post-package
+            -post-build
+            -pre-clean
+    -->
+    <import file="custom_rules.xml" optional="true" />
+
+    <!-- Import the actual build file.
+
+         To customize existing targets, there are two options:
+         - Customize only one target:
+             - copy/paste the target into this file, *before* the
+               <import> task.
+             - customize it to your needs.
+         - Customize the whole content of build.xml
+             - copy/paste the content of the rules files (minus the top node)
+               into this file, replacing the <import> task.
+             - customize to your needs.
+
+         ***********************
+         ****** IMPORTANT ******
+         ***********************
+         In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
+         in order to avoid having your file be overridden by tools such as "android update project"
+    -->
+    <!-- version-tag: 1 -->
+    <import file="${sdk.dir}/tools/ant/build.xml" />
+
+</project>

jni/Android.mk

@@ -0,0 +1 @@
+include $(call all-subdir-makefiles)

jni/Application.mk

@@ -0,0 +1,6 @@
+APP_ABI := armeabi-v7a armeabi mips x86
+APP_PLATFORM := android-9
+APP_OPTIM := release
+NDK_TOOLCHAIN_VERSION := 4.8
+APP_STL := gnustl_static
+APP_CPPFLAGS := -std=c++11 -frtti -fexceptions