Native Code Support - False Hopes

[Trasd]

Developers,

Am I missing something here?

I was so excited when I read about the NDK C/C++ Native Code support, now I don't have to use a separate development system - OR SO I THOUGHT!

200MB in internal memory? Why in the world are you doing this? Surely you must know not all of us are on the newest, top of the line systems, but most of us can add large, external memory cards to our devices.

With such a wonderful, quality product, why was this decision made? It was a poor one. If it was in haste to get it out into the market place, please correct it.

I have no trouble with NDK and C4Droid, so it can't be an Android restriction.

Come on guys, two steps forward, one back?

[Android IDE]

AIDEs NDK support requires 140MB of internal storage and an additional 50MB temporarily on the SD card for the downloaded package while it is being unpacked. The 140MB are needed to support the standard Android NDK GCC 4.6 toolchain for ARM (including statically linked binaries, libraries for multiple Android target versions, all STL flavors, buildsystem, etc.). Full NDK build compatibility was our goal. This is something that C4Droid does not offer, not even with the GCC Plugin.

Now at least the executables (about 55MB) must reside on internal memory because SD card storage is usually mounted noexec. So far we have not bothered with putting the rest of the stuff on the SD card and symlinking it. If more users of AIDE have problems with the space requirements of the NDK we will consider it.

Hans

--
--
AIDE - Android Java IDE mailing list
andro...@googlegroups.com
http://groups.google.com/group/android-ide?hl=en

---
You received this message because you are subscribed to the Google Groups "AIDE - Android Java IDE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ide...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
AIDE Team

Twitter - @AndroidIDE

G+ - http://bit.ly/HVbYkO

[Trasd]

The download says 200MB, 140MB is much better, but only 55MB I (actually, my system) could handle.

So, unless others speak up, I'm SOL? Great.

Come on folks - speaks up! LOL, but serious, if your internal memory is limited (Iike mine) and you happen to use Google groups and you happen to see this post and you happen to need NDK, please say something. Slim chances, I bet.

I still fail to see the logic - waste not, want not. Nice addition, just wish I could use it.

[seanmo...@gmail.com]

Oh I'm having issues with space on internal memory, java apps seem to work, but the linker doesn't seem to work. I can't get any of the test apps to work if they include c code.

[Android IDE]

@Sean: What kind of device do you have? Is there an error message
displayed? Did you get a dialog after downloading the NDK that it is
installed and configured properly?

On Sun, Oct 13, 2013 at 6:20 AM, <seanmo...@gmail.com> wrote:
> Oh I'm having issues with space on internal memory, java apps seem to work, but the linker doesn't seem to work. I can't get any of the test apps to work if they include c code.
>

[Tom Arn]

I'll side with you.
I'd also prefer to just use 55 MB instead of 140 MB of valuable internal storage.
Tom

[bitter...@yahoo.ie]

Are you trying to develop C application code on a phone?  I am trying AIDE on mini-android stick that you just plug into you tv via the hdmi port.  It has an rk3066 dual core processor and a GPU.  I haven't tried the NDK support yet.  It should be no problem.  I am interested in using renderscript when I get more experience.  I guess I will have to use the android sdk to do that. 
I tried android studio and it was very slow.  It was like watching a slug eating a lettuce leaf.  I think even a 8 core PC with 16Gb of ram would hardly speed things up enough.  That is an example of really bad system planning.  The advice to write fully functioning code first and only then optimize has been dished out by algorithm designers who have never created an application with more than 1000 lines of code in it, that is to say Knuth is to blame.