Under specific build constraints, RCB menu options all become disabled
Given certain rare build constraints, all RCB menu options become disabled (grayed out) due to constraint checking. If this occurs, exiting the screen with constraint checking enabled is not possible. If you wish to go back to alter previous screens, first turn off constraint checking, move to the previous screen, and then re-enable constraint checking. This situation is triggered when building both the Internationalization library and any library that requires multi-threading, while simultaneously not building the Threads library.
Missing Top-Level Build Results HTML Page
Whenever you invoke RCB to build some set of libraries, there should be a build results HTML page at <buildspace>\records\results\index.html. However, this occurs only the first time you invoke RCB; for subsequent builds this file is missing. You can, however, find the same information by looking in the subdirectory for the buildtype of the build just performed. For example, the results for a 12d build would be found at <buildspace>\records\results\12d\index.html. (INF-2847).
LANG Environment Variable Setting on Solaris
When invoking the RCB GUI 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' on them may be generated as the user navigates through the RCB GUI pages. These boxes may obscure portions of the GUI. These boxes can be suppressed by unsetting the LANG variable or setting it to another locale (ie: C, POSIX, or en_US.ISO8859-1) (INF-4361)]
Unknown or Non-verified Publisher Message
On some Windows platforms, the User Access Control (UAC) dialog may indicate that the RCB executable is from an "Unknown" publisher, i.e. the publisher cannot be verified. You may also encounter this message when installing RCB on some Windows platforms. This message can be safely ignored.
UNC Path Incompatibility
On Windows, UNC (Universal Naming Convention) paths generally are exports provided by remote file servers. These paths take the form \\host\share\path. While it is possible to launch RCB from a UNC location, all paths specified in the buildspec must be located on paths identified using a drive letter.
There are three cases where the UNC path may cause problems:
You export the build and the local buildspace, the export buildspace, or both are UNC paths. The result is a fatal error referring to a file null. The stack trace in the RCB err.txt file will reference a java.io.IOException: Invalid argument thrown from java.io.WinNTFileSystem.
If you create a local buildspace, you can create the buildspec without issue, but the characterization process will fail. The resulting error message indicates that null is not recognized as an internal or external command, operable program or batch file.
If a third-party library uses a UNC path, RCB appears to handle these paths correctly. However, when RCB attempts to link generated libraries and examples against libraries located on UNC paths, the link operation reports undefined symbols.
Mapping the UNC paths and using the mapped drives' letter in your RCB build works around all three of these issues. (INF-4614)
Using EXCEED™ and UTF-8 encoded character sets
If using EXCEED™, Java™, GUI applications will not work with any UTF-8 character encoding, for example, en_US.UTF8. If RCB launches at all, fatal errors may occur. As a workaround, try using VNC™ with windowmaker window manager, or the console, instead of EXCEED™. Note: This problem has also been seen using the Gnome desktop environment. (INF-4716)
No spaces in #include path strings
RCB-generated makefiles do not put quotes around include path strings. If the path to the installation directory (local buildspace), export buildspace, or a user-provided third party library contains spaces, then compile failures will result. One way to prevent these failures is to ensure that the paths for the locations in question don't contain spaces. However, this may not be possible in some environments. If it isn't possible to remove all spaces from the paths, select the build action of "just generate makefiles" and then perform the build through RCB. Once RCB has generated the required makefiles, alter the makefiles to quote the path(s) which contain spaces, then execute the relevant makeall_<buildtype> script (located in the root of the buildspace) to perform your build manually. (INF-2215)
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.