Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/IDE/Code Editor    [ Add a report in this area ]  
Report #:  7384   Status: Reported
MS toolchain -- xstring gets scrapped
Project:  C++BuilderX/BC++ 2005 Build #:  103
Version:    1.0 Submitted By:   Roman Morokutti
Report Type:  Crash / Data loss / Total failure Date Reported:  2/24/2004 2:15:06 AM
Severity:    Critical / Show Stopper Last Updated:
Platform:    All versions Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
5.00 out of 5
Total Votes: None
Description
For some reasons, the compile fails when MS
toolchain is selected. I used the example from
Robert E. right out of the Code Central
repository. I followed the instructions of the compiler and altered xstring to add a semikolon at Line 1284. When I then pressed F9 the errors began at the beginning of xstring saying that the curly braces do not match. Fortunately I saw in the Windows Explorer that the original file was saved away with xstring~1~
and the file has grown to 59 kb, the original
file has about 23 kb. Somehow CBX scrapped the
file totally. I do not know why.
Steps to Reproduce:
See above
Workarounds
No.
Attachment
None
Comments

Robert Ehteshamzadeh at 3/16/2004 6:53:59 PM -
from

http://codecentral.borland.com/codecentral/ccweb.exe/getfile?id=20998&filename=README_VSDOTNET.TXT

1. Install Visual Studio.Net.
Be sure to check the "register environment variables" box at the end of the install.
This alters your default environment so that command line tools are on the path,
and also sets up the environment variables %INCLUDE% and %LIB% .

2. If this is successful, you should be able to run nmake.exe, cl.exe and link.exe from
a standard command prompt. ( i.e. open the run command dialog and enter cmd.exe )

3. After you've done this, install the Intel compiler.
If you want to install just the compiler, you can save some time by using setup.exe
in the Windows\c++_windows directory, rather than the general setup program.

4. If this is successful, you should be able to run icl.exe and xilink.exe from the command prompt.

do not proceed until you can successfully complete step 2.

Roman Morokutti at 4/23/2004 4:46:57 AM -
14088  2839689

Roman Morokutti at 4/30/2004 10:24:17 AM -
Hi,

as I refrehed my VSC++ implementation, another xstring came with it.
So with that one, it works fine now. But there is still the question, why
BCBX does scrap that file. If someone at Borland is interested in that
file I can post it when needed

Server Response from: ETNACODE01