Re: Building PilBox

[Erik Gustafson]

Hi Alex,


> https://developer.android.com/studio/index.html

Yes, I downloaded it from there.


Ok, cool.


 I believe you can just unpack the tar ball and then "import"
it into a new project.


Sounds simple enough, I think my lack of experience with the Android
ecosystem is the culprit here. I'll keep at it.

Thanks,
Erik

Re: Building PilBox

[Alexander Burger]

On Sun, Apr 02, 2017 at 11:09:05AM -0500, Erik Gustafson wrote:
> How are you getting the Android Studio SDK (referred to as '../Sdk/' in the
> README)? I tried getting it from
> 
> https://developer.android.com/studio/index.html

Yes, I downloaded it from there.

I don't remember the exact details, as I did not use it for a while, and then
only used it to develop PentiKeyboard (Java without any native or PicoLisp
parts).

If I recall correctly, I later used the SDK itself to install the NDK via some
menu.


> but it did not have the expected directory structure and I could not find

What is the expected directory structure? Here it simply has one subdirectory
for each project. I believe you can just unpack the tar ball and then "import"
it into a new project.

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Building PilBox

[Erik Gustafson]

Hmm...

How are you getting the Android Studio SDK (referred to as '../Sdk/' in the
README)? I tried getting it from

https://developer.android.com/studio/index.html

but it did not have the expected directory structure and I could not find
'make_standalone_toolchain.py'. I also tried using the Android Studio IDE
and various arch linux packages, but none seemed to produce the expected
directory structure.

Instead I grabbed the Android NDK from

https://developer.android.com/ndk/downloads/index.html

which includes 'build/tools/make_standalone_toolchain.py'.

Using that to build the toolchain into 'PilBox/' seems to work fine, as all
the files needed for 'mk.arm64.linux' are in the right places. Then, at
some point during the build ('./mk.arm64.linux') process,
'toolchain/bin/clang38' is executed (presumably from
'toolchain/bin/aarch64-linux-android-clang'?). And 'clang38' expects
ncurses? I'm just as confused as you here.

I'm guessing the problem is that I'm using the NDK instead? Probably should
have mentioned that in my first mail...

Erik

On Apr 2, 2017 8:10 AM, "Alexander Burger"  wrote:

He Erik,

> preparing the toolchain, but './mk.arm64.linux' fails with the following
> (abridged) error messages:
>
>../../toolchain/bin/clang38: error while loading shared libraries:
> libncurses.so.5: no such file

This makes absolutely no sense to me. Ncurses should not be needed anywhere
to
build the binary.

Can you find out more about the context?

♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Building PilBox

[Alexander Burger]

He Erik,

> preparing the toolchain, but './mk.arm64.linux' fails with the following
> (abridged) error messages:
> 
>../../toolchain/bin/clang38: error while loading shared libraries:
> libncurses.so.5: no such file

This makes absolutely no sense to me. Ncurses should not be needed anywhere to
build the binary.

Can you find out more about the context?

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Building PilBox

[Erik Gustafson]

Hi Alex,

I'm finally getting around to exploring PilBox. I installed the ready-made
pilBox.apk to my phone and tried it out. Very cool, lots of potential there
:)

I've run into trouble trying to get it setup for myself, however. No issue
preparing the toolchain, but './mk.arm64.linux' fails with the following
(abridged) error messages:

   ../../toolchain/bin/clang38: error while loading shared libraries:
libncurses.so.5: no such file

   ../../toolchain/bin/aarch64-linux-android-strip: {'../bin/picolisp',
'../lib/ext', '../lib/ht'}: no such file

Thoughts? I have ncurses 6.0 installed on my (arch linux) system.

Thanks,
Erik