D7 Enterprise Trial - Missing DCC32.exe
Mike Dobson
In short: downloaded Delphi 7 Enterprise Trial, appears to be
missing DCC32.exe command-line compiler...
Few more details: D7ET appears to work fine within IDE, but
the command-line compiler executable (DCC32.EXE) appears to
be missing entirely, even though there IS a DCC32.cfg file
created on installation (as WELL as a DCC32.exe entry in the
registry, same keys as Delphi32.exe, which of course, exists).
I don't think I have very much time left in my trial period,
but I've been trying to use a particular (short) tuturial,
which just happens to mention command-line compilation about
a third of the way through, so I tried it ... Thought at
first, might be intentionally missing along with .NET preview
tool, but that appears to be DccIL tool...
Have written to "Customer Service", who told me to call
"Sactuary Registration Team" toll-free number, who told
me to check and/or post to the newsgroup... Spent about
an hour browsing newsgroups to no avail so far, so ...
Here it is!
Thanks in advance if anyone feels like responding to a
"Trial" user! I've used various Borland tools starting
of course, with TurboPascal in the late 80's, when my
university switched most of the academic programming from
VAX/VMS to PC's...
Mike
Ignacio Vazquez
3f2a859b$3...@newsgroups.borland.com...
> In short: downloaded Delphi 7 Enterprise Trial, appears to be
> missing DCC32.exe command-line compiler...
Looks like it doesn't include it, which doesn't really seem like that huge a
deal, not because command-line compilation isn't important, but because the
trial is probably more to examine the IDE. Plus, it's probably more
difficult to lock down the command-line compiler than the IDE.
> Few more details: D7ET appears to work fine within IDE, but
> the command-line compiler executable (DCC32.EXE) appears to
> be missing entirely, even though there IS a DCC32.cfg file
> created on installation
Which is shared by the IDE.
> (as WELL as a DCC32.exe entry in the
> registry, same keys as Delphi32.exe,
> which of course, exists).
Hmm. Curious.
> I don't think I have very much time left in my trial period,
> but I've been trying to use a particular (short) tuturial,
> which just happens to mention command-line compilation about
> a third of the way through, so I tried it ... Thought at
> first, might be intentionally missing along with .NET preview
> tool, but that appears to be DccIL tool...
Actually, the .NET preview has the opposite problem: no IDE :)
Cheers,
Ignacio
--
Jesus is coming... EVERYONE LOOK BUSY!
Leo Saguisag (Borland)
> 3f2a859b$3...@newsgroups.borland.com...
> > In short: downloaded Delphi 7 Enterprise Trial, appears to be
> > missing DCC32.exe command-line compiler...
>
> Looks like it doesn't include it, which doesn't really seem like that huge
a
> deal, not because command-line compilation isn't important, but because
the
> trial is probably more to examine the IDE. Plus, it's probably more
> difficult to lock down the command-line compiler than the IDE.
You are correct, this was by design.
> > (as WELL as a DCC32.exe entry in the
> > registry, same keys as Delphi32.exe,
> > which of course, exists).
>
>
> Hmm. Curious.
We did not want to modify the installer logic any more than was necessary.
In this case, we did not see any harm in leaving this reference to dcc32.exe
in the registry so we did not bother to remove the installer logic that
creates this key in the first place.
-- Leo
Mike Dobson
>> "Mike Dobson" <MikeD...@Email.com> wrote in message
>> 3f2a859b$3...@newsgroups.borland.com...
>> > In short: downloaded Delphi 7 Enterprise Trial, appears to be
>> > missing DCC32.exe command-line compiler...
>>
>> Looks like it doesn't include it, which doesn't really seem like that huge
>a
>> deal, not because command-line compilation isn't important, but because
>the
>> trial is probably more to examine the IDE. Plus, it's probably more
>> difficult to lock down the command-line compiler than the IDE.
>
>You are correct, this was by design.
OK, so, no problem. Would be nice if this were mentioned
in the Release Notes/Readme ... The issue with the registry
(below) just further confuses the issue; maybe could have
just one more text file, specific to the "trial" package.
Maybe no one else doing a "trial" ever got past the IDE to
try command-line compilation (as I mentioned, I just tried
it because of a tutorial); not to mention, sometimes, it's
more convenient to go command-line, as this seems to be
the slowest loading IDE I've seen so far (although all of
the others on the same machine are either Micro$oft or IBM).