source: trunk/third/motif/README-1.2.3 @ 12415

Revision 12415, 12.0 KB checked in by ghudson, 26 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r12414, which included commits to RCS files with non-trunk default branches.
Line 
1NOTE: OSF/MOTIF IS LICENSED SOFTWARE.  SOURCE AND OBJECT CODE IS NOT
2TO BE DISTRIBUTED TO THIRD PARTIES EXCEPT AS PROVIDED BY THE TERMS OF
3YOUR LICENSE AGREEMENT.  PASSIVE DISTRIBUTION TO UNIDENTIFIED PARTIES,
4SUCH AS MAKING FILES AVAILABLE FOR UNRESTRICTED ELECTRONIC FILE
5TRANSFER, IS STRICTLY PROHIBITED BY THE LICENSE.
6
7THESE RESTRICTIONS APPLY TO ANY PARTY TO WHOM THE SOFTWARE HAS BEEN
8DISTRIBUTED.
9
10The Purpose of This Release
11
12        This patch release contains approximately 425 bug fixes for
13        Motif 1.2.
14
15        The reference platforms for Motif 1.2.3 are the HP 9000/720
16        running HP-UX 9.01 and an Intel 486 workstation running OSF/1
17        1.2.
18
19        OSF encourages the reporting of all bugs found in OSF/Motif
20        regardless of the platform or hardware configuration in which
21        the bug is found.  However, OSF will commit to accept (and
22        repair according to priority) only those bugs that can be
23        replicated on the current reference configurations.  A list of
24        known bugs can be found in the OPENBUGS file and a list of
25        bugs fixed in this release can be found in the FIXEDBUGS file,
26        both on the release tape.
27
28        Since this is a general availability product release, it has
29        undergone the full quality assurance cycle at OSF.
30
31
32Installing This Release
33
34        OSF/Motif 1.2.3 is provided on magnetic tape, in tar format.
35
36        This release is made up of a "sparse tree" of files that have
37        changed since patch release 1.2.2. The new versions of the
38        files should replace the corresponding Motif 1.2.2 versions of
39        the files in your source tree, and then the Makefiles and then
40        the binaries should be rebuilt.
41
42        Before you install this release, you must have installed patch
43        releases 1.2.1 and 1.2.2.  If you received releases 1.2.1
44        through 1.2.3 combined on a single tape, and followed the
45        installation instructions, you will have installed all three
46        releases in the right order.
47
48        To install the entire contents of the tape, create the
49        directory that you want to be the root for the sources, make
50        that the current directory, load the tape into the tape drive,
51        and issue this command:
52
53                tar xvf device_name
54
55        After the tape is unloaded, you can use, for example, cp -f
56        command to copy the sources from the current directory into
57        your source tree.
58
59        This release creates four new files: ./README-1.2.3, ./bindings/pc,
60        ./lib/Mrm/MrmIswap.c and ./lib/Xm/sharedlib.c.  If you are
61        using a symbolic link tree, you will need to create new links
62        for them. Also ./lib/Xm/LabelDIcoI.h and ./lib/Xm/ListDIconI.h
63        files were defuncted; you may wish to remove these files from the
64        source tree.
65       
66        If you have any problems when installing the tape, call the
67        OSF/Motif support desk at (617) 621-8990.
68
69
70Summary of Changes in this Release
71
72        All changes made in this release are fixes for reported bugs.
73        For details on the bugs fixed, see the file CLOSEDBUGS on this
74        tape.
75
76
77Bug Lists
78
79        On the tape there are two files, OPENBUGS and CLOSEDBUGS,
80        which contain, respectively, the list of all bugs from any
81        version of Motif not yet closed, and all bugs from any version
82        of Motif fixed in the 1.2.3 release.
83
84
85Overview of the Motif Directory Structure
86
87        This section describes the Motif directory structure.
88
89        This file, ./README-1.2.3, summarizes the contents of the top
90        level directories in the directory structure, briefly
91        describes the build process, and describes bug reporting
92        procedures.
93
94        The file ./BUGREPORT is a bug report template.
95
96        The file ./OPENBUGS contains all open bugs.
97
98        The file ./CLOSEDBUGS contains all bugs fixed in this
99        release.
100
101        The directory ./X11R5 contains official MIT patches for
102        Version 11 of the X Window System.  The patches to the Xlib
103        and the X Toolkit Intrinsics are required for building and
104        running Motif 1.2.3.  The file ./X11R5/README describes the
105        patches and how to apply them to your X sources.  For more
106        information, refer to the section "Building Motif On Your
107        System."
108
109        Note:  MIT, not OSF, is responsible for support
110               of any patches in the ./X11R5 directory.
111               We provide them unsupported for the
112               convenience of users who might not yet
113               have received the latest sources.
114
115        The directory ./doc contains the full sources for the Motif
116        documentation.  No updates for documentation are provided in
117        this release.
118
119        The directory ./lib contains the toolkit library and resource
120        manager library:
121
122           * ./lib/Xm contains the Motif widget library.
123
124           * ./lib/Mrm contains the Motif resource manager
125             library used with the uil compiler.
126
127        The directory ./bindings contains vendor-specific bindings for
128        virtual keysyms.  For more information on virtual bindings,
129        see the file ./bindings/README or the VirtualBindings(3X)
130        manual page in the OSF/Motif Programmer's Reference.
131
132        The directory ./clients contains the Motif window manager, the
133        User Interface Language (uil) compiler, and the xmbind client:
134
135           * ./clients/uil contains the uil compiler and the
136             callable uil interface library (libUil.a).
137
138           * ./clients/mwm contains the Motif window manager.
139
140           * ./clients/xmbind contains a client used to set up
141             the bindings between keys on the keyboard and Motif
142             virtual keys.
143
144        The directory ./demos is an unsupported directory.
145
146        The directory ./tools contains a single tools subdirectory,
147        wml, with the Widget Meta-Language (WML) facility.
148
149        The directory ./config contains configuration files.
150
151        The directory ./tests contains regression tests.  No updates
152        for tests are provided in this release.
153
154
155Where to Get Help
156
157        To report problems with this release, please complete the OSF
158        Problem Report in the file ./BUGREPORT and mail to:
159
160          motif-defect@osf.org or uunet!osf.org!motif-defect
161
162        motif-defect is an alias to a person at OSF who is in charge
163        of receiving and dispatching bugs reported against the latest
164        released version of OSF/Motif.
165
166        Discussions concerning the technology in this release can be
167        directed to the mailing list:
168
169          motif-talk@osf.org or uunet!osf.org!motif-talk
170
171        If you want to be added to the motif-talk mailing list, please
172        send your email address to:
173
174          motif-talk-request@osf.org or uunet!osf.org!motif-talk-request
175
176        Please include your company name and Motif license agreement
177        number.
178
179        Licenses with full support contracts can also call OSF for
180        help.  The service number is 1-617-621-8990, and support is
181        available between 8:30 AM and 5:00 PM United States Eastern
182        time, Monday through Friday.  You can obtain an OSF/Motif
183        software support contract for support of released versions of
184        OSF/Motif by contacting OSF Direct Channels at 1-617-621-7300.
185
186
187Building Motif for Your System
188
189        This release requires no changes in the build process.  Please
190        refer to the Release Notes, Chapter 6, or the section
191        "Building Motif for Your System" in the README-1.2.1 file, for
192        more information.
193
194        Be sure to read the section "Tailoring the Build Process" for
195        information on how to configure your system before building
196        Motif.  This section includes instructions for patching your
197        X11R5 sources.  The section "Motif Makefiles" describes the
198        steps you should follow to build the source, including
199        building the Makefiles, after you have tailored your build
200        configuration.  The section "The Motif Build Tree" indicates
201        how the build proceeds once it has begun.
202
203        Motif 1.2.3 uses X11R5 Xlib and X Toolkit Intrinsics
204        libraries.  The versions of these libraries used to build
205        Motif must have the MIT fixes 1-25, supplied in the ./X11R5
206        directory, applied to them in order for Motif to build and run
207        properly.  Please read the README in that directory for more
208        discussion of the patches.
209
210
211Readiness for Certification
212
213        The Motif Validation Test Suite (VTS 1.1) was run and passed
214        on the following configurations:
215
216           * Intel 486 running OSF/1 1.2, MIT R5 server
217
218           * HP 9000/720 running HP-UX 9.01, R5 server
219
220           * SPARCstation 2 running SunOS 4.1.2, R4 server
221
222
223Making Client Makefiles with imake
224
225        This section contains new information, written in response to
226        several questions from licenses.
227
228        Clients in the X11R5 release use the xmkmf command to build
229        Makefiles.  This command executes imake, and usually sets the
230        UseInstalled imake variable appropriately.
231
232        Motif uses the UseInstalled flag, and also uses the
233        UseInstalledMotif flag independently.  Thus, in general, the
234        xmkmf command cannot be used for Motif clients, because of the
235        need to consider the UseInstalledMotif flag separately.  Since
236        xmkmf is a simple script that calls imake, it is easy to
237        construct the proper call to imake using the following rules.
238
239        In these instructions, replace {MTOP} by the toplevel
240        directory with the Motif source tree, and {XTOP} by the
241        toplevel ("mit") directory with the X source.  If imake has
242        been installed, it is assumed that the directory containing it
243        is in your PATH, and {CONFDIR} is the X configuration
244        directory (usually /usr/lib/X11/config).
245
246        When needed, the imake variables XTop and MTop are normally
247        set in your site.def (to {XTOP} and {MTOP} respectively);
248        however they may also be set with additional -D arguments to
249        imake.
250
251        1. With both X and Motif in their source trees, ensure the
252        imake variables XTop and MTop are set, and use:
253
254            ${XTOP}/config/imake -I{MTOP}/config
255
256        2. With Motif in its source tree, and X installed, ensure MTop
257        is set, and use: 
258
259            imake -I{MTOP}/config -DUseInstalled
260
261        3. With both Motif and X installed, use:
262
263            imake -I{CONFDIR} -DUseInstalled -DUseInstalledMotif
264
265        The configuration files currently are not designed to work
266        with Motif installed and X in its source tree.
267
268        Here is a simple Imakefile, for a single client in its own
269        directory:
270
271            LOCAL_LIBRARIES = XmClientLibs
272                    DEPLIBS = XmClientDepLibs
273                       SRCS = client.c
274                       OBJS = client.o
275
276            MSimpleProgramTarget(client)
277            InstallProgram(client,$(BINDIR))
278            DependTarget()
279
280        Or, for a client that uses uil/mrm, replace the library
281        definitions by MrmClientLibs and MrmClientDepLibs, and also
282        use:
283
284            MSimpleUilTarget(client)
285
286        to build the client and uid file.  Look in the "demos"
287        directory for more examples.
288
289
290Configuration Variable Changes
291
292        Changes have been made to the variables used by imake since
293        Motif 1.2, and some of them may affect users' Imakefiles.
294
295        If the imake variable "DontBuildMotifDemos" is defined, the
296        Motif demos are not built or rebuilt.  You must remake the
297        toplevel Makefile for this to come into effect.
298
299        The imake variable UilFlags contains site-specific flags for
300        the uil compiler.  This becomes the make variable UILFLAGS.
301        The make variable LOCAL_UILFLAGS (and LOCAL_UILFLAGS_1, etc)
302        can also be used in Imakefiles.
303
304        The make variable UIL_INCLUDES now correctly names the
305        standard directory for uil include files.  Command lines that
306        execute the uil compiler will have a -I option added referring
307        to this. MSimpleUidLocaleTarget rule was created.
308
309        Several changes were done to better support shared libraries.
310
311        We have rewritten the hp.cf file, introducing several new
312        imake variables.  Please read the file for details.
313
314
315Note regarding Xt translations fix in patch 25 to X11R5
316
317
318        Due to a bug fix in the Xt translation code (patch 25 to X11R5),
319        the translations in Xt are now very strictly handled, instead
320        of accepting any possible match. Because of this, in certain
321        platforms, QATS and the Motif VTS are not behaving as they did
322        in the past. This is due to incorrect assumptions made in the
323        translations for certain keyboards, for example, in those keyboards
324        in which the arrow keys are defined in the keypad. We believe that
325        this change will also influence additional Motif applications.
326
327        A quick solution to this problem consists of creating a file
328        that is passed to the utility xmodmap and that redefines the
329        bindings for the keys in question. The following is an example of
330        what the file might look like:
331
332!
333! Always force:
334!   KP_2 = Down
335!   KP_8 = Up
336!   KP_4 = Left
337!   KP_6 = Right
338!
339keycode 120 = Down
340keycode 76 = Up
341keycode 98 = Left
342keycode 100 = Right
343
344        This file changes the bindings for the keypad keys that match the
345        arrow keys so that only the arrow keys and not the keypad numbers
346        are produced. This allows the application to use modifiers with the
347        arrow keys.
348
Note: See TracBrowser for help on using the repository browser.