Android SDK development root

[dablock]

What's the "drunk dialing" equivalent to posting when your too angry to post?

So LC failed to work all weekend. This morning I setup my work mac with a new fresh install of android sdk, LC 4.6.3, tech support's dx file, etc. Set up everything in order (& this is crucial because if you don't go in order this will not work at all). Amazingly, when I select my android sdk root, LC finds my jar path (which it would never do with my home mac). Perfect!!!

I create a new app with just a single text field. Select my Test Target, then click Development > Test. It's compiling....it's going to work...NO!!! Another freaking error!!!! "Unable to build app for testing: empty path."

UNBELIEVABLE!!!

I have a valid path to my 'default build folder' & 'automatically build here' is selected in Standalone Settings. Android settings are setup & use my self-signed certificate. I can see & attach to the emulator. Tried restarting LC several times & each time I get this "empty path" error when trying to test.

Does anyone have ideas what to do about this error? Or should I start another thread for this particular error since this appears to be a new issue?

[BarrySumpter]

hi dablock,

I've been there and done that with the same agro.
And still get errors like these after 4 months.
To prove it I've created a step-by-step manual for win32:
http://forums.runrev.com/viewtopic.php?f=53&t=8137

Can you please update your signature with any sort of variation on mine so we can see what platforms you're working with?

[dablock]

Hey, Barry. Thanks for your reply.

I got an email reply from tech support (thanks, Heather!) that likely explains my first problem. The reason the JDK Path is not recoginized on my home computer is because Java 1.6 is required. Unfortunately that's not mentioned anywhere here & I have a macbook which is a Core Duo which is only 32-bit & Java SE6 (1.6) requires a 64-bit processor. The only 32-bit alternative I've found is SoyLatte (a BSD port of Java6)...and the android sdk won't run with it.

So I've dropped $99 on LiveCode & wasted over 10 hours fussing with this. And this all could have been easily avoided if RunRev simply listed this in their system requirements. And my other computer with Java SE6 still won't compile an android app.

I'm throwing in the towel.

[BarrySumpter]

You can update your signature starting in the top left corner
clicking on User Control Panel
Profile tab
Edit Signature

I got LiveCode Pro running on MacBook Pro 32-bit with Java sdk for max x86.
The biggest issue I had was the rediculous size of the xCode download.

The 99$ reads like its the personal version and not the professional version.
The personal version may have its own issues.
Just like the 64-bit platform has it own issues.
Which is why I keep asking peeps to update their signature to show us what they are working with.

Can you tell me how you found the Java version on your MacBook and I'll check mine.

OK here's mine:

its the x86 that tells me its the 32bit version.

Gotta write that I get super confused when it comes to folder and file paths with anything to do with LiveCode.
It took me quite a while to figure out I had more that one java jdk installed on my computer.
It was pretty much just trial and error until I selected the right folder.

hthnh - here to help - not hender

[dablock]

Once again, thank you Barry for your assistance!

If you open the Terminal on your mac, just enter: java -version

My home macbook (OSX 10.5.8 ) displays java version "1.6.0_03-p3" because I have SoyLatte setup. But it was originally "1.5.0_30". This computer does NOT recognize the JDK Path & fails to compile.

At work, my iMac (OSX 10.6.8 ) is java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode). This computer DOES recognize the JDK Path but still fails to compile.

I purchased the personal version of LC but, as I understand it, the code base is identical regardless of version. The product key simply enables various components of the IDE.

Thanks, Barry.

[BarrySumpter]

Even with my MacBook Pro 64 bit cpu - it defaults to run in 32 bit mode

Perhaps thats why Java 64 bit runs OK in 32 bit mode?

I can't find where the MBP is actually running in either 32 or 64.

my MBP shows the same java 64 bit version as your work computer.

Other than suggesting trying to install the the Java 64bit on your 32 bit cpu,
into a different folder than your current Java,
which I'm not telling you to do, nor would I want to take responsability if you did,
you should be able to re-install SoyLatte if it didn't work out or it causes issues,
there are too many variations on the theme for me to nut out without actually trying it.

Unless theres a VM version OSX 10.5.8 that you could test on a Win32 vmware.

I thought the 64 bit software was for accessing ram over a certain amout.
If that ram wasn't there then the software could adjust.
I might be wrong.

---

With the work computer,
I'd have to see the error and make sure you're setup correctly.
i.e. pointing to the right folder or the right sub-folder.
I do recall this stuff driving me mad after quite a few re-boots etc.

[BarrySumpter]

64 bit apps can run when not in 64 bit mode. 64 bit mode just means the kernel is 64 bit.

the 32-bit kernel can run 64-bit apps, and the 64-bit kernel can run 32-bit, with no problems. they just run it in the corresponding mode.

http://forums.macrumors.com/showthread.php?t=1034905


http://landonf.bikemonkey.org/static/soylatte/

64-bit JDK for Mac OS X 10.5: soylatte16-amd64-1.0.3.tar.bz2 (sig):
http://landonf.bikemonkey.org/static/so ... .3.tar.bz2

[dablock]

Thanks again for your help, Barry.

I appreciate the information you provided but unfortunately it won't fix my issue. I understand the info you've provided, but this isn't a 32 versus 64-bit issue as you're framing it.

My macbook is a first generation 2006 macbook with a 32-bit core duo processor. Every mac since then has a 64-bit Intel processor, a core 2 or better. Apple began more fully supporting 64-bit starting with Leopard. OSX 10.5+ can run in mixed 32 & 64-bit modes (which you're describing) because OSX can account for the 32-bit code or deliver native 64-bit code to the the 64-bit processor. But the opposite is not true: OSX does not universally account for 64-bit instructions & deliver it to a 32-bit processor. So 32-bit code to a 64-bit processor is possible in OSX, but 64-bit to a 32-bit processor is not.

That's why Apple's Software Installer installs Java SE5 (instead of SE6 which is 64-bit only) on computers with 32-bit processors (ie, G3 & G4 PowerPCs, & Core Duo and Core Solo).

Even so, I installed Java SE6 anyway. But as expected, it won't run, complaining about the processor.

Bottom line, my computer is not supported but this is NOT listed in LC's system requirements.

[richervin]

Did you configure the SDK location?

It's under LiveCode > Preferences > Mobile Something on the Macintosh.

This is not working correctly in Windows XP, but worked fine on the Mac.

I extracted the Android files into the /Developer folder. Specify the top-level folder (/Developer/android-sdk-macx86?) in the preferences panel.

[menichol]

I have this same problem where can I find the solution please! Thnx.

I'm having the same issue.

I am running Windows 7 via VMWare Fusion, and have successfully installed the Android SDK (installer_r12-windows.exe) and Java SDK.

The Android SDK Manager runs fine, and have installed support for Android 2.2 (Froyo), as mentioned.

Still receiving invalid Android SDK messages... totally bummed.

What can I do?

Screenshots provided.

Screen shot 2011-08-04 at 8.09.09 AM.png

Screen shot 2011-08-04 at 8.09.50 AM.png

Thanks!

Todd