> I don't know; but the various makefiles in the src/ subdirectory (other than > src/Makefile) bypass configure completely: when using them (e.g. to compile > Vim using various Windows compilers), configure is not used at all. If you > create a new (let's say) src/Make_ast.mak, you could do the same, using Make > variables (which can be set by environment variables) for any "user-settable" > options (such as, e.g., the tiny/small/normal/big/huge featureset, console > Vim > or gvim, do or don't include MzScheme/Perl/Python/Ruby/Tcl interfaces and > where are their libraries, etc.). See the various src/Make_*.mak for > examples, > and in particular Make_cyg.mak which runs on Windows but in a Unix-like > environment, and cross-compiles a Vim for native-Windows.
This would be an advisable approach, i.e. starting with a Makefile, not with ./configure. I believe this would be relatively easy, too, as I believe Vim has used ./configure only relatively recently, so won't rely so heavily upon it as other projects do. Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
