i have a maven-based android project which uses the ActionbarSherlock as an apklib-dependency and Gson as an jar-dependency. Building the application with maven works just fine, but i cant start/run the application using eclipse as long as the ActionbarSherlock dependency is added.
Is it possible that eclipse can´t handle the apklib-dependency? I also had to add the lib as a library project to my eclipse workspace and add the dependency to maven. otherwise i can´t access the actionbarsherlock from my code...
Thank you :)
Support for apklib dependencies in ADT Eclipse is part of ongoing work for the m2e-android project. Please comment on this issue to stay updated:
https://github.com/rgladwell/m2e-android/issues/8
The current workaround is to add the complete source code of apklib to your workspace.
Related
I have been trying to get the facebook sdk v4 to work with my existing libgdx android project. Here are the steps i took:
¹. Imported facebook android sdk v4 as gradle project to my workspace. Went well
Edited my android projects properties to include facebook sdk as library. Didnt work,couldnt import classes
Reverted 2nd step and added project to java build path. Didnt work
Added individual jar files as dependencues. Worked but not all classes could be imported maybe the one that were not included in jar?
Now I am totally confused as most of the topics online refer to older sdk.Please guide me
You can update your libgdx project to Gradle using https://github.com/libgdx/libgdx/wiki/Project-Setup-Gradle. Then you can add a dependency to the facebook-android-sdk artifact as described in 4th and 5th step here: https://developers.facebook.com/docs/android/getting-started#androidstudio.
I created a sample HelloWorld app on Android using Eclipse! It's not importing a java package. What could be wrong?
Try rebuilding your project. This link explains: http://izvornikod.com/Blog/tabid/82/EntryId/12/How-to-force-Eclipse-to-rebuild-generated-resource-class-R-in-Android-project.aspx
First you have to remove error from res folder its might be a reason nd then clean your project
2.Check you add android support v7 appcompat library in your project if not then first you have to add it in your project and also clear android support v7 appcompat library. if library having error then never reslove in your project.
may this info. help to you :)
I have a problem importing the PagerSlidingTabStrip library into Eclipse, I get multiple errors and I know this happens because the library was built using gradle.
I tried to follow this answer but I can't find use as source folder in the build path menu.
I've never used gradle previously and don't know how to go about this in Eclipse. Please guys, help most of us who have this problem out of our dilemma. Would be very grateful.
Okay in the end this was what i did:
I checked the build.gradle file of the library for target and min sdks. I then put what i found in the android manifest.xml which I know Eclipse uses.
I deleted the build.gradle and gradle.properties files.
Made sure the project was marked as a library. And it works!
I think the most crucial step was to check the build.gradle for the sdks and whatever else the project requires and replicating that the way it should be in the manifest file.
I am using Android Studio for building an application, in which I am using Facebook-SDK and Actionbar Sherlock as a dependencies. Each project library contains android-support-v4.jar.
When I am trying with any one of the project library it is working well. But I'm facing problems when trying to implement both simultaneously.
I know that I am facing the problem due to android-support-v4.jar.
I want to know how to add android-support-v4.jar in an efficient way.
\Android\android-studio\sdk\build-tools\android-4.2.2\dx.bat failed
I just solved the similar problem. On my case and most probably on your case also, the problem is on adding android-support-v4.jar for multiple times. I then remove the dependencies of android-support-v4.jar from my project's build.gradle and just have a single dependencies on facebook build.gradle, as facebook sdk was first to build on my project.
I faced this problem yesterday. I got it to work by making sure that there is the same android-support-v4.jar file in all libs directories throughout the project. The facebook-sdk and ABS ship with versions that might not be current when compared to the one that is installed by default by Android Studio. Let me know if it works.
If you need help integrating libraries in Android Studio, I recommend looking at facebook-sdk's step by step tutorial. I am sure once you integrate facebook-sdk you can use those steps to add any other library that you need by making small changes (i.e. use the name of the library you are trying to add instead of facebooksdk on the settings.gradle and build.gradle)
Today, I updated my Android SDK and Eciple ADT to the most recent versions (ADT Rev 22). After restarting Eclipse it is quite unhappy with the Build Paths whenever I reference custom libraries.
An example is shown in this screenshot:
My custom "Android Utilities Library" compiles fine, but everything that depends on it shows build path errors. E.g. when I investigate the build path settings for "Android URA Library" it shows me an error with the android_utilities_library.jar missing under "Android Dependencies" (which in fact is true, the libraries will be built to individual class files in bin/classes).
After reading the solution to Build path errors with library projects I tried to clean and manually build my projects in the correct order, but to no avail.
I've never dealt with this before, so I don't know how to attack the problem.
Any help is appreciated. Thx!
Installing the new Build Tools did the trick. They were not automatically included when I updated the SDK (probably need to run the update twice I guess).
I found a solution that works for me:
Go to Project Properties > Build Path > Order and Export
Then you have to check each checkbox.
In my case my libraries were restored
I hope it will help.
I can see that your project Android URA Library is referring to Android Utilities Library, then the problem should not relate to SDK/ADT update.
Please check:
Project Properties of Android URA Library, choose Project tab and make sure you added Android Utilities Library as dependency project. Otherwise, please add it.
If the problem is still existing, then Projects \ Clean All Projects
Go to libraries and check the build path of the dependent libraries. It should be same as your projects build path.
if you have import all the Dependencies in your workSpace.maybe you can:projetc-->build all.
I meet the problem,and it works well