Re: [perl #41243] [TODO] Link on Win32 with Borland C++

On Tue, Dec 16, 2008 at 12:20 PM, Ron Blaschke <[email protected]> wrote:
> Andrew Whitworth wrote:
>> I'll pick up borland and play with it, although I won't get to it
>> until the next cycle. I've got a really old version of Turbo C++ 4.52
>> left over from school, and free versions of Turbo C++ Explorer are
>> available for download. I don't promise any miracles, but at least I
>> will be able to prove that some errors still exist or not.
>>
>> --Andrew Whitworth
>>
>> On Tue, Dec 16, 2008 at 12:49 AM, Will Coleda via RT
>> <[email protected]> wrote:
>>> On Thu Jan 11 09:55:40 2007, stmpeters wrote:
>>>> On Thu Jan 11 08:57:22 2007, coke wrote:
>>>>> Need details.
>>>> A recent patch has gotten Parrot to the point that it can be compiled
>>>> with Borland C++ on Win32.  Unfortunately, it does not link correctly to
>>>> actually create a valid parrot executable.  Additional configuration is
>>>> needed to make Borland compile and link Parrot so that it can actually
>>>> be run and tested.
>>> Without a champion for this compiler, there's not much we can do; Our current targets for
>>> Windows include, as I understand it, cygwin, strawberry perl and its build system, and recent
>>> versions of VisualC++. Borland isn't in our core list for the upcoming 1.0 release.
>>>
>>> If we do find a Borland champion, they should open a new ticket at https://trac.parrot.org/.
>>>
>>> Rejecting this ticket; Regards.
>
> Some time ago, because of this ticket, I tried with Borland C++ 5.5.1
> and 5.82, and failed miserably.  But that may just be my bad bcc-foo.
> Unless someone's keen for this platform and has access to a fairly new
> ("within two years") version (is it called C++ Builder now?), I'm not
> sure if this is worth pursuing.
>
> Ron
>

The issue I ran into at the time was that dmake, which was the usual
make program used with bcc32, is not capable of handling the Parrot
make file.  I believe it could work with gmake on win32, but I hadn't
really attempted anything down that direction since I was encountering
too many other issues following a major restructuring of the headers
that had occurred.

Steve