RE: FW: configure script "detection" logic for ( #define XPMATTRIBUTES_TYPE ) is NOT correct
I am in a quandary
If I make changes to the build-setup for IBM ( it may not work for older systems )
I may need to add some new detection code to identify that this is a newer system >>
X Window System programming considerations
z/OS V1R12.0 Communications Server IP Programmer's Guide and Reference
The X Window System toolkit includes files that define two macros for obtaining the offset of fields in an X Window System Toolkit structure, XtOffset, and XtOffsetOf. Programs written for, or ported to, z/OS UNIX MVS™ must use the XtOffsetOf macro for this purpose.
Some Motif widget and gadget resources have the type KeySym. In an ASCII-based system the KeySym is the same as the ASCII character value. For example, the character 'F' has the ASCII hexadecimal value 46 and the KeySym hexadecimal value 46.
However, on z/OS UNIX MVS, the character value of 'F' is hexadecimal C6, while the KeySym hexadecimal value is still 46. Remember to use true KeySym values when specifying resources of type KeySym, whether in a defaults file or in a function call.
In some cases, an X Window System server may have clients that are not running on z/OS UNIX MVS. If a z/OS UNIX MVS X Window System application sends nonstandard properties that contain text strings to the X Window System server, and these properties might be accessed by clients that are not running on z/OS UNIX MVS, the strings should be translated. The translation should be to the server default character set before transmission to the server and to the appropriate host character set when retrieved from the server. This translation is an application responsibility.
The z/OS UNIX c89 or make commands should be used to compile and link X Window System and Motif programs. The following example shows how to use the c89 command to compile an X Window System program, xxx, which uses the Athena widget set, and create the executable file xxx. All code that uses the X Window System and Motif libraries must be compiled with the DLL option even if static linking is used.
c89 -o xxx -Wc,dll,xplink -Wl,xplink xxx.c /usr/lib/Xaw_31.x /usr/lib/SM_31.x
The following example shows how to compile the program xxx for use with the 64-bit DLLs. LP64 also requires the use of XPLINK.
c89 -o xxx -Wc,dll,xplink,LP64 -Wl,xplink xxx.c /usr/lib/Xaw_64.x /usr/lib/SM_64.x
The following example shows how to use the c89 command to compile an X Window System program, yyy, which uses the Motif widget set, and create an executable file yyy:
c89 -o yyy -Wc,dll,xplink -W1,xplink yyy.c /usr/lib/Xm_31.x /usr/lib/SM_31.x
The following example shows how to use the c89 command to compile an X Window System program, yyy, which uses the Motif widget set, and create an executable file yyy. This example links with the previous function libraries (X 6.1 and Motif 1.2). You must explicitly tell the compiler where to pick up the header files for the previous function libraries with the -I option.
c89 -o yyy -Wc,dll -W1,xplink yyy.c -I/usr/include/lpp/tcpip/X11R6/include
/usr/lib/Xm.x /usr/lib/SM.x /usr/lib/ICE.x /usr/lib/X11.x
For examples of the input to the make command, see the Makefile in each of these subdirectories:
From: Bram@... [mailto:Bram@...]
Sent: Saturday, April 28, 2012 4:33 AM
To: Bovy, Stephen
Subject: Re: FW: configure script "detection" logic for ( #define XPMATTRIBUTES_TYPE ) is NOT correct
Stephen Bovy wrote:
> The xpm attribute type should not be declared if the xpm header or
> xmp linker detection fails >>
> /* #undef HAVE_X11_XPM_H */
> The following should NOT have been set
> /* Define to the type of the XpmAttributes type. */ #define
> XPMATTRIBUTES_TYPE XpmAttributes
> cc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MOTIF -O -D_ALL_SOURCE -Wc,float\(IEEE\),HALTONMSG\(3296\) -W c,dll -o objects/gui_xmebw.o gui_xmebw.c
> WARNING CCN3296 ./gui_xmebw.c:38 #include file <X11/xpm.h> not found.
> ERROR CCN3275 ./gui_xmebw.c:291 Unexpected text attr encountered.
> ERROR CCN3045 ./gui_xmebw.c:291 Undeclared identifier XpmAttributes.
So what #ifdef needs to change then?
ROBIN: (warily) And if you get a question wrong?
ARTHUR: You are cast into the Gorge of Eternal Peril.
ROBIN: Oh ... wacho!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php