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. :-)