Yeah, I did that as well, but I couldn't find what the properties were. I zoned out on the fact that because renderscript is a command-line tool, the options would be similar to gcc. Looks like I need to spend more time writing some C code.
I added it to project.properties, so others won't run into the problem. I'll look at the camera fix now. Joe On Thu, Jun 28, 2012 at 7:58 AM, Simon MacDonald <[email protected]> wrote: > Our build.xml on line 109 includes a dependency on the Android SDK's > build.xml. So when I see the error about "renderscript.opt.level" I > realized it must be something introduced in version 20 of the SDK's > build.xml. So I just grepped through the file to see what's what and > that's what led me to the new properties. > > Simon Mac Donald > http://hi.im/simonmacdonald > > > On Thu, Jun 28, 2012 at 10:53 AM, Joe Bowser <[email protected]> wrote: >> OK, Where the hell did you find that? I've been stuck on this crap all >> yesterday! >> >> On Thu, Jun 28, 2012 at 7:46 AM, Simon MacDonald >> <[email protected]> wrote: >>> If you are like me and set your SDK to upgrade over night you can get >>> around this issue for now if you add: >>> >>> renderscript.opt.level=O0 >>> >>> into your local.properties file. Then "ant jar" will work for you. >>> >>> Basically, these two new properties: >>> >>> <property name="renderscript.debug.opt.level" value="O0" /> >>> <property name="renderscript.release.opt.level" value="O3" /> >>> >>> are used to set: >>> >>> renderscript.opt.level >>> >>> when you run "ant debug" or "ant release" respectively. So we'll just >>> need to provide the correct value for when we run "ant jar". >>> >>> Simon Mac Donald >>> http://hi.im/simonmacdonald >>> >>> >>> On Thu, Jun 28, 2012 at 2:37 AM, Joe Bowser <[email protected]> wrote: >>>> I'm using 1.8.2. The issue isn't with ant, it's with the upgraded >>>> Android SDK. If you upgrade the SDK, you get the new build.xml, which >>>> our build.xml depends on. We wrote ant jar, but not ant debug. We >>>> have to go in and see what's changed in the build script so we can get >>>> ant to compile. >>>> >>>> It's a ant script issue that is going to be a pain to resolve, and >>>> it's what I'm working on tomorrow. For the meantime, if you want >>>> things to compile, don't upgrade to r20 of the Android SDK. It'd be >>>> nice to remove the dependency on the SDK, but we weren't expecting for >>>> things to fail so badly. >>>> >>>> Joe >>>> >>>> On Wed, Jun 27, 2012 at 8:55 PM, Lorin Beer <[email protected]> wrote: >>>>> Hey Joe, >>>>> >>>>> silly question, but what version of ant are you running? Compiling to a >>>>> jar is broken, but not debug/release? >>>>> >>>>> - Lorin >>>>> >>>>> On 2012-06-27, at 5:19 PM, Joe Bowser wrote: >>>>> >>>>>> Hey >>>>>> >>>>>> I foolishly upgraded my tools today, and the current ant files are >>>>>> borked. You can't build a jar for Cordova right now with r20. This >>>>>> means that I haven't been able to test anything today because of this >>>>>> issue. I tried an ant debug and that worked fine, so I'm guessing >>>>>> Goole changed the steps again, so I'm going to go spelunking in the >>>>>> build.xml tomorrow. >>>>>> >>>>>> But whatever you do, don't upgrade just yet!!! Things are still broken! >>>>>> >>>>>> Joe >>>>>
