Sysprogs forums › Forums › VisualGDB › VisualGDB-Android-VS2008 Errors unless rebuild all
- This topic has 4 replies, 3 voices, and was last updated 10 years, 11 months ago by Anonymous.
-
AuthorPosts
-
November 30, 2013 at 10:28 #692brettjones1900Participant
When I make a change to the code and build I get
1> [aapt] Generating resource IDs…
1> [aapt] invalid resource directory name: F:ArchivedProjectsDestroyTheWorldCodeprojectbinres/crunch
1>BUILD FAILED
1>F:AndroidSDKSsdktoolsantbuild.xml:653: The following error occurred while executing this line:
1>F:AndroidSDKSsdktoolsantbuild.xml:698: null returned: 1
1>Total time: 1 second
1>1>Command exited with code 1
1>Executable: F:AndroidSDKSapache-ant-1.9.2binant.bat
1>Arguments: debug
1>Directory: F:ArchivedProjectsDestroyTheWorldCodeproject
1>Environment: JAVA_HOME=C:Program Files (x86)Javajdk1.7.0_40|ANT_HOME=F:AndroidSDKSapache-ant-1.9.2|ANDROID_SDK_ROOT=F:AndroidSDKSsdk
1>Project : error PRJ0019: A tool returned an error code from “Performing Makefile project actions”
1>Build log was saved at “file://f:ArchivedProjectsDestroyTheWorldCodebuildVisualGdb2008DebugBuildLog.htm”
1>DestroyTheWorld – 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========The contents of build.xml at 653
elseText=”hasCode = false. Skipping aidl/renderscript/R.java”>
Handling aidl files…
framework=”${project.target.framework.aidl}”
libraryBinAidlFolderPathRefid=”project.library.bin.aidl.folder.path”
genFolder=”${gen.absolute.dir}”
aidlOutFolder=”${out.aidl.absolute.dir}”>
The contents of build.xml at 698
proguardFile=”${out.absolute.dir}/proguard.txt”>
If I do a rebuild all then the build succeeds but the project is rather large and takes about 10 minutes to build.
After the build when I launch from eclipse I get
R.java was modified manually! Reverting to generated version!
So I launch again and this time it is successful and everything works as expected and I can debug etc.Any help with this issue would be greatly appreciated.
Thanks in advancedNovember 30, 2013 at 20:09 #2823ketParticipantHi,
It looks like this issue: https://code.google.com/p/android/issues/detail?id=60496
Some of the discussions on the issue are also here: https://plus.google.com/+AndroidDevelopers/posts/hNZNjqKLpny
Try the workarounds discussed there.December 1, 2013 at 13:04 #2824AnonymousParticipantFrom the discussion it sounded like it was from target platform miss match and mine was miss matched because i was trying to target platform 10 which visualGDB does not have a equivalent platform and google does not offer platform-9
I instead targeted platform 14 but got the same results.. here are the steps I tookin eclipse I right clicked project and select properties
selected android and check the box next to Android 4.0clicked the button ok
opened AndroidManifest.xml and set
cleaned the project
open the file project.properties and verify it has the lines
# Project target.
target=android-14In visual studio clicked Project->Visual GDB Project Settings
Selected Build Settings
In Drop Down under Target selected android-14rebuild all
worked first time but fails next time unless do rebuild all.. did I miss something?.
Anyway Unchecking Build Automatically in eclipse fixes the build fail and less of a hassle than a rebuild all
so I guess this issue is resolvedDecember 2, 2013 at 04:57 #2825ketParticipantHi,
If it works the first time but not after, then check whether any of your manual file changes were automatically overwritten by ANT or VisualGDB.
December 4, 2013 at 12:28 #2826AnonymousParticipantI checked.. it doesn’t get overwritten but the build sequence is now not time consuming so works ok.
In eclipse clean project. In Visual Studio build. In eclipse build all then launch.
Overall I am happy with my purchase of VisualGDB. Makes debugging android apps fast and easy. -
AuthorPosts
- You must be logged in to reply to this topic.