Okay guys, I haven't touched the code since friday, but today I must finish this. So I guess I made the dumb error of not using the standalone toolchain.. I will try that. Can you (Dan or Guenter) send me any params for the configure ? what I am doing now is the following : 1. made a standalone toolchain and put it in opt 2. added Guenter's local folder in the toolchain 3. call the configure script like this
export PATH=/opt/arm-linux-androideabi-4.4.3/bin:$PATH ./configure --host=arm-linux-androideabi 4. make the configure goes OK, the make goes OK.. by the way is this normal? (copied from the configure output) checking build system type... x86_64-unknown-linux-gnu checking host system type... *arm-unknown-linux-androideabi //???* but I have no libz or libssl support (what I noticed in the config after the configure ) and I guess it's because I don't add the support.. but how do I add the -lz in the standalone toolchaing? and how do I add the ssl support (again WITHOUT OpenSSL ENGINE support.. just https://) thanks for your help Tancho On Thu, Jul 5, 2012 at 7:59 PM, Dan Fandrich <[email protected]> wrote: > On Thu, Jul 05, 2012 at 07:17:01PM +0200, Guenter wrote: > > Am 05.07.2012 15:37, schrieb Tancho .: > > >2. the script I'm using is actually just setting the environment and > > >then calling the curl config script, it's based on the explanations in > > >the Android.mk file comments by the dev team > > you mean the Android.mk in libcurl source tree? Then sorry, I cant > > comment on this one since I never used it; but if you wait a bit I'm > > sure that Dan will comment on this ... > > If you use the standalone Android toolchain (from > make-standalone-toolchain.sh), you don't need Android.mk or the > instructions mentioned within it. I used Android.mk when creating Android > ROMs that included libcurl built-in, but you will probably also need it > when writing code using the NDK. If you can avoid it, do so, since > getting the config.h file built correctly the first time using the > instructions in Android.mk can be tricky and time consuming. You could > also try creating config.h using the standalone toolchain, then using > the NDK and Android.mk to build libcurl. I'm not positive that the > compile and link options are the same in both environments, but the kind > of things that configure looks for ought to be. > > >>> Dan > ------------------------------------------------------------------- > List admin: http://cool.haxx.se/list/listinfo/curl-library > Etiquette: http://curl.haxx.se/mail/etiquette.html >
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
