Yes I did exactly that. The cloned SSL source doesn't have cms.h. Would
point me an older tag that I could check out just to temporarily resolve
this?

Thanks
Andy


On Thu, Jan 3, 2013 at 9:30 AM, Andreas Steffen <
[email protected]> wrote:

> Hello Andy,
>
> our instructions recommend to get the openssl code and header
> files from our repository:
>
>   The openssl Directory
>
>   This directory contains the sources for a version of OpenSSL
>   specially prepared for the build within the Android NDK.
>   The easiest way to get these sources is to check it out directly
>   from our Git server:
>
>   git clone 
> git://git.strongswan.org/**android-ndk-openssl.git<http://git.strongswan.org/android-ndk-openssl.git>-b
>  ndk jni/openssl
>
> Did you do that step? If yes, then the recent inclusion of PKCS#7
> support into the strongSwan code base might have broken the Android
> build and Tobias must fix it.
>
> Regards
>
> Andreas
>
>
> On 02.01.2013 15:34, DreamDreams wrote:
>
>> Dear list,
>>
>> I'm trying to compile android client from source following this
>> instruction
>> <http://wiki.strongswan.org/**projects/strongswan/wiki/**AndroidVPNClient<http://wiki.strongswan.org/projects/strongswan/wiki/AndroidVPNClient>
>> >.
>>
>> But when I ran ndk-build I got this error message:
>>
>> jni/strongswan/src/**libstrongswan/plugins/openssl/**
>> openssl_pkcs7.c:24:25:
>> fatal error: openssl/cms.h: No such file or directory.
>>
>> Any idea?
>>
>> Thanks
>> Andy
>>
>>  ==============================**==============================**
> ==========
> Andreas Steffen                         [email protected]
> strongSwan - the Linux VPN Solution!                www.strongswan.org
> Institute for Internet Technologies and Applications
> University of Applied Sciences Rapperswil
> CH-8640 Rapperswil (Switzerland)
> ==============================**=============================[**ITA-HSR]==
>
>
_______________________________________________
Users mailing list
[email protected]
https://lists.strongswan.org/mailman/listinfo/users

Reply via email to