C++BuilderX 1.0 下载完毕!!!

耙子 2003-09-12 12:47:43
可以安装在 Windows XP/2000、unix、Solaris 8 (没提到 windows 9x系列)

包含了IB 7.1,dbExpress, Corba,Noika等的移动开发平台,intel的C++编译器(年初吵得沸沸扬扬的,说这个编译器提供了多p4的最大支持)
readme 内容如下

C++BuilderX™ Release Notes


Table of Contents

Release Notes
Supported Platforms
Other Release Notes
Mobile Development
Intel® Tools
Known Issues
Mobile Development
This file contains important supplementary and late-breaking information that may not appear in the main product documentation. We recommend that you read this file in its entirety. Some features mentioned in this document are not included in all versions of C++BuilderX.

Release Notes
Supported Platforms
While C++BuilderX may install on a wider range of platforms, this release officially supports the following operating systems:

Windows 2000
Windows XP
RedHat Linux Enterprise Workstation 2.1
Solaris 8

Other Release Notes
Other documentation provided with this release includes the following files:

deploy.html contains information about redistributing your applications.
license.html contains information on licensing allowances and limitations for this product and other Borland software that is bundled with it.
Please refer to these documents for your rights and restrictions for this release. They are available in HTML format in the main directory of your C++BuilderX installation.

This release includes the following dbExpress drivers:

InterBase 6.5 client/server (Linux, Windows, Solaris)
DB2 v. 7.2 client/server (Linux, Windows)
Informix 9.21 client/server (Linux, Windows)
Informix SE 7.2 server (Informix 9.21 client) (Linux, Windows)
MySQL 3.23.49 client/server (Linux, Windows)
MSSQL 2000 client/server (Windows only)
MSSQL 7 server (MSSQL 2000 client) (Windows only)
Oracle 9.0.1 client/server (Linux/Windows)
PostreSQL 7.2 (Linux only)
Compiling the dbExpress sample application on Solaris requires the Forte toolset.

Mobile Development
Mobile (Symbian OS) development is supported only on Windows platforms. Although the wizards, project management and code editing features are available on all platforms, the Symbian SDKs are only available for Windows. Please see the Known Issues section below for more information.
For more information regarding the installation of the Mobile SDKs CD, please see the install.html file in the root directory of the Mobile SDKs CD.

Intel® Tools
For information on installing and registering the Intel® tools please see the install.html file in the root directory of the Intel Software Development Products CD or the install_Intel.html file in the root directory of the C++BuilderX core product CD.

Known Issues
The following are known issues with the C++BuilderX product for this release:

Borland Enterprise Server 5.2, VisiBroker Edition is required to use the VisiBroker wizards to generate a client or server. For each supported platform, BES 5.2 VE supports only a single toolchain:
Windows: Borland C++ compiler
Linux: GNU compiler
Solaris: Sun Forte for C++ compiler
When using the wizards to create your CORBA application, make sure you select the correct toolchain for your platform.
If your IDL files use the following syntax:
interface intf

then the VisiBroker Server Wizard will not properly detect your interfaces. It is necessary to use this syntax:

interface intf {

If your IDL file includes another IDL file which contains additional interfaces, the VisiBroker Server and Client wizards will not automatically compile the included IDL file. After the wizard has completed, you should run the idl2cpp compiler manually on the included IDL file. Refer to the Borland Enterprise Server 5.2, VisiBroker Edition documentation for instructions on running the idl2cpp compiler.
If you run the VisiBroker Server wizard multiple times to add additional interfaces to your project, you will need to manually add a "#include" line to main.cpp for each different implementation header.
When using the VisiBroker Client and Server wizards, the client and server applications cannot exist in the same directory.
When using the VisiBroker Client and Server wizards, there cannot be a space within the pathname of the IDL file.
By default, CORBA applications are compiled using the _DEBUG define. To disable this, open the Build Options Explorer and remove this setting.
In the Corba Server Wizard, most users will want to set the Lifespan to PERSISTENT in Step 3 of 4 (the default is TRANSIENT).
If you do not choose the correct toolchain, your project will not be set to build with the correct options. You can use the Project Properties dialog and the Build Options Explorer to set the properties. The following procedures explain how to set the properties for Windows, Linux, and Solaris.

Use the Project Properties dialog to set the active toolchain to the Borland C++ Compiler.
Using the Target Settings wizard, select Multi-threaded console project build settings.
Add the following settings to your project using the Build Options Explorer:
- Add these conditional defines: _RTLDLL
- Add $(VBROKER)\include to your include search path.
- Add $(VBROKER)\lib to your library search path
- Add c0x32.obj to the Object files setting (this should be the first object linked into your project)

Use the Project Properties dialog to set the active toolchain to GNU C++.
Add the following settings using the Build Options Explorer:
GNU C++ compiler:
- Add these conditional defines: conditional defines: _REENTRANT, THREAD and PTHREADS
- Add $(VBROKER)/include to your include search path.
GNU C++ linker:
- Add these libraries to the Library files setting: -lcosev_r, -lcosnm_r, -lvport_r, -lorb_r and -lpthread
- Add $(VBROKER)/lib to your library search path

263 点赞 收藏 37
37 条回复
cx_super 2003-09-21
szcoder 2003-09-16
1.0没啥意义,官方文档上写preview for new framework。
tccsdn 2003-09-16


longsong 2003-09-16
jishiping 2003-09-16
今天打开电脑,收取EMail,收到Borland的EMail,通知C++BuilderX 1.0已经正式发布了。
ArWen 2003-09-16
C++BuilderX 1.0是个啥东西?
iiprogram 2003-09-16
Dear Tomahawk field tester,

Thank you for you interest in Tomahawk, and for downloading and installing the product.

Today, September 15, 2003 Borland launched C++BuilderX, the commercial release of Tomahawk. The full product release includes multiple compilation toolset support and multiple platform support.

C++BuilderX includes rich Application Lifecycle Management (ALM) support, including tool integrations for the StarTeam defect tracking and code management tool, CaliberRM for requirements management and Together for round-trip C++ UML modeling. This release also included a technology preview of our ANSI-compliant C++ compiler, Visual Development Designer and C++ Application Framework.

If you reported a defect via QualityCentral during the field test Borland will ship you a fully licensed copy of C++BuilderX. Please make sure your BDN account has your correct shipping information, you can login and check your account details here: http://bdn.borland.com.

Borland will provide update releases of both the core product and the technology preview over the upcoming months. Be sure to check out the product homepage at http://www.borland.com/cbuilderx for details and updates.
耙子 2003-09-15
hy1080 2003-09-15
goldflute 2003-09-15
Borland已经可以下载了,不过是Mobile SDKs
nyucv 2003-09-14
WIN 2003安装不成吗????????
leejd 2003-09-14
alenwelkin 2003-09-14
sun_wyz 2003-09-14

diaodou 2003-09-14
耙子 2003-09-12

耙子 2003-09-12
When using a Japanese OS, the cursor will stop in the middle of a character for bold and italic attributes. To correct the problem add the following line to CBuilderX/bin/cbuilder.config file:
vmparam -Dprimetime.editor.useVariableWidthFont=true
Once you have added this, remove the users.properties file in the .cbuilder1 directory within your home directory.
For some localized versions of Windows, the Symbian makesis command will fail if your username contains other than low-ascii characters.
Mobile Development
Using the New Symbian DLL wizard or New Symbian GUI Application wizard to add targets to an existing project that does not conform to the standard Symbian directory structure will fail. The standard Symbian directory structure for a project is:
<project root>
Where the project bld.inf and target mmp files are stored in the group subdirectory. If your project does not follow this structure, the New Symbian DLL wizard and New Symbian GUI Application wizard will create mmp and source files in the wrong location. The workaround is to move the created files to the desired location after the wizard has completed.
When using the Series 60 SDK 0.9, Nokia Edition (Metrowerks format), some of the Nokia sample applications may not build. This is because the Metrowerks version of the Series 60 0.9 SDK are missing the WINSCW platform under the PRJ_PLATFORMS keyword. To fix this, add WINSCW to the PRJ_PLATFORMS list. Then, perform a Save All and rebuild the application.
Missing lib files for ARMI/Debug. Copy EDLL.LIB, EDLLSTUB.LIB, EEXE.LIB and EGCC.LIB from epoc32\release\armi\urel to epoc32\release\armi\udeb.
The Metrowerks toolchain requires at least one exported symbol (function or method) in a library to compile. If you attempt to build after you add a DLL using the wizard and before you add a function or method, the build will fail.
When building ARMI applications using Bluetooth as the deployment method, verify that gdbstub on the phone and the Connection Manager on the PC are running prior to starting the build. These must be running in order to deploy in this manner. If you decide to use this method to deploy, this method may result in silent failures (from gdb.exe provided by Symbian) if gdbstub does not successfully establish a connection to the PC. If gdbStub is successful in establishing a connection to the PC, you should see a serial connection in the Connection Manager once gdbstub has started. Due to these silent failures, even when there is no connection between gdbstub and the Connection Manager the progress dialog box indicating that the program is "Copying files to device" will seem successful; however, the transfer will have actually failed.
Some of the examples mentioned in the Nokia SDK documentation are not included with the product. Some of the examples that are included are installed read-only by default and will cause an error when you attempt to build. Before attempting to build these examples, you will need to remove the read-only setting from these files. The following files are read-only:
Bluetooth HCI example
Cipher example
ErrorUI example
MultiViews example
Hello world example
Hello world plus example
Sound example
The C++BuilderX installation CD includes zip archives of the full source code for products licensed under the GNU General Public License that are distributed with this release. Please see the \ent\MinGW_GPL_dist directory on your product CD.
When using printf and scanf, the output pane of C++BuilderX does not show any print statements before the scan statement. However, cout and cin display as expected. This is true of all toolsets.
On Windows, attempting to select a root directory on the mounted drive (for example, c:\) before entering the Name value of any New Application wizard dialog causes a NullPointerException. Therefore, you cannot create a new project in the root of the mounted drive.
C++BuilderX may hang or crash on Windows XP when using an ATI Radeon video driver. This often occurs after a screen saver appears. To work around this issue, uncomment the following lines in the jdk.config file in the bin directory of your C++BuilderX installation:
vmparam -Dsun.java2d.noddraw=true
vmparam -Dsun.java2d.d3d=false
For this release, exported makefiles are not compatible with Cygwin's Make.


Copyright© 2003 Borland Software Corp.
All right reserved.
耙子 2003-09-12
Use the Project Properties dialog to set the active toolchain to Sun Forte C++.
Add the following settings using the Build Options Explorer:
CC compiler:
- Add these conditional defines: conditional defines: THREAD and SOLARIS
- Add the multithreaded compiler option (-mt)
- Add $(VBROKER)/include to your include search path.
CC linker:
- Set the multithreaded compiler option (-mt)
- Add these libraries to the Library files setting: -lcosev_r, -lcosnm_r, -lvport_r, -lorb_r and -lpthread,
-lsocket, -lnsl, -ldl, and -lposix4
- Add $ (VBROKER)/lib to your library search path

GCC compatibility issues are possible on newer versions of RedHat. Problems have been reported using GCC version 3.32 (Default on RedHat 8 and 9). Compiling the default project with this GCC version may produce errors such as:
"main.cpp": `cout' undeclared in namespace `std' at line 7
To work around this issue, deactivate the include path option (-I) in the compiler, or revert to GCC version 2.95.
Header dependencies are not properly tracked. In this release, you must perform a Build All if a header changes.
On Windows, the linker option -aa is not turned on by default for 32-bit Windows applications. Please go to the Build Options Explorer to turn this option on.
In the Build Options Explorer, options that the tool chain enable by default are shown as having a mark in the related checkbox. Since these are the default behavior of the tool, no corresponding option appears on the command line.
On Windows, when working on a project from an exported makefile, a "make clean" may not remove files if C++BuilderX has been launched from a non standard command shell. To make sure this does not happen, launch C++BuilderX from a cmd.exe shell. This only applies to makefile projects. All other kinds of projects are unaffected.
If you are using C++BuilderX with MSVS.NET as the active tool chain, be sure to set your environment variables by running the vcvars32.bat script installed by Visual Studio.
Environment variables that an exported makefile relies on need to be set to the correct value before executing. The BCBX environment variable, if not set already, will be set from the IDE to the C++BuilderX installation directory.
Because the C++BuilderX Windows product install calls other third-party installers, the Path environment variable on Windows systems can be stretched to its maximum length. If stretched beyond its maximum length, you may find that essential build tools (like compilers and linkers) are inaccessible in C++BuilderX.
If you have problems with inaccessible build tools after installation, check to see if the Path is stretched beyond its maximum length. To do this:

Go to the System icon in the Control Panel.
On the Advanced tab, select the Environment Variables button.
Examine the contents of Path in both the User and System Variables panes. If the value cuts off prematurely, try to remove unnecessary or repeated directories. You can then add back directories containing your missing build tools.
If the user does not have write permissions to the GDB debugger, the IDE presents an error of "The file system containing this file is read-only." Make sure you have a version of GDB for which you have write permissions selected.
In some cases, debugging on Windows with GDB will fail with the GDB error 193, which appears on the status bar of the debugger toolbar. This is related to long file names with embedded spaces. For example, if your project file is saved in the "C:\Documents and Settings" directory, such as "C:\Documents and Settings\User\ConsoleApp1.cbx," and you happen to have a file called "C:\Documents" or "C:\Documents and," the IDE can't debug the project using the GDB debugger. The solution is to either remove the "C:\Documents" or "C:\Documents and" file or to save your project files in another directory.
For debugging with GDB on Linux and Solaris, and DBX on Solaris, make sure the LD_LIBRARY_PATH environment variable is properly configured on your system.
To debug using Microsoft tools you must first download the Microsoft debugger, CDB. To download this tool, go to http://www.microsoft.com/whdc/ddk/debugging/default.mspx.
When debugging a console application in C++BuilderX on a Solaris machine remotely (having exported your display to a local machine), a console window will not come up when debugging the application.
When debugging with the Solaris DBX debugger, the assembly pane of the CPU view will not show source code intermixed with the assembly code. Instead it will only show assembly code. The context menu option "Toggle Mixed" has no effect.
GDB has problems setting breakpoints in DLLs and Shared Objects that are statically or dynamically linked to the main executable and loaded at run time. To set breakpoints in a DLL or Shared Object that is loaded at run time, debug the main executable and stop the debug session right after the DLL or Shared Object is loaded. Once the DLL or Shared Object is loaded, source files of the DLL or Shared Object can be opened and breakpoints can be set. For statically linked DLL's and Shared Objects, stop at function 'main' (start the debug session with F8). After this, breakpoints can be set in the DLL or Shared Object. For dynamically linked DLL's and Shared Objects, debug and stop at a breakpoint right after the DLL or Shared Object is programmatically loaded, after this, breakpoints can be set in the DLL or Shared Object.
The MingW compiler installed by C++BuilderX for Windows users is not internationalized. The compiler can not compile the source file when multibyte characters are used as a string literal. Wide character literals are not compiled correctly when the characters set of the source file is not ISO8859_1.
To display German or French compiler messages on the message pane when using the Microsoft compiler, add the following parameter in cbuilder.config.
vmparam -Dprimetime.runtime.io.encoding=Cp850

woainihaha 2003-09-12



C++ Builder 茶馆
2003-09-12 12:47