Yes, but I didn't modify it. Instead I created a new project.
The new project ("lvl2") is bound to the jar that I build from the
*latest* google extras package, just to make sure it binds the latest
library without problem.
Yet, the old library (the one in "lvl.zip") should have bound fine, as
shown in:
http://dl.dropbox.com/u/493047/2012/04/old_lvl_certainly-bound.png
The only differences are 1) the jar files themselves (old and new), 2)
Metadata.xml because the package name has changed from
"com.android.vending.licensing" to "com.google.android.vending.licensing" .
I assume that the metadata difference was the cause of the reason, which
is why I mentioned that how jars were built is important ;-)
Atsushi Eno
On 2012/04/28 10:01, Matt wrote:
Atsushi,
It looks like you made some changes to your lvl and rebuilt today, since the
modified date is 2pm today. I agree that what you have now contains all the
types where the one you posted yesterday did not. What did you change to
make the binding generator generate all of the types?
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5671853.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
