marrub
/
st
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
st/config.mk

36 lines
937 B
Makefile
Raw Normal View History

backport of local changes
2009-05-10 05:17:09 -07:00
# st version
bump version to 0.8.2
2019-02-09 03:48:39 -08:00
VERSION = 0.8.2
backport of local changes
2009-05-10 05:17:09 -07:00
# Customize below to fit your system
# paths
add local configurations
2019-07-27 14:15:50 -07:00
PREFIX = $(HOME)/.local
Do not obfuscate what make is doing. Change some styling too while we're at it.
2017-07-11 15:24:51 -07:00
MANPREFIX = $(PREFIX)/share/man
backport of local changes
2009-05-10 05:17:09 -07:00
X11INC = /usr/X11R6/include
X11LIB = /usr/X11R6/lib
Set the path of pkg-config in a variable instead of hardcoding it In this way the path of pkg-config can be overridden from the command line. This is useful for example when cross-compiling.
2019-01-04 00:48:37 -08:00
PKG_CONFIG = pkg-config
backport of local changes
2009-05-10 05:17:09 -07:00
# includes and libs
Do not obfuscate what make is doing. Change some styling too while we're at it.
2017-07-11 15:24:51 -07:00
INCS = -I$(X11INC) \
Set the path of pkg-config in a variable instead of hardcoding it In this way the path of pkg-config can be overridden from the command line. This is useful for example when cross-compiling.
2019-01-04 00:48:37 -08:00
`$(PKG_CONFIG) --cflags fontconfig` \
`$(PKG_CONFIG) --cflags freetype2`
Do not obfuscate what make is doing. Change some styling too while we're at it.
2017-07-11 15:24:51 -07:00
LIBS = -L$(X11LIB) -lm -lrt -lX11 -lutil -lXft \
Set the path of pkg-config in a variable instead of hardcoding it In this way the path of pkg-config can be overridden from the command line. This is useful for example when cross-compiling.
2019-01-04 00:48:37 -08:00
`$(PKG_CONFIG) --libs fontconfig` \
`$(PKG_CONFIG) --libs freetype2`
st now runs on Linux, OpenBSD and FreeBSD.
2010-08-27 18:18:22 -07:00
backport of local changes
2009-05-10 05:17:09 -07:00
# flags
Let the user specify CPPFLAGS This complements the work done in d4928ed, allowing the user to specify the preprocessor flags with the CPPFLAGS environment variable. This is useful for example to specify preprocessor macros with -D. CFLAGS could be used instead, but CPPFLAGS is more correct and is expected to be honored in some cases. For example, the helper scripts to build Debian packages make use of CPPFLAGS, but the variable is currently being ignored unless manually appended to CFLAGS.
2019-01-10 04:36:09 -08:00
STCPPFLAGS = -DVERSION=\"$(VERSION)\" -D_XOPEN_SOURCE=600
add local configurations
2019-07-27 14:15:50 -07:00
STCFLAGS = $(INCS) $(STCPPFLAGS) $(CPPFLAGS) $(CFLAGS) -mtune=native -march=native -O3 -pipe -fstack-protector-strong -fno-plt
Let the user specify C and LD FLAGS
2017-07-11 15:26:35 -07:00
STLDFLAGS = $(LIBS) $(LDFLAGS)
backport of local changes
2009-05-10 05:17:09 -07:00
Pledge on OpenBSD
2018-05-25 02:59:28 -07:00
# OpenBSD:
#CPPFLAGS = -DVERSION=\"$(VERSION)\" -D_XOPEN_SOURCE=600 -D_BSD_SOURCE
#LIBS = -L$(X11LIB) -lm -lX11 -lutil -lXft \
# `pkg-config --libs fontconfig` \
# `pkg-config --libs freetype2`
backport of local changes
2009-05-10 05:17:09 -07:00
# compiler and linker
Do not obfuscate what make is doing. Change some styling too while we're at it.
2017-07-11 15:24:51 -07:00
# CC = c99