So I've finally got things setup. Half of my issues were me not knowing
gradle well, and the other half I think was a bug in AS. It got so bad that
at one point, AS thought the project didn't use gradle (Even though all
necessary gradle files existed). Also, when adding modules, it didn't seem
to actually add them (I checked the modules.xml file in the .idea folder,
and it wouldnt change at all after changing the settings.gradle file). Once
I created a new project and started over, things went much, much more
smoothly.
On Friday, September 19, 2014 8:40:00 PM UTC-4, Ryan Bis wrote:
>
> Ok, I've been trying to get this to work, and haven't had much luck. I
> keep getting Configuration with name 'default' not found.
>
> So I've got a few libraries, I'll list what I have right now:
>
> Library A
>
> Library B -> depends on Library A, and has an imported module. I'm getting
> the above error in this library project. I just created a new project, and
> added the dependencies.
>
> gradle.settings file:
> include ':app'
> include ':LibraryA'
> include ':BModule1'
> project(':LibraryA').projectDir=new File('path/to/librarya')
>
> Then in the :app build.gradle dependencies section:
> compile project(':BModule1')
> compile project(':LibraryA')
>
> Library C -> depends on Library A, and depends on google play services.
> This would be setup similar to Library B, only with the google play
> services dependency, instead of the module. I haven't set this up until I
> get Lib B working.
>
> Project
>
> I have different flavors which will use either Lib B, C. (Which as I
> understand it, would also give all flavors access to Lib A). I think I got
> how to get this one setup how I need it, I just need to get the other
> libraries to build properly.
>
> Thanks for any insight.
>
> On Thursday, September 18, 2014 12:51:09 PM UTC-4, sbarta wrote:
>>
>> Yes, you can do it. The general approach is to put the source library
>> someplace convenient to all the projects using it, getting it to build
>> independenly under Gradle, and then in projects that use it, add a module
>> and point the module to the directory where the module lives. You can do it
>> in settings.gradle like this:
>>
>> include ':libraryName'
>> project(':libraryName').projectDir=new File('/path/to/library')
>>
>> On Thu, Sep 18, 2014 at 9:46 AM, Ryan Bis <[email protected]> wrote:
>>
>>> So when you import a source library, it seems to copy that library's
>>> contents into the current project.
>>>
>>> I have a library that is used with several different projects. This
>>> library has it's own repo (which is separate from the project's repo).
>>>
>>> So, as it seems AS copies the library into the project, what happens
>>> when that library's repo gets updated? Does this mean I have to copy these
>>> changes throughout all of my projects? Is there an easier way to set this
>>> up, so that I don't have to manually edit the library in every project that
>>> it's in?
>>>
>>> Thanks,
>>> Ryan
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "adt-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
