Differences

This shows you the differences between two versions of the page.

--- proton_vsrename [2011/12/29 03:22] – seth
+++ proton_vsrename [2012/07/07 02:00] – seth
@@ Line 9: / Line 9: @@
 === Smart renaming with vsrename (Windows only) ===
-First, grab [http://www.codeproject.com/KB/cpp/vsrename.aspx|vsrename (Visual Studio Project Renamer)] - what it does is intelligently search and replace in file names and inside text file (it can figure out what is a text file or not) in an entire directory tree.  Don't let the Visual Studio in the name fool you, it doesn't really care what files it works on.
+First, grab [[http://www.codeproject.com/KB/cpp/vsrename.aspx|vsrename (Visual Studio Project Renamer)]] - what it does is intelligently search and replace in file names and inside text file (it can figure out what is a text file or not) in an entire directory tree.  Don't let the Visual Studio in the name fool you, it doesn't really care what files it works on.
 Grab vsrename.exe and throw it somewhere in your path to get ready.
@@ Line 23: / Line 23: @@
 Now, at this point you can open windows/lasercats.sln and build the game for windows and it should work.  (Don't forget to rebuild your resources with media/build_media.bat )
-=== Android considerations ===
+=== Android notes ===
-But - one fault of vsrename is it doesn't change directories, and android does have a directory named the app name.. so you'll have to **rename android/src/com/rtsoft/barebones** to **android/src/com/mycompany/lasercats**.
+If you're doing Android, you'll probably want to look over the following files by hand to tweak things:
-There are probably other things you'll end up having to hand tweak as you build for each platform, feel free to add them here.
+  * android/app_setup_info.bat
+  * android/AndroidManifest.xml
+  * android/build.xml
+  * android/res/values/strings.xml (to change the display name of the app, unless it was hardcoded in the manifest)
+  * android/res/drawable/icon.png (change the app icon)
 === Summary ===
-And there go, more or less ready to go.  Keep in mind you can't move this project directory anywhere, you need to keep it in the same directory as proton's shared directory, as most of the scripts and tools use relative paths to minimize setup.
+And there you go, more or less ready.  Keep in mind you can't move this project directory anywhere, you need to keep it in the same directory as proton's shared directory, as most of the scripts and tools use relative paths to minimize setup.
 It IS possible to do directory checkout of your own svn located inside of your svn proton checkout btw - it's what I do for client projects, works like charm.