Thanks, that explains a lot :) But what about just copying the android.mk file from the source tree inside the folder I get from extracting the strongswan-4.2.9-stable-4853.tar.bz2 file instead? Would that work? (and why isn't that file there in the first place? Wrong version?)
Federico -----Opprinnelig melding----- Fra: Tobias Brunner [mailto:[email protected]] Sendt: 21. oktober 2011 16:16 Til: Mancini, Federico Kopi: [email protected] Emne: Re: [strongSwan] Strongswan on android gingerbread > Now I don't understand why I should build a tarball just to extract > it again Yes, that's strange, isn't it ;-) The reason for this is that building the tarball also creates several generated files, which cannot be done that easily directly inside the Android build system. These files are generated by bison/flex, gperf and some contain variables replaced with sed (the top Android.mk for instance). Anyway, you can actually do this without explicitly building a tarball, right within the strongSwan source tree. Please run the following commands: ./autogen.sh ./configure make make distclean This result in a tree similar to an unpacked tarball. Regards, Tobias _______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
