Ah. I did my test from the command line, rather than from Eclipse. cd testpr~1 ant release
If doing it that way works for you, you can set up an ant launcher for Eclipse that invokes it in the same manner. If this works for you, and you can't figure out how to set up a suitable launcher to do that from inside Eclipse, let me know and I can walk you through it. On Dec 20, 10:37 am, H <[email protected]> wrote: > Thanks for the suggestions Bob. > > I've just restarted eclipse and told it to open my project from "docum~1" > instead of "Documents and settings". But when I try to do a proguard build, > it still fails. In my windows temp folder I can find a new .pro file created > and inside it I can find the following "-injars > C:\DOCUME~1\H\LOCALS~1\Temp\android_7024561833062132179.jar;C:\Documents and > Settings\H\workspace\android\xxx\xxx.jar ...... -printusage C:\Documents > and Settings\H\workspace\android\xxx\xxx...." where you can still see some > mentions of "Documents and Settings". There are several more, but I've > omitted them for brevity.. :-) > > So the BuildHelper provided by ADT that produces this .pro file which it > then passes to proguard via ant, is still producing the wrong content for > this file. And the proguard task can't run as it it can't understand an > injar of "c:\documents" (for example). > > The only solution (other than a fix to the adt) is to move the whole > workspace to a folder heirarchy without spaces in it, which is not allowed > under the current policy. And, to be honest, that's right for Windows xp and > has been for many years now. But it don't help me now! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
