i3/libi3 at 29f9f8c0908d40e88d3b065533b1b5f232f5685e - i3

History

Michael Stapelberg 91134f75c0 Move get_mod_mask to libi3, use it in i3 and i3-config-wizard Also, the API changed a bit. There are two functions now, both assume you already got the keysyms (which is the case for i3 and i3-config-wizard), one gets the modifier mapping for you (aio_get_mod_mask_for) while the other assumes you also got that. No roundtrips are required for the latter.		2011-10-23 21:26:15 +01:00
..
fake_configure_notify.c	Move fake_configure_notify to libi3	2011-10-09 13:40:15 +01:00
get_colorpixel.c	Move get_colorpixel to libi3, use it everywhere else	2011-10-23 17:38:21 +01:00
get_mod_mask.c	Move get_mod_mask to libi3, use it in i3 and i3-config-wizard	2011-10-23 21:26:15 +01:00
get_socket_path.c	Move get_colorpixel to libi3, use it everywhere else	2011-10-23 17:38:21 +01:00
ipc_connect.c	Move get_colorpixel to libi3, use it everywhere else	2011-10-23 17:38:21 +01:00
ipc_recv_message.c	Move ipc_send_message and ipc_recv_message to libi3	2011-10-02 18:33:36 +01:00
ipc_send_message.c	Move get_colorpixel to libi3, use it everywhere else	2011-10-23 17:38:21 +01:00
Makefile	Introduce libi3, an internal library to eliminate code duplication	2011-10-02 16:11:30 +01:00
README	Introduce libi3, an internal library to eliminate code duplication	2011-10-02 16:11:30 +01:00
safewrappers.c	Move get_colorpixel to libi3, use it everywhere else	2011-10-23 17:38:21 +01:00
strndup.c	move strndup to libi3	2011-10-23 18:02:01 +01:00

README

Introduction
============

libi3 is an *INTERNAL* library which contains functions that i3 and related
tools (i3-msg, i3-input, i3-nagbar, i3-config-wizard, i3bar) use.

It is NOT to be used by other programs.

Structure
=========

Every function gets its own .c file, which in turn gets compiled into an .o
object file. Afterwards, all .o files are archived into one static library
(libi3.a). This library will be linked into all i3 binaries. The linker is able
to eliminate unused .o files when linking, so only the functions which you
actually use will be included in the corresponding binary.