On Thu, Apr 3, 2014 at 4:30 AM, Daniel Stenberg <[email protected]> wrote:
> Forwarded with permission. > > ---------- Forwarded message ---------- > Date: Thu, 3 Apr 2014 13:12:05 > From: Kevin Ingwersen > Subject: Porting cURL into a new build system\ > > I am working on a fairly scaled project which uses a build system > different to CMake or autoconf. Therefore I had a few questions, as I am > not very good with reading configure.ac files, as I have never used it. > > - What is the bare minimum configuration, and how to compile it by hand? > As Daniel pointed out, do a regular configure as close to what you need as possible and look at the resulting config.h, modify by hand if needed. This is how I cross-compiled cURL to various different platforms in my last job, where we already had our own make based build system that could cross compile, so it was easier to just describe cURL for that. If you only need to compile for the host, I'd try to do what Daniel suggests, use the existing build mechanism. The "danger" with having your own one size fits all config.h is that you have to always settle for the smallest/lowest common subset/functionality of all your target platforms. This might or might not be acceptable to you. > Like, what does the config.h file (I guess configure would normaly create > one) need so that cURL runs properly, and which sources would then need to > be compiled? > A good starting point are the various Android.mk files for cURL that allow you to build cURL with the Android NDK. They list the necessary header and source files. For example https://android.googlesource.com/platform/external/curl/+/master/Android.mk. HTH, Fabian
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
