linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] I tried to generate an apk with d ifferent pac


From: Sylvain Berfini
Subject: Re: [Linphone-developers] I tried to generate an apk with d ifferent package name, as seen in README, but without effec t. How to do?
Date: Fri, 07 Feb 2014 19:55:38 +0100
User-agent: Roundcube Webmail/0.9.5

Hi Rodrigo,

No you don't have to rewrite manually the manifest inside the generated apk, aapt does that on itself. If you want to check your apk, install it and use the android app manager to check it's package.

Cheers.

---
Sylvain Berfini
Software Engineer @ Belledonne Communications

Le 2014-02-07 19:08, Rodrigo Pimenta Carvalho a écrit :
Hi Sylvain.
Thank you for your attention.
However, I'm still confused.

The command ...ANDROID-4.4/AAPT LIST LINPHONE-DEBUG.APK  still shows
me:

org/linphone/mediastream/MediastreamerActivity.wnin in the list.

So, I still have a folder structure org.linphone inside my apk. Is it
fine?

I also have read the appt man and it explains that (according to our
custom_rules.xml file) :

a) the manifest is rewritten. But I just see a new manifest in the the
new package (on ADT), after running make, not a rewritten one. So,
should I manually override the old manifest with the new one?

b) R.java is generated into a different package. I is ok. I saw it.
But, how to be sure that the new R.java was used when the apk was
built?

Is there any way to certify that my apk has the correct package, as
suggested by the custom_rules.xml file?

Thank you again.
Regards.

Rodrigo Pimenta Carvalho.
--------------------------------------------------------------------------------------------------------------

Em 07/02/2014, às 11:41, Sylvain Berfini
<address@hidden> escreveu:

Hi Rodrigo,

Changing the package name in the custom_rules file has for effect to

call aapt with the --rename-manifest-package. Here's the
documentation
from aapt:
--rename-manifest-package
Rewrite the manifest so that its package name is the package name
given here. Relative class names (for example .Foo) will be
changed to absolute names with the old package so that the code
does not need to change.

Basically it doesn't change anything in the code, it only change the

package name used to identify the application (and so it changes the

install path on the device), and it's also used when the app log
messages in logcat.

Cheers.

---
Sylvain Berfini
Software Engineer @ Belledonne Communications

Le 2014-02-07 14:31, Rodrigo Pimenta Carvalho a écrit :

Hi.

I have followed the README file, changing the custom_rules.xml
accordingly (to generate a new apk with different package name),
and
run the make clean + make.
The apk was generated. So I investigated it inside and I didn't
see my
new package name in any file there. So, the changed custom_rules
.xml
file did not take effect over the apk.

However, in folder gen, seen via ADT, I see a new package and it
has
exactly the new wanted name. So, I suspect that I still have to do
something with it. But, what?

Any hint will be very helpful!

Thanks a lot.

Rodrigo.
_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers

_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers

 !DSPAM:52f520d119891922821469!
_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


!DSPAM:52f520d119891922821469!



reply via email to

[Prev in Thread] Current Thread [Next in Thread]