I have created the ant build as suggested by you but I can't figure it
out.
Unfortunantly I haven't got a day for this... :(
Can't understand how it is possible that there is no guide on how to
do that in a fast way.
On Aug 9, 5:54 pm, Bob Kerns r...@acm.org wrote:
Well, I suggested a better
so no news about obfuscating with Proguard?
On Aug 4, 10:47 pm, DanH danhi...@ieee.org wrote:
And my experience (non-Dalvik, to be sure) is that 'Class loading
time
goes up, execution efficiency is reduced' is incorrect, that the
opposite results -- in fact, that's one of the reasons to
Well, I suggested a better approach to setting up your ant script, and
we haven't heard back from you on that, so I guess that counts as no
news...
I've extracted the relevant sections from your reply below, in case
you missed it.
You haven't told us of any problem with ProGuard -- the last
After local.properties, the next problem sounds like your script is
missing a setup call.
!-- Execute the Android Setup task ...
This will ensure that the properties are setup correctly
but that your customized build steps are used.
--
setup import=false /
It's not
On 2 August 2010 16:22, dys denys.segu...@gmail.com wrote:
For one of my applications I had to use progard (more to strip unused
classes than really to obfuscate. I made a small bat script beginning
after the initial compilation (still made in Eclipse) and calling
AAPT, PROGARD, DX,
And my experience (non-Dalvik, to be sure) is that 'Class loading
time
goes up, execution efficiency is reduced' is incorrect, that the
opposite results -- in fact, that's one of the reasons to consider
obfuscation despite the pitfalls -- so I think bad advice is being
handed out with the good
I disagree. It's off topic.
Except for the point about it being harder to decompile Dalvik byte
codes, but that's just a matter of some tool development work.
And my experience (non-Dalvik, to be sure) is that Class loading time
goes up, execution efficiency is reduced is incorrect, that the
For one of my applications I had to use progard (more to strip unused
classes than really to obfuscate. I made a small bat script beginning
after the initial compilation (still made in Eclipse) and calling
AAPT, PROGARD, DX, APKBUILDER, JARSIGNER and ZIPALIGN. Are you
interested ?
On 1 août,
Thanks for your reply, very appreciated.
I'm hanging there...
Since google recommends obfuscation, why don't ask it to release a
guide on how to obfuscate apk?
On Aug 1, 7:27 am, Miguel Morales therevolti...@gmail.com wrote:
Looks like that's defined in:
ant/ant_rules_r2.xml and
Pointing out the pitfalls of obfuscation is NOT moving the thread off
topic. For in order for you to understand the answer to your
immediate question, has anyone had success at it, you have to
understand what 'success' could MEAN in the context. And DanH has been
quite generous with exactly the
Wow, thanks this maked me goes forward to next error :)
thanks...
Target package-resources does not exist in the project
what does it means, how can I specify package-resources?
Thanks.
On Jul 30, 11:34 pm, Miguel Morales therevolti...@gmail.com wrote:
Make sure you have the included files
Looks like that's defined in:
ant/ant_rules_r2.xml and templates/android_rules.xml
not sure where this is supposed to be included. you'll have to figure that out.
On Sat, Jul 31, 2010 at 7:38 AM, sblantipodi
perini.dav...@dpsoftware.org wrote:
Wow, thanks this maked me goes forward to next error
Ok, since I founded no way to automatically do it with netbeans now
I'm trying the ant way posted here:
http://just2us.com/2009/07/tutorial-obfuscate-an-android-application/
previously in this thread.
I followed all the instructions but I get this error from ant o_O
taskdef class
Just say no to obfuscation.
On Jul 30, 3:36 am, sblantipodi perini.dav...@dpsoftware.org wrote:
Since I'm going mad trying obfuscating my projects on Netbeans and
it's not reasonable
at the moment for me to switch to Eclipse I need a command line script
that let me
build and obfuscate my
Ok, thanks for the suggestions, any other idea? :)
On Jul 30, 2:59 pm, DanH danhi...@ieee.org wrote:
Just say no to obfuscation.
On Jul 30, 3:36 am, sblantipodi perini.dav...@dpsoftware.org wrote:
Since I'm going mad trying obfuscating my projects on Netbeans and
it's not reasonable
at
Well, how about going native? (NDK) That should be somewhat more
challenging than decompiling java.
Good luck / Jonas
On 07/30/2010 04:11 PM, sblantipodi wrote:
Ok, thanks for the suggestions, any other idea? :)
On Jul 30, 2:59 pm, DanHdanhi...@ieee.org wrote:
Just say no to
Keep in mind that what goes onto the phone isn't Java bytecodes but
rather the Dalvik translation. Much harder to back-translate than
bytecodes.
(I've seen obfuscated bytecodes and it's not pretty. Class loading
time goes up, execution efficiency is reduced, the odds of hitting a
bug, either in
You are so kind answering me and I really appreciate it
but there are many answers, all are off topic.
I haven't asked if it is good to obfuscate or if I need to switch to
NDK,
I asked if someone succeded obfuscating standard android class using
ant.
Please don't move this thread off topic.
On Fri, Jul 30, 2010 at 5:14 AM, sblantipodi
perini.dav...@dpsoftware.org wrote:
Ok, since I founded no way to automatically do it with netbeans now
I'm trying the ant way posted here:
http://just2us.com/2009/07/tutorial-obfuscate-an-android-application/
previously in this thread.
I followed
If this is a normal Android project, run android update project -p
..., where ... is the path to your project, and it will create or
repair your local.properties file.
On Fri, Jul 30, 2010 at 1:31 PM, sblantipodi
perini.dav...@dpsoftware.org wrote:
I have listed it in the main.xml, the problem
I have listed it in the main.xml, the problem seems that ant doesn't
find the SDK...
if you found my error on google
taskdef class com.android.ant.SetupTask cannot be found
you will find dozens of people with my same problem,
but I can't find a solution yet...
On Jul 30, 6:59 pm, Frank Weiss
done, same problem... :(
On Jul 30, 7:46 pm, Mark Murphy mmur...@commonsware.com wrote:
If this is a normal Android project, run android update project -p
..., where ... is the path to your project, and it will create or
repair your local.properties file.
On Fri, Jul 30, 2010 at 1:31 PM,
Make sure you have the included files such as:
property file=local.properties/
Which should have:
sdk.dir=/path/to/sdk_root
property file=build.properties/
Which should have:
sdk-location=/path/to/sdk_root
and
property file=default.properties/
Which should have:
target=android-3 ##or whatever
23 matches
Mail list logo
