If I understand you correctly, I think you're advising me to do what I
may have already tried: copy MyCustomParcelable.aidl (which contains
only a package statement and a parcelable MyCustomParcelable
statement) into my second app's source tree.
I just tried it again, and that does not work.
If it works for building the library, I don't see any reason why it
won't work for building the app. You can look at the remote service
API demo to see how things should be set up.
On Nov 8, 8:11 am, DulcetTone [EMAIL PROTECTED] wrote:
If I understand you correctly, I think you're advising me
You'll need to make the source .aidl files available for them to
import.
On Nov 7, 3:21 pm, DulcetTone [EMAIL PROTECTED] wrote:
I have a custom Parcelable which I have gotten working internally in
the project in which it is compiled.
That project is then exported as a JAR in Eclipse, and
Hi, hackbod.
Can you be more explicit in this?
tone
On Nov 7, 11:53 pm, hackbod [EMAIL PROTECTED] wrote:
You'll need to make the source .aidl files available for them to
import.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Well, you need to have the source .aidl file in the sources of the app
that is using it, just like you have it in the library. These don't
work like Java files where you can link to the generated jar or
whatever without the source; the source is needed for everyone that is
compiling against it.
5 matches
Mail list logo