| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Standardized whitespace around function calls. | Greg Ward | 2000-09-30 | 1 | -4/+4 |
| | | |||||
| * | Added 'include_dirs' parameters all over the place. | Greg Ward | 2000-06-27 | 1 | -19/+39 |
| | | | | | | Added 'check_lib()', which provides a subset of the functionality of 'check_func()' with a simpler interface and implementation. | ||||
| * | Fleshed out and added a bunch of useful stuff, notably 'check_func()', | Greg Ward | 2000-06-21 | 1 | -32/+176 |
| | | | | | | | 'try_cpp()', 'search_cpp()', and 'check_header()'. This is enough that the base config is actually useful for implementing a real config command, specifically one for mxDateTime. | ||||
| * | First crack at the Distutils "config" command. Unlike other commands, this | Greg Ward | 2000-06-06 | 1 | -0/+180 |
| one doesn't *do* anything by default; it's just there as a conduit for data (eg. include dirs, libraries) from the user to the "build" commands. However, it provides a couple of Autoconf-ish methods ('try_compile()', 'try_link()', 'try_run()') that derived, per-distribution "config" commands can use to poke around the target system and see what's available. Initial experimenst with mxDateTime indicate that higher-level methods are necessary: analogs of Autoconf's AC_CHECK_HEADER, AC_CHECK_LIB will be needed too (and that's just to probe the C/C++ system: how to probe the Python system is wide open, and someday we'll have to worry about probing a Java system too). | |||||
