Each SourcePro C++ release is a replacement for, not an upgrade to, the previous version. Always perform an installation into a new area, and not into the same install directory as a previous version.
Module dependency checks are not performed in the Installer. If you attempt a build with dependencies on uninstalled components, RCB displays a warning message.
There is no uninstaller for Windows or UNIX. To uninstall SourcePro, simply delete the installation directory. On Windows, no registry entries are made. On Windows, you may need to delete the desktop shortcut and the Start Menu group for SourcePro C++ 12.5.
In the Installer Product Selection dialog box, the scrollbar arrows are very slow. You can grab the scrollbar or click on the scrollbar area to rapidly move through the list.
The user needs to have administrator privileges to run the installer. If you don't have administrator privileges, the installer will complain when you choose an install location. A solution is to create a new directory, right-click it to bring up the Properties dialog, and choose the security tab, where you can give yourself full privileges for that directory. You can then install into this new location.
UNC installation paths not supported. For network installs on Windows, using a UNC path to specify the installation location is not supported. The problem is actually in RCB which, in such installs, is unable to create valid makefiles. So instead, create a mapped network drive to the desired network location. For the mapped network drive, be sure to check "Reconnect at Logon" checkbox. If this option is not selected, the mapped network drive will not appear when browsing for an install location.
On 64-bit machines, installer may fail to launch automatically. When inserting the 12.5 installer DVD into a Windows 64-bit machine, the installer may fail to launch automatically. To launch the installer manually, go to the root directory of the DVD and run setup.bat.
To run the installer or RCB on a UNIX system, the system must have the X11 graphical user interface system installed. It can also matter which window manager you use to run X11 because some window managers do not work well with the JVM used by the installer and RCB. Some problems can be worked around simply by resizing the installer or RCB window so the window is redrawn. Another option is to try a different window manager.
Here are some recommendations and known issues:
| Platform | Recommended window managers | Window managers with known problems | Type of problem |
| Solaris | Window Maker (8, 16, 24) kde (16) |
Twm | Missing check boxes and scroll bars |
| Linux Redhat and SUSE | Window Maker (16, 24) | Twm | Missing check boxes and scroll bars |
Solaris
UTF-8 locale results in erroneous text boxes that may obscure GUI. On Solaris, when invoking the installer with the LANG environment variable set to a UTF-8 locale (i.e. en_US.UTF-8), a series of small boxes with the word "iiimx" and/or "English/European" may be generated while navigating through the installer, possibly obscuring portions of the GUI. These boxes can be suppressed by unsetting the LANG variable or setting it to another locale (i.e. C, POSIX, en_US.ISO8859-1).
On Solaris 11, "\u" in the PS1 variable causes the installer to fail to launch. The workaround is to reset the PS1, and other PS variables, to something more simple:
export PS1=">"
This changes the prompt to appear as ">", and allows the installer to launch normally. (INF-5655)
AIX
Installer leaves behind an empty directory. This problem is caused by a bug (#IOA-000064318) in the software suite "InstallAnywhere" used to create the installer. The default temporary directory is created in /tmp with the name installer.dir.<process> where process is the process ID of the executing installer.
HP-UX
Installer may display incorrectly. With certain windows managers on HP_UX, the installer may not display the component selection screen correctly. Refreshing the screen using the previous and next buttons, or using a different windows manager, should resolve the issue. (INF-5654)
This section describes issues related to installing SourcePro C++ on a remote machine. Issues about installing on a particular platform are in addition to this discussion.
While there are various ways to connect from one machine to another, for remote installations we recommend using Virtual Network Connection (VNC). VNC is a common desktop sharing system that allows you to view a GUI on a remote computer. The remote machine runs a VNC server, and the local machine connects through a VNC client. There are many free VNC Server and Client versions on Operating Systems that SourcePro supports.
Do not forget to set the DISPLAY environment variable in your shell on the host where you are installing SourcePro. The DISPLAY variable should point to the VNC server and contain the port number used by your session. For example:
export DISPLAY=vnc-server.roguewave.com:3 |
On Windows, installing on another Windows machine should be a simple matter of using VNC to reach the remote machine and run the installer.
To install on a UNIX machine from Windows, you should also be able to use VNC to reach the remote UNIX machine and run the installer, assuming the UNIX machine has X11 installed.
If the UNIX machine you want to install onto does not have X11 installed, the likely scenario is:
Go to a UNIX machine that does have X11, either a desktop machine with a physical display or with VNC.
Connect to the machine you want to install onto using SSH or something similar.
Pipe the display on the target machine back to the machine with X11.
Run the installer normally on the target machine.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.