Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Error while installing libXdevel, package cannot be found Ask Question. Asked 9 years, 7 months ago. Active 6 years, 2 months ago. Viewed 11k times. Done Building dependency tree Reading state information Done E: Unable to locate package libXdevel But it seems that the package does not exist.
Improve this question. Bruno Pereira One: you don't need synaptic for that. You have to resolve the dependency on the system where you are building your package. This means you need to have those dependencies installed, inclusing libXdevel.
Here are some detail. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Linux Installation libXdevel Ask Question. Asked 3 years, 2 months ago. Active 3 years, 2 months ago. Viewed 6k times. It's saying Requires: pkgconfig kbproto Required: pkgconfig xcb Requires: pkgconfig xproto Add a comment.
With good humor and cheer, they took a rough draft and made it an infinitely better and more useful document. The work they have done will help many everywhere. The alpha and beta test participants deserve special recognition and thanks as well. It is significant that the bug reports and many fixes during alpha and beta test came almost exclusively from just a few of the alpha testers, mostly hardware vendors working on product implementations of X.
The continued public contribution of vendors and universities is certainly to the benefit of the entire X community. Our special thanks must go to Sam Fuller, Vice-President of Corporate Research at Digital, who has remained committed to the widest public availability of X and who made it possible to greatly supplement MIT's resources with the Digital staff in order to make version 11 a reality.
Others not mentioned here worked on the toolkit and are acknowledged in the X Toolkit documentation. The principal author of the rest of the internationalization facilities is Glenn Widener Tektronix. Our thanks to them for keeping their sense of humor through a long and sometimes difficult design process. Although the words and much of the design are due to them, many others have contributed substantially to the design and implementation.
The principal authors design and implementation of the Xcms color management facilities are Al Tabayoyon Tektronix and Chuck Adams Tektronix. We also once again thank Al Mento of Digital for his work in formatting and reformatting text for this manual, and for producing man pages. Stephen Gildea X Consortium authored the threads support.
Ovais Ashraf Sun and Greg Olsen Sun contributed substantially by testing the facilities and reporting bugs in a timely fashion. The coordinators of the integration, testing, and release of this implementation of the internationalization facilities are Nobuyuki Tanaka Sony and Makoto Wakamatsu Sony.
X display servers run on computers with either monochrome or color bitmap display hardware. The server distributes user input to and accepts output requests from various client programs located either on the same machine or elsewhere in the network.
Xlib is a C subroutine library that application programs clients use to interface with the window system by means of a stream connection. Although a client usually runs on the same machine as the X server it is talking to, this need not be the case. Rather, it provides a detailed description of each function in the library as well as a discussion of the related background information. Other higher-level abstractions for example, those provided by the toolkits for X are built on top of the Xlib library.
For further information about these higher-level libraries, see the appropriate toolkit documentation. Although additional information appears here, the protocol document is the ruling document.
Overview of the X Window System. Standard header files. Generic values and types. Naming and argument conventions within Xlib. Programming considerations. Character sets and encodings.
Formatting conventions. Some of the terms used in this book are unique to X, and other terms that are common to other window systems have different meanings in X. You may find it helpful to refer to the glossary , which is located at the end of the book. The X Window System supports one or more screens containing overlapping windows or subwindows. A screen is a physical monitor and hardware that can be color, grayscale, or monochrome.
There can be multiple screens for each display or workstation. A single X server can provide display services for any number of screens. A set of screens for a single user with one keyboard and one pointer usually a mouse is called a display. All the windows in an X server are arranged in strict hierarchies. At the top of each hierarchy is a root window , which covers each of the display screens. Each root window is partially or completely covered by child windows.
All windows, except for root windows, have parents. There is usually at least one window for each application program. Child windows may in turn have their own children. In this way, an application program can create an arbitrarily deep tree on each screen. X provides graphics, text, and raster operations for windows. A child window can be larger than its parent. That is, part or all of the child window can extend beyond the boundaries of the parent, but all output to a window is clipped by its parent.
If several children of a window have overlapping locations, one of the children is considered to be on top of or raised over the others, thus obscuring them. Output to areas covered by other windows is suppressed by the window system unless the window has backing store.
If a window is obscured by a second window, the second window obscures only those ancestors of the second window that are also ancestors of the first window. A window has a border zero or more pixels in width, which can be any pattern pixmap or solid color you like. A window usually but not always has a background pattern, which will be repainted by the window system when uncovered. Child windows obscure their parents, and graphic operations in the parent window usually are clipped by the children.
Each window and pixmap has its own coordinate system. The coordinate system has the X axis horizontal and the Y axis vertical with the origin [0, 0] at the upper-left corner. Coordinates are integral, in terms of pixels, and coincide with pixel centers. For a window, the origin is inside the border at the inside, upper-left corner. X does not guarantee to preserve the contents of windows. When part or all of a window is hidden and then brought back onto the screen, its contents may be lost.
The server then sends the client program an Expose event to notify it that part or all of the window needs to be repainted. Programs must be prepared to regenerate the contents of windows on demand. X also provides off-screen storage of graphics objects, called pixmaps. Single plane depth 1 pixmaps are sometimes referred to as bitmaps. Pixmaps can be used in most graphics functions interchangeably with windows and are used in various graphics operations to define patterns or tiles.
Windows and pixmaps together are referred to as drawables. Most of the functions in Xlib just add requests to an output buffer. These requests later execute asynchronously on the X server. Functions that return values of information stored in the server do not return that is, they block until an explicit reply is received or an error occurs. You can provide an error handler, which will be called when the error is reported.
If a client does not want a request to execute asynchronously, it can follow the request with a call to XSync , which blocks until all previously buffered asynchronous events have been sent and acted on.
As an important side effect, the output buffer in Xlib is always flushed by a call to any function that returns a value from the server or waits for input.
Many Xlib functions will return an integer resource ID, which allows you to refer to objects stored on the X server. These resources are created by requests and are destroyed or freed by requests or when connections are closed. Most of these resources are potentially shareable between applications, and in fact, windows are manipulated explicitly by window manager programs. Fonts and cursors are shared automatically across multiple screens. Fonts are loaded and unloaded as needed and are shared by multiple clients.
Fonts are often cached in the server. Xlib provides no support for sharing graphics contexts between applications. Client programs are informed of events.
Events may either be side effects of a request for example, restacking windows generates Expose events or completely asynchronous for example, from the keyboard.
A client program asks to be informed of events. Because other applications can send events to your application, programs must be prepared to handle or ignore events of all types. Input events for example, a key pressed or the pointer moved arrive asynchronously from the server and are queued until they are requested by an explicit call for example, XNextEvent or XWindowEvent.
These events also arrive asynchronously, but the client may wish to explicitly wait for them by calling XSync after calling a function that can cause the server to generate events. Some functions return Status , an integer error indication. If the function fails, it returns a zero.
If the function returns a status of zero, it has not updated the return arguments. Because C does not provide multiple return values, many functions must return their results by writing into client-passed storage. By default, errors are handled either by a standard library function or by one that you provide. Functions that return pointers to strings return NULL pointers if the string does not exist. The X server reports protocol errors at the time that it detects them.
If more than one error could be generated for a given request, the server can report any of them. Because Xlib usually does not transmit requests to the server immediately that is, it buffers them , errors can be reported much later than they actually occur.
For debugging purposes, however, Xlib provides a mechanism for forcing synchronous behavior see section When synchronization is enabled, errors are reported as they are generated. When Xlib detects an error, it calls an error handler, which your program can provide. If you do not provide an error handler, the error is printed, and your program terminates. The following include files are part of the Xlib standard:. This is the main header file for Xlib.
The majority of all Xlib symbols are declared by including this file. This file also contains the preprocessor symbol XlibSpecificationRelease. This symbol is defined to have the 6 in this release of the standard. Release 5 of Xlib was the first release to have this symbol. This file declares types and constants for the X protocol that are to be used by applications.
This file contains symbols for much of the color management facilities described in chapter 6. All functions, types, and symbols with the prefix "Xcms", plus the Color Conversion Contexts macros, are declared in this file.
This file declares various functions, types, and symbols used for inter-client communication and application utility functions, which are described in chapters 14 and This file declares all functions, types, and symbols for the resource manager facilities, which are described in chapter This file declares the cursor symbols for the standard cursor font, which are listed in Appendix B. The KeySyms are arranged in groups, and a preprocessor symbol controls inclusion of each group.
The preprocessor symbol must be defined prior to inclusion of the file to obtain the associated values. This file declares all the functions, types, and symbols used for extensions, which are described in Appendix C. This file declares types and symbols for the basic X protocol, for use in implementing extensions.
This file declares all the functions, types, and symbols used for the X10 compatibility functions, which are described in Appendix D.
Xlib defines the type Bool and the Boolean values True and False. None is the universal null resource ID or atom. Xlib follows a number of conventions for the naming and syntax of the functions. Given that you remember what information the function requires, these conventions are intended to make the syntax of the functions more predictable.
To differentiate the X symbols from the other symbols, the library uses mixed case for external symbols. It leaves lowercase for variables and all uppercase for user macros, as per existing convention. All user-visible data structures begin with a capital X. More generally, anything that a user might dereference begins with a capital X. Macros and other symbols do not begin with a capital X.
To distinguish them from all user symbols, each word in the macro is capitalized. All elements of or variables in a data structure are in lowercase. All resource objects, where used, occur at the beginning of the argument list immediately after the display argument. When a graphics context is present together with another type of resource most commonly, a drawable , the graphics context occurs in the argument list after the other resource.
Drawables outrank all other resources. Where the x, y, width, and height arguments are used together, the x and y arguments always precede the width and height arguments. Where a mask is accompanied with a structure, the mask always precedes the pointer to the structure in the argument list. Coordinates and sizes in X are actually bit quantities.
This decision was made to minimize the bandwidth required for a given level of performance. Coordinates usually are declared as an int in the interface. Values larger than 16 bits are truncated silently. Sizes width and height are declared as unsigned quantities. Keyboards are the greatest variable between different manufacturers' workstations. If you want your program to be portable, you should be particularly conservative here. Many display systems have limited amounts of off-screen memory.
If you can, you should minimize use of pixmaps and backing store. The user should have control of their screen real estate. Therefore, you should write your applications to react to window management rather than presume control of the entire screen. What you do inside of your top-level window, however, is up to your application. Some of the Xlib functions make reference to specific character sets and character encodings. The following are the most common:. A basic set of 97 characters, which are assumed to exist in all locales supported by Xlib.
This set contains the following characters:. The actual encoding of these characters on the host is system dependent. The encoding of the X Portable Character Set on the host. The encoding itself is not defined by this standard, but the encoding must be the same in all locales supported by Xlib on the host. If a string is said to be in the Host Portable Character Encoding, then it only contains characters from the X Portable Character Set, in the host encoding.
The set of 65 characters, which can be used in naming files on a POSIX -compliant host, that are correctly processed in all locales. The set is:. Global symbols are printed in this special font. These can be either function names, symbols defined in include files, or structure names.
When declared and defined, function arguments are printed in italics. In the explanatory text that follows, they usually are printed in regular type. Each function is introduced by a general discussion that distinguishes it from other functions. The function declaration itself follows, and each argument is specifically explained.
General discussion of the function, if any is required, follows the arguments. Where applicable, the last paragraph of the explanation lists the possible Xlib error codes that the function can generate. For a complete discussion of the Xlib error codes, see section To eliminate any ambiguity between those arguments that you pass and those that a function returns to you, the explanations for all arguments that you pass start with the word specifies or, in the case of multiple arguments, the word specify.
The explanations for all arguments that are returned to you start with the word returns or, in the case of multiple arguments, the word return. The explanations for all arguments that you can pass and are returned start with the words specifies and returns. All other pointers passed to these functions are used for reading only. Before your program can use a display, you must establish a connection to the X server.
Once you have established a connection, you then can use the Xlib macros and functions discussed in this chapter to return information about the display.
This chapter discusses how to:. To open a connection to the X server that controls a display, use XOpenDisplay. Specifies the hardware display name, which determines the display and communications domain to be used. The encoding and interpretation of the display name are implementation-dependent. Strings in the Host Portable Character Encoding are supported; support for other characters is implementation-dependent.
Specifies a protocol family or an alias for a protocol family. Supported protocol families are implementation dependent. The protocol entry is optional. Specifies the name of the host machine on which the display is physically attached. You follow the hostname with either a single colon : or a double colon Specifies the number of the display server on that host machine.
You may optionally follow this display number with a period. A single CPU can have more than one display. Multiple displays are usually numbered starting with zero.
Specifies the screen to be used on that server. Multiple screens can be controlled by a single X server. The XOpenDisplay function returns a Display structure that serves as the connection to the X server and that contains all the information about that X server. If the protocol is specified as "tcp", "inet", or "inet6", or if no protocol is specified and the hostname is a host machine name and a single colon : separates the hostname and display number, XOpenDisplay connects using TCP streams.
Otherwise, the implementation determines which IP version is used. If the hostname and protocol are both not specified, Xlib uses whatever it believes is the fastest transport.
If the hostname is a host machine name and a double colon :: separates the hostname and display number, XOpenDisplay connects using DECnet. A single X server can support any or all of these transport mechanisms simultaneously. A particular Xlib implementation can support many more of these transport mechanisms.
After a successful call to XOpenDisplay , all of the screens in the display can be used by the client. You can access elements of the Display and Screen structures only by using the information macros or functions. For information about using macros and functions to obtain information from the Display structure, see section 2. X servers may implement various types of access control mechanisms see section 9. The Xlib library provides a number of useful macros and corresponding functions that return data from the Display structure.
The macros are used for C programming, and their corresponding function equivalents are for other language bindings. This section discusses the:. All other members of the Display structure that is, those for which no macros are defined are private to Xlib and must not be used.
Applications must never directly modify or inspect these private members of the Display structure. These functions really should be named Screen whatever and XScreen whatever , not Display whatever or XDisplay whatever. Our apologies for the resulting confusion. Applications should not directly modify any part of the Display and Screen structures. The members should be considered read-only, although they may change as the result of other operations on the display.
The following lists the C language macros, their corresponding function equivalents that are for other language bindings, and what data both can return. Both return a value with all bits set to 1 suitable for use in a plane argument to a procedure. Both BlackPixel and WhitePixel can be used in implementing a monochrome application.
These pixel values are for permanently allocated entries in the default colormap. The actual RGB red, green, and blue values are settable on some screens and, in any case, may not actually be black or white. The names are intended to convey the expected relative intensity of the colors. ConnectionNumber display ;.
Both return a connection number for the specified display. Both return the default colormap ID for allocation on the specified screen. Most routine allocations of color should be made out of this colormap. Both return the depth number of planes of the default root window for the specified screen.
Other depths may also be supported on this screen see XMatchVisualInfo. To determine the number of depths that are available on a given screen, use XListDepths. The XListDepths function returns the array of depths that are available on the specified screen.
To release the memory allocated for the array of depths, use XFree. Both return the default graphics context for the root window of the specified screen. This GC is created for the convenience of simple applications and contains the default GC components with the foreground and background pixel values initialized to the black and white pixels for the screen, respectively.
You can modify its contents freely because it is not used in any Xlib function. This GC should never be freed. DefaultRootWindow display ;. Both return the root window for the default screen. DefaultScreenOfDisplay display ;. Both return a pointer to the default screen. Both return a pointer to the indicated screen. DefaultScreen display ;. Both return the default screen number referenced by the XOpenDisplay function.
This macro or function should be used to retrieve the screen number in applications that will use only a single screen. Both return the default visual type for the specified screen. For further information about visual types, see section 3. Both return the number of entries in the default colormap. Both return the depth of the root window of the specified screen. For an explanation of depth, see the glossary. DisplayString display ;. Both return the string that was passed to XOpenDisplay when the current display was opened.
These are useful to applications that invoke the fork system call and want to open a new connection to the same display from the child process as well as for printing error messages.
The XExtendedMaxRequestSize function returns zero if the specified display does not support an extended-length protocol encoding; otherwise, it returns the maximum request size in 4-byte units supported by the server using the extended-length encoding.
The XMaxRequestSize function returns the maximum request size in 4-byte units supported by the server without using an extended-length protocol encoding. Single protocol requests to the server can be no larger than this size unless an extended-length protocol encoding is supported by the server. The protocol guarantees the size to be no smaller than units bytes. LastKnownRequestProcessed display ;.
Both extract the full serial number of the last request known by Xlib to have been processed by the X server. Xlib automatically sets this number when replies, events, and errors are received. NextRequest display ;.
Both extract the full serial number that is to be used for the next request. Serial numbers are maintained separately for each display connection. ProtocolVersion display ;. Both return the major version number 11 of the X protocol associated with the connected display.
How can I install these files? Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Jos Jos Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
0コメント