John Cowan wrote:
I'm starting to see a CMake-ish design. I think what I want are 2 well-defined states of development:Brandon J. Van Every scripsit: - given a Chicken compiler and Scheme source code, generate a canonical set of C files. - given a C compiler and a canonical set of C files, generate a Chicken compiler. This is not really how the current build system is set up. These notions are mishmashed around a lot in "stage2, stage3, create a distribution," etc. If only these 2 well-defined points of compilation existed, it would be easier to maintain. Furthermore, CMake should implement a search capability to locate Chicken compilers. None of this "set the magic BOOSTSTRAP_PATH" stuff. You wouldn't care about something being "stage2" or "stage3." You'd only care that you've found several Chicken compilers, and that you're using the most recent / appropriate one for your build. Defaults would be reasonable, and the user could intervene to select a specific Chicken compiler if necessary. Cheers, Brandon Van Every |
_______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
