Borland support is not as seamless as MinGW, yet; it should still be very usable. (At least for Parrot proper; I have not tried any of this with IMCC, Perl6, or the other languages.)
This works for me with ActivePerl 631 (5.6.1), and Borland's C++ 5.5.1 (The free version).
First, configure with 'cc' and 'link' set to 'bcc32', and removing the linkflags from Perl5: 

perl Configure.pl --cc=bcc32 --link=bcc32 --linkflags=""

[download]
Edit "Makefile", changing 'AR_CR' from 'lib cr' to 'rem', like so: 
-AR_CR = lib cr
+AR_CR = rem

[download]
Then build and test the code. Expect lots of warnings during the build. 
nmake
nmake test

[download]

If you don't have nmake, get it free from Microsoft here: nmake. Borland's make will fail without some hacking.

I get these test failures, all of which I expected. (I am working on patches for all of them; none should affect your use of Parrot assembler): 

Failed Test     Status Wstat Total Fail  Failed  List of Failed
---------------------------------------------------------------
t/op/hacks.t       1   256     9    1  11.11%  7
t/op/string.t      1   256    99    1   1.01%  97
t/src/basic.t    255 65280     2    2 100.00%  1-2
t/src/exit.t     255 65280     2    2 100.00%  1-2
t/src/intlist.t  255 65280     4    4 100.00%  1-4
t/src/list.t     255 65280     2    2 100.00%  1-2
t/src/sprintf.t  255 65280     2    2 100.00%  1-2

[download]
Also, expect some tests to pass, but give spurious/false exit code failures, like this: failed with exit code 1 Again, this is a known bug in Win32. (I just haven't filed the patch, yet).

In reply to Re: Parrot build mechanism expertise required. by Util
in thread Parrot build mechanism expertise required. by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.