Proton build system requirementsPage comment added by Rob GodfreyI agree with Gordon's top two priorities... I consider both of these to be essential requirements. (3) for me would be two have the source structure / build scripts we release to be identical to that within subversion. Having the source / build scripts differ between how the developers use it and how the end users experience it would seem to be to be a great way to ensure that we introduce bugs into our user experience. One thing that is absolutely not a priority to me is to make sub-directories of proton to be completely isolated from each other. If a developer wishes to change the proton engine API (s)he needs to be aware of the effects on all the language implementations not just their favoured language.
In reply to a comment by Gordon Sim:
My prioritised list would be: (1) no 'foreign' toolchain should be imposed on developers that do not need it (vital for end users, just nice to have for those contributing to proton itself)
Change Notification Preferences
View Online
|
|
- [CONF] Apache Qpid > Proton build system requirements confluence
- [CONF] Apache Qpid > Proton build system requirements confluence
- [CONF] Apache Qpid > Proton build system requirements confluence
- [CONF] Apache Qpid > Proton build system requirements confluence
- [CONF] Apache Qpid > Proton build system requirements confluence