Cleanscape Lint GUI General Support FAQ

 

Q:   My Flint GUI fonts look terrible!

 A:  Earlier versions of Linux included more standard families of fonts; to reach the lowest common denominator of font availability, Cleanscape
opted for font-families like Helvetica, Times, or Courier. However, many of these families simply don’t exist now, and what you end up with
is probably the worst available font: Fixed.

The Cleanscape GUIs allow the user to specify their font choices. This is done in an initialization file, which is named
-
%FLINTHOME%\flint.ini on Windows
-
$HOME/.flint.ini on Linux (note prefixed ‘.’)

       Edit the [Fonts] section of that file to specify your desired font(s) (replacing “Default”), then restart the GUI. The format of an input line is
font-family size style
If the font family contains spaces, enclose the entire family name in curly brackets. “style” is one of: normal, italic, bold, underline, etc.

Example entries for the flint.ini file:
tab text     = {Palatino Linotype} 10 italic
menu items   = utopia 8 normal

      Since the reports provide visual cues, we recommend a monospaced font to keep things in alignment.
We recommend size 8 for buttons and tab labels, and size 10 for everything else. Try different sizes!
For CentOS and Redhat, we recommend the liberation font family: {liberation sans} or {liberation mono}

Q:   But what fonts are available?
A:   Copy this small file to a file named
availablefonts. It’s important to use the version of perl provided by Cleanscape; adjust the
      shebang as necessary. Chmod it to 755 and run it.

      To see which fonts look nicest on your screen, copy and paste the program from the bottom of this page, from O’Reilly’s Mastering Perl/Tk.
      Add the shebang from the previous file as line 1, chmod it to 755, and run it. An encapsulated version that sets the library directories is here.
   

Q:   We are having problems running the Cleanscape Lint GUI. The following message appears in a dialog box, then the GUI quits:

Fatal Error

Error: Display dimensions are too small.

Presently, we need 1024x768 or above.

A:   The GUI needs a certain amount of screen real estate and was created under the assumption that most people use a resolution of 1024x768 or larger.  Please adjust your screen resolution to that minimum setting.


       This particular customer was using Hummingbird Xwindowing software, and even though both the Windows and Linux machines were set to 1024x768, the actual size available to programs was 712 pixels in the vertical dimension.  We believe this was due to Hummingbird creating a horizontal toolbar.  If you set your Hummingbird session to “full screen”, this problem is handled.


      If you’d like to see the dimensions being reported to your Cleanscape session, copy this small file to a file named “scrsize”, and run it on your machine, adjusting the first line as necessary.

 

Q:  I note the GUI is perl/Tk and we already have that installed, but I am getting error messages and the GUI is not starting.

A:   To ensure compatibility across numerous hosts, Cleanscape requires version control.  Therefore, the Cleanscape distribution contains all files necessary to run the GUI, including a perl binary and hundreds of .pm modules.  Occasionally, there are problems starting the GUI and in almost all instances it has to do with version mismatches because the GUI for some reason is not accessing the perl binary or .pm files coming from the distro.  Here are some things to try:


·         If you are running on a 64-bit architecture, ensure that you have 32-bit (i686) installations of glibc and libX11.  For example, in RHEL, run the following as root:

There could be other missing i686 libraries; check the error messages from the GUI for clues or email [email protected].


·         Install as root, if possible.

·         If you are running in a client/server environment, test on the server first.

·         Verify FLINTHOST, FLINTHOME, CSIAPPBASE, and PATH are set accordingly as per the installation instructions.  For C++lint and Lint-Plus, the first two environment variables are named CSIHOST and IPTLINT, respectively.

·         Confirm that you are running the correct version of perl and Tk (the ones from our distro).  To do so, download this ZIPfile, extract to $HOME, chmod script file testtk to 755, and run it.  It will display information about the environment, then start a couple test UIs on your screen. NOTE: The script assumes you’ve set CSIAPPBASE as mentioned earlier.

 

You can check out other FAQs related to Cleanscape static analyzers by clicking here.

      

CLEANSCAPE SUPPORT CONTACT INFO

[email protected]

800-944-5468 (aka 800-94-4LINT)

706-245-1070 (Sales/Service office direct)