Building Argus on Android...

[Carter Bullard]

Hey Jim,
No there is no argus-lite.  All advanced features, however, like threads, 
pcre use, extended features, shared ibrary support, are all optional, and
selected using the ./configure program.  If you haven't done it yet,
use the autoconf support in argus-3.0.6 to build an appropriate
./configure file for your platform, and then chose the options that you
want to build a simpler argus.   Type this:

   ./configure --help

to see the kind of options that are available.

The entire porting effort of argus is centered around autoconf.  Does
Android NDK have autoconf?

One strategy to get the simplest argus would be to port argus-2.x
which are available, although I would not recommend it.  There are many
sites that are still running versions of argus-2.x, successfully, so you
would be able to generate a working argus, but 3.0 is better.

Bison and flex are very important to argus, as they are the basis of
the flow selection and filtering compilers, which are very important.  
Do these packages not run on Android NDK?  If gcc is available, then
flex and bison have already been ported, somewhere....

Argus has been successfully ported to so many platforms, that I doubt
that Android is going to be an issue.  So knocking out each issue one at
a time, is still the best approach.  What problems are you having now?

If you have any show stopper problems, send the output of the
./configure, and or the compiler errors that you are getting, to the list.
If it is really problematic, then I could get involved, if a platform is available.

Carter


On Mar 27, 2013, at 7:10 PM, "Jim Gargani" <jgargani at comcast.net> wrote:

> Hi,
> 
> I'm working on a personal project to try and build Argus on Android Jelly
> Bean 4.2.2 using the Android NDK.  I have a couple of items that I'd like to
> understand better:
> 
> #1 - Argus build:
> a.      Is there a less full-featured "lite" build of Argus I could use to
> initially port to Android Linux (ARM or Intel Atom)?  Or is the easiest path
> to use the full source build?
> b.      Is there any reason a static link of "libpcap" would be a problem
> over a dynamic link?
> 
> #2 - Role of "bison" and "flex" in building Argus:
> a.      How are these tools used in Argus?
> b.      Are they required for building alone or runtime?  Or both?
> 
> Any insight would be appreciated.
> 
> Regards,
> Jim.
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2589 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20130327/41d49f0e/attachment.bin>