On 2010-03-17, at 19:53, Aaron J. Grier wrote: > I do not expect all combinations to be built by default. however, > if I > configure with "--enable-ide64" and "--enable-selfmodifying" I am > asking > for the above four combinations to be built. adding "--enable- > con80" to > the previous two, and I am asking for eight combinations. I was thinking along similar lines when I was writing about conditional builds. But I guess the problem starts when e.g. two different options require modifications to the same modules. For example JiffyDOS (not sure if this is a good one) AND ide64 (which I would consider both to be "important") both would modify read.s and write.s. Then you have to say "either or", which means more logic to the building process and loss of the modularity goal we wanted to achieve. OR... maintaining an exponentially growing set of combinations of different read.s-es and write.s-es. The same for options modifying other source files. Too bad :-( Having said that - I would still be happy to have at least the exclusive variations possible. -- SD! ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Mar 17 21:07:00 2010
This archive was generated by hypermail 2.1.8 : 2010-03-17 21:07:03 CET