i3/libi3 at 95f510e724ac1fc3611e1b736c7ef367c493af81 - i3

History

Fernando Tarlá Cardoso Lemos 95f510e724 Don't multiply by sizeof(char) twice. This is a no-op, since sizeof(char) is 1. But still, we shouldn't multiply twice, it's misleading.		2012-03-26 16:47:44 +02:00
..
fake_configure_notify.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
font.c	Document text_len in the draw_text description.	2012-03-26 16:47:23 +02:00
get_colorpixel.c	Implement support for chosing a 32 bit visual (necessary for pseudo-transparency) (Thanks darkraven)	2012-02-15 18:56:07 +00:00
get_mod_mask.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ipc_connect.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ipc_recv_message.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ipc_send_message.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +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
root_atom_contents.c	shmlog: store meta information in the buffer itself, store path as X11 atom	2012-01-06 23:40:07 +00:00
safewrappers.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
strndup.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ucs2_conversion.c	Don't multiply by sizeof(char) twice.	2012-03-26 16:47:44 +02: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.