Nick Mathewson wrote:
[How it's _supposed_ to work is this: on everywhere that has a shell
that can handle autoconf, the autoconf script detects the system
settings and generates a config.h file, which gets post-processed into
a event-config.h automatically. On anywhere without a shell that can
handle autoconf (this is basically only Visual Studio), we use a
pre-generated event-config.h file that has the right settings for
Windows on Visual Studio's idea of C.]
If you provided waf or cmake files too, then they can also do the simple
platform config
chores, but work cross-platform. Both will generate config files.
cmake has the advantage that it will generate VS configs that can then
be used by devs who
want to fiddle with the software - but waf is probably more
straightforward and Python is
probably not too hard a sell as a prerequisite.
Perhaps something to consider for 2.x?
James
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
