Yitzchak Scott-Thoennes wrote:
>On Wed, Jun 15, 2005 at 05:28:35PM +0100, Steve Hay wrote:
>
>
>>I have it working, courtesy of change 24852! Nothing much to it, really.
>>
>>
>
>Huzzah! Now do you feel like getting static extensions working there?
>It's the only remaining holdout. If you don't, I'll try to have a
>look at it at some point.
>
>
Done! Changes 24862 and 24866.
>
>
>>It was partly due to the switch to Winsock2 (the addition of ws2_32.lib
>>had been omitted from the BORLAND case, but even these free Borland
>>tools come with it!), and partly due to (my!) new dmake binary which no
>>longer expands escape sequences like \n unless explicitly requested with
>>an :m modifier (which Sarathy's old dmake doesn't support).
>>
>>Oh, and one other niggle: the resource compiler was set as "rc", but
>>actually seems to be called "brcc32".
>>
>>A couple of tests complained that they couldn't find cc3250mt.dll (which
>>is in the Borland compiler Bin directory).
>>
>>
>
>IIRC there's a note in README.win32 about that. Which tests get the
>missing dll? taint.t could be made to copy the dll to the t directory
>the way I think it does for cygwin. (Necessary because it clears
>PATH.)
>
Yes, it is op/taint.t with the missing DLL, and yes, README.win32 does
mention it ;-)
I had a look at getting op/taint.t to copy the DLL like Cygwin does, but
unlike the Cygwin case, the Borland DLL doesn't have a predictable name
(mine is called bcc3250mt.dll, other versions presumably have different
names) and doesn't live in a predictable place (mine is in
C:\Borland\BCC50\Bin, but this won't always be true).
We could scan through $ENV{PATH} (before clearing it!) looking for
bcc3250mt.dll, but even then we can't copy it using system() quite as
easily as Cygwin because Win32 doesn't actually have a copy executable
-- it is built into the shell... which also doesn't have a predictable
name (cmd.exe, command.com) or location.
I gave up there :(
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are
confidential and intended for the addressee(s) only. If you have received this
message in error or there are any problems, please notify the sender
immediately. The unauthorized use, disclosure, copying or alteration of this
message is strictly forbidden. Note that any views or opinions presented in
this email are solely those of the author and do not necessarily represent
those of Radan Computational Ltd. The recipient(s) of this message should
check it and any attached files for viruses: Radan Computational will accept no
liability for any damage caused by any virus transmitted by this email.
