55261 pet-ro == Introducting the new paste == Currently there are two other pastes to the #dylan channel to manage the quality of the processes which are administrated by the Open Dylan Community: * Paste number 54106: Recommend web site updates http://paste.lisp.org/display/54106 related to web presentation of the Open Dylan Community * Paste number 54932: CDAN proposals http://paste.lisp.org/display/54932 related to the idea of the Open Dylan Community to come up with a CDAN (CDAN Comprehensive Dylan Network Archive) 'CDAN proposals' focus is to discuss the structure of the CDAN and how the structure is mapped to repositories. Related to the topic CDAN is the topic Build Mangement And now we additionally open this, which is titled * Discussing ODC's Build Management related to Open Dylan Community's Build Management Here we discuss improvements to the Build Management in general. And of course we discuss here how to come up with a Build Management that works well with an upcoming CDAN. The Open Dylan Community already have several project stups related to Build Management. As time goes on you will find annotations about them here. 3410924304 #dylan 1 pet-ro To build a compiler which is part of an Open Dylan release use * admin\build\build-release.bat How to use that for a build process of an Open Dylan release is described elsewhere ( see: http://wiki.opendylan.org/wiki/view.dsp?title=Building%20an%20Open%20Dylan%20release --Note: currently under construction ) Here we focus on improvement on how build-release.bat does it job. Example: Handling related to MS Visual Run-time == Situation == * I prepared a build by ** setting MPSKIT of run-time/pentium-win32/makefile accordingly ** copying the relevant two jam files * I started a build of an OD release. ** It stops with: cannot open input file "minvcrt.lib" with in the first generation == Proposal 1 == * Starting a build-release with the option /internal-release could use msvcrt.lib from the MS environments to support the first generation. Maybe we can use WIN32_LIB_PATH as defined in http://research.microsoft.com/invisible/conf/make/first.mk.htm to copy relevant MS stuff to the Open Dylan build area * Starting a build-release with the option /external-release could add a minvcrt.lib to release, which IMHO is not required in an internal-release. See archive-note related to minvcrt to understand this handling http://www.opendylan.org/pipermail/gd-chatter/2006-May/008593.html == Proposal 2 (Alternative to Proposal 1) Check why minvcrt isn't build during generation 1. * Note: there is a related section run-time/pentium-win32/makefile but currently I do not understand why then it ends up in a 'cannot open input file "minvcrt.lib" ' message. pet-ro do not have time to dig into this the next few days. Feel free to comment. I welcome any enlightment. :-) 3410938504 #dylan