Several iterations of updates below:<\/p>\n
<\/p>\n
Update 1:<\/span> This procedure works on the <\/strong>zxing-1.4.zip<\/em> source base.\u00a0 I’m trying to figure out why it doesn’t want to work easily with the most current SVN code (e.g., rev 1217 or 1220).\u00a0 I thought it was just some preloading weirdness that caused the Java Stack Overflow errors, then I thought it was Subversion related, but now… now I’m not sure what’s going on but I’ll let you know if I figure it out.<\/strong><\/p>\n Update 2:<\/span> Eclipse does NOT like the new version of <\/strong>\/android\/default.properties<\/em> at all.\u00a0 After you create the project folders but before you try creating the project in Eclipse, edit <\/strong>\/android\/default.properties<\/em> and change<\/strong><\/p>\n <\/p>\n to<\/strong><\/p>\n That seems to prevent the whole Stack Overflow problem.\u00a0 I’m not sure why this changed or what the more correct thing to do it but there’s some apparently relevant discussion here<\/a>. Curiously, despite my reversion of this change I do not see any problem in my test builds here, whether in Eclipse or when using the command-line build as outlined previously.<\/strong><\/p>\n Update 3:<\/span> If you comment out the <\/strong>target= line in that file entirely (using “#”) the problem also <\/em>goes away – be sure to select an SDK level >= 4 though.\u00a0 Eclipse still <\/em>forces you to select a Google APIs target, but if you double-click one of the “un-selectable” Android targets (click the text NOT the checkbox!) just right it’ll apparently take the setting and work OK.\u00a0 Who knows if that works in general – probably not. With an Android target launching the AVD also goes much more smoothly!<\/strong><\/p>\n <\/p>\n Question is, what is it that makes Eclipse insist this is an APIs project when default.properties is not giving it any hints? <\/strong>Or i<\/strong>s it a quirk of the SDK? <\/strong>What triggers this, and is it more readily resolved than by doing this?<\/strong><\/p>\n Update 4:<\/span> Last update for tonight. Once a project is in Eclipse you can go to Properties -> Android for that project and select a suitable Android target.\u00a0 As long as you don’t have dependencies on Google APIs it should be fine.\u00a0 If you <\/strong>\/android\/AndroidManifest.xml and remove the <\/strong>android:minSdkVersion setting that problem goes away as well (again, select Android 1.6 SDK level 4 to ensure proper operation).<\/strong><\/p>\n <\/p>\n Either it’s Eclipse 3.5.1 or the ADT plugin that’s messing up here.\u00a0 Regardless, it doesn’t seem to be any flaw in ZXing.\u00a0 It’s rather annoying to see Eclipse acting like this… are other people seeing this sort of bug?<\/strong><\/p>\n To summarize:<\/span> to avoid all these painful problems just plain remove <\/strong>default.properties and edit <\/strong>AndroidManifest.xml before you create a new Eclipse project based on the latest source.\u00a0 Ensure you select Android 1.6 SDK level 4 for best results.<\/strong><\/span><\/p>\n Also, when you run the app it’s best to just start the AVD first, wiping user data, (or at least uninstalling the old version of your app) and being at the home screen before you “Run As”.\u00a0 Otherwise, the app’s display ends up rather funky.<\/span><\/strong><\/p>\n Finally, “Build Automatically” may be more trouble than it’s worth, at least for a larger project such as this.\u00a0 Consider this if your head starts making dents in the wall as you struggle to make sense of Eclipse’s random “out of memory” errors. \ud83d\ude42 In my previous post<\/a> I referred to a Knol<\/a> that tells you how to build ZXing for Android (the Barcode Scanner) using the Eclipse<\/strong> IDE.\u00a0 There are pros and cons to doing this, given that ZXing is normally built from the command line using Ant (and during that build it is optimized using Proguard).<\/p>\n <\/p>\n However, my goal is to learn more about Android programming in general and to make it even more interesting, I’m doing it from Windows.\u00a0 Having the project working in an IDE is preferable for me when it comes to unraveling functional connections and learning how a (quite useful!) Android app is put together.<\/p>\n <\/p>\n First of all, that Knol isn’t all that bad.\u00a0 It helps if you read it carefully (I kept screwing up a particular step), however some of the steps are unclear apparently because the SDK has changed rather substantially since it was first written.\u00a0 I’ve tried to be ridiculously detailed here so as to eliminate any possible confusion for the novice.<\/p>\n Second, it’s not clear that you need to install anything<\/em> other than the Eclipse Classic 3.5.1<\/a> IDE and the Android SDK<\/a> to perform this experiment.\u00a0 I have the JDK, Ant and Proguard as well but they aren’t in my system paths nor is JAVA_HOME set system-wide yet.\u00a0 Therefore I suspect none of that other stuff is getting referenced in this experiment.\u00a0 You should have the IDE installed, the Android SDK installed and up-to-date, and the ADT Plugin for Eclipse (found on the SDK page). <\/strong><\/p>\n Initialize the project in Eclipse<\/strong><\/span><\/p>\n Allow it to prebuild.\u00a0 At this point you’ll have some 250+ errors but the next step should resolve them!<\/strong><\/p>\n Add the \/core\/src <\/em>code to your project:<\/strong><\/span><\/p>\n Hard way #1:<\/span><\/span><\/strong> Hard way #2:<\/span><\/span><\/strong><\/em><\/span><\/p>\n A somewhat easier way to do this (avoiding the extra copy) is to put \/core\/src<\/em> under<\/span> <\/em>\/android<\/em> (thus creating \/android\/core\/src<\/em>) before <\/strong>you initialize the project!\u00a0 Then, after <\/strong>you initialize the project you can pick the src <\/em>folder under the core <\/em>entry in the project items and select Build Path -> Use as a Source Folder<\/em> to have the desired effect (it’ll crete an entry called core\/src<\/em>).\u00a0 I would expect a symlink, correctly applied, would also have the desired effect.\u00a0 As you can see, the android <\/em>folder itself is really superfluous here.\u00a0 [I still think there’s got to be an even easier way to gather this all together, without moving ANYTHING around.]<\/span><\/span><\/p>\n The best way to add \/core\/src <\/em>to your project!<\/strong> No symlinks required (and being Windows it’s possible but not easy and besides this is even more minimalist) and it should work seamlessly even if you’re doing thing with Subversion-controlled code.<\/p>\n You’ve already created a project area called zxing (or whatever) and in it are the \/android tree and the \/core\/src tree. Rather than manually or automatically move ANY code, simply do this:<\/p>\n If you were successful, you should see a whole mess of warnings (I see over 170) – but no errors!<\/strong><\/p>\n To install and test this on the Android Virtual Device:<\/strong><\/span><\/p>\n Like I’ve mentioned, I got various odd little IDE errors as I made my way through all this… perhaps I’m doing something that’s not entirely right or the Eclipse IDE \/ Android SDK combination isn’t very stable. But will it blend<\/em>?\u00a0 That is, will it work on a physical device?\u00a0 Heck yeah!<\/p>\n To install and test this on an Android physical device:<\/strong><\/span><\/p>\n That’s about it!\u00a0 I’d expect this to work just as well from a Linux host but I haven’t tested it.<\/strong><\/p>\n Caveats:<\/strong><\/span><\/p>\n Several iterations of updates below:<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"Layout":"","footnotes":"","_links_to":"","_links_to_target":""},"categories":[1],"tags":[116,23,21,26,24,30,28,27,117,25],"class_list":["entry","author-marty","has-more-link","post-12","post","type-post","status-publish","format-standard","category-uncategorized","tag-android","tag-ant","tag-barcode-scanner","tag-building","tag-droid","tag-eclipse","tag-subversion","tag-success","tag-windows","tag-zxing"],"_links":{"self":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/posts\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":0,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/posts\/12\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/categories?post=12"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/tags?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\ntarget=android-4<\/strong><\/pre>\n
target=Google Inc.:Google APIs:4<\/strong><\/pre>\n
\n
\n
\n<\/span><\/strong><\/p>\n
\n\n
\n
\n
\n
\n<\/em><\/span><\/p>\n\n
\n
\n
\n
\n<\/strong><\/p>\n\n
\n