Hey guys! I want extend the DSL for variants/flavors and add build tasks that compile for each variant to build JNI libs using our own build systems for each variant.
The way it works inside the plugin is very hardcoded in VariantManager but I would love to get a callback myself to create my own tasks. What I would love to do is know the VariantData like it's passed around internally. Right now my method is super hacky. I'm running through all the tasks as they are added and parsing the task names to add dependencies. It's not optimal. The source provider/artifact API concept looks like it is my only hook to add different libs to each variant but it's only for adding additional folders. That works for me to set directories but doesn't help me on the task side. My goal is that I'm building this so you can call arbitrary build tools (like cmake or xcodebuild) with the current variant info so that custom JNI libs can be built for each flavor/architecture/configuration. Is there is a cute method I can use without hacking or calling private APIs? The short term is I could fork and refactor the Android plugin but I don't want to pull what Amazon did (and hopefully work with their fork maybe) and be able to work if you apply my plugin after the Android one (sort of where the new NDK plugin seems to be going). Would you guys be open to pull requests if I refactor the base plugin to expose a few methods to get callbacks from the VariantManager when it's creating tasks? Thanks!!! ~ Zac Bowling Engineering - Apportable, Inc http://apportable.com/ -- 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.
