I have thought about this project for a long time, but never did anything with it. What I envision is something between winemaker, Visual C++'s project files, and autoconf/make files. Here's is what I am thinking for the moment (subject to change in next 5 minutes). A GUI application that more or less resembles the "project settings" windows in Visual C++. It lets you define the modules to link, preprocessor definitions, link options, optimizations, output name and directory, etc. I think VC++ does an admirable job of this. This "project" file that is written, probably as an internal format that only makes sense to us (maybe XML?), could then be used to generate make files for VC++, GNU make, autoconf, Borland C++, etc. In essense, provide the friendliness and less error-prone way of defining the project components and options like VC++ does, but then generate a makefile in 1 or more alternate formats. Most of my experience is with Windows programming and VWCL (www.vwcl.org), so I would most likely tackle this on the Windows platform first, just to make quick work of the basic GUI, etc. The code that does the real work would be highly portable to begin with, and the GUI on Linux/UNIX would either be provided by WineLib, or abstrected far enough from the application logic code that someone else could create a native Qt/GTK front end from the code. Basically, get the code that does the real work isolated from the pretty front end so that we can support the application on various host OS's. Does anyone beside me think this is a good idea? Been done before? Wanna help? Thanks for the feedback, in advance. Todd _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
