Hi Mark ! Can you explain why the "JAR-way" is wrong ? I´ve been using AS over 1 year (and IOIO 4 months) now and it has been stabilizing very well at that time. I had difficulties using libraries in AS, but it seems very straightforward. The best way to move to AS is: - create new AS project (no importI, then the Gradle is clean - put the library JARs in libs-dir - make sure that build.gradle contains dependency compile fileTree(dir: 'libs', include: ['*.jar']) - copy the source code files from Eclipse or where ever you have them, to the src-dir and build the project
I've been using this way also AWS SDK (from Amazon) with no problem. Why do you need IOIOlib in source code format ? I think the intended way in AS is use JAR for the "old" libraries and AAR format for new (maybe AS can produce these, but I do not know how). JAR-files seem to contain everything (manifest-file etc.) that is needed. I have never been using Eclipse only AS, so I cannot say which one is better, but I decided to learn the new tool and not the old one ! Hi Guys, > > I didn't realize that Android Studio is the "official" IDE now. Do you > know why they are moving away from Eclipse and ADT? There is a lot of > infrastructure there... > > I tried to use Android Studio awhile back (version 0.8.something) and > never succeeded in getting a project to build. I kept getting Gradle > errors and it would not work no matter what I tried. Since AS is the > "official" IDE, I took a crack at getting the IOIO sources set up in it > yesterday and once again, I failed miserably. I managed to get the base > IOIOLib built in AS as a simple Java module (I refactored the Log class to > remove the dependency on the classes in the target/android and target/pc > folders), but I spent about 4 hours trying to make simple Android project > (for IOIOLib_Android) that simply used the core IOIOLib project as a module > and I could not make it work. From what I can see, to consume the library > in source form, AS always "copies" the whole library source tree into the > current project (this seems wrong), but even when I add the dependency on > this embedded module, it would not work. It simply would not resolve the > classes. > > I tried to revisit it this morning and figured I would start from scratch > and import one of the basic samples (File > Import Sample...) and not even > this works. The code that gets imported is immediately mangled by AS and > gives Gradle errors that I could only resolve by manually editing the > Gradle build files. This is the same nightmare I had the last time I tried > to use AS. Frankly, it blows my mind that you would need to edit build > files for the simplest of projects. Just do a Google search for "android > studio external library dependency" and you'll see just how many people are > having issues with this. Why is this so difficult? I can understand > having the "power of Gradle" at your fingertips, but I can hack Ant files > to do amazing things too if I want to. > For me, Eclipse+ADT just works out of the box. Indeed, I had Eclipse > building a sample with the latest code and was debugging (over wifi no > less) in 20 minutes after giving up on AS this morning. I gave AS a > *really* earnest try and lost an entire day trying to make the simplest of > tasks work. Is this really a 1.0 release?? > > I'd be willing to help out here, but for the moment, I need to get some > work done and I can't seem to do that in AS unless I just drop .JAR files > in there, which is not what you are looking for. I'm going back to Eclipse > for the moment, but if anyone has made any better progress than I have, I'd > be happy to hear about it and lend a hand when I can fit it in. > > Regards, > Mark. > > > On Sunday, 21 December 2014 13:24:03 UTC-5, Ytai wrote: >> >> @Heikki, thanks, but I'm looking for deeper integration than building a >> JAR. A JAR doesn't contain Android resources, manifest files etc., which >> are important to reduce the amount of boilerplate the application that uses >> them then needs to do. >> >> @Adam, AAR sounds like the right direction. I'll take you up on your >> offer. Any chance you can send a draft pull request with some explanations >> for a noob like me. >> >> @Al, I hear you. I will consider leaving both platforms supported, >> although if I had to make a choice I would go for the officially supported >> thing. Ideally, if all libraries are Maven targets the choice of IDE used >> for app development becomes less critical. >> >> On Sat, Dec 20, 2014 at 12:14 AM, Al B <[email protected]> wrote: >>> >>> I'm not sure I follow the subject of this thread "Time to move IOIO to >>> Android Studio". Does it mean that IOIO is planning to not longer support >>> the Eclipse IDE? That will be sad. Come one? Not now that I can set my >>> Luna environment to look like the Studio (see attachment). >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "ioio-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/ioio-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
