Using DDD with LessTif
DDD includes a number of hacks that make DDD run with LessTif, a free M*tif library without loss of functionality. Since a DDD binary may be dynamically bound and used with either an OSF/Motif or LessTif library, these lesstif hacks can be enabled and disabled at run time.
Whether the lesstif hacks are included at run-time depends on the setting of the lessTifVersion resource:
| lessTifVersion(class LessTifVersion) | Resource |
|---|---|
| Illegal HTML tag removed : x.y |
|---|
To set the lessTifVersion resource at DDD invocation and to specify the version number of the LessTif library, you can also use the option --lesstif-version Illegal HTML tag removed : version.
The default value of the lessTifVersion resource is derived from the LessTif library DDD was compiled against (or 1000 when compiled against OSF/Motif). Hence, you normally don't need to worry about the value of this resource. However, if you use a dynamically linked DDD binary with a library other than the one DDD was compiled against, you must specify the version number of the library using this resource. (Unfortunately, DDD cannot detect this at run-time.)
Here are a few scenarios to illustrate this scheme:
- Your DDD binary was compiled against OSF/Motif, but you use a LessTif 0.88 dynamic library instead. Invoke DDD with
--lesstif-version 88. - Your DDD binary was compiled against LessTif, but you use a OSF/Motif dynamic library instead. Invoke DDD with
--lesstif-version 1000. - Your DDD binary was compiled against LessTif 0.85, and you have upgraded to LessTif 0.90. Invoke DDD with
--lesstif-version 90.
To find out the LessTif or OSF/Motif version DDD was compiled against, invoke DDD with the --configuration option.
In the DDD source, LessTif-specific hacks are controlled by the string lesstif_version.
Node:Dirty Tricks, Next:Extending, Previous:Configuration Notes, Up:Top