a1batross
/
kore
forked from mirrors/kore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
kore/Makefile

177 lines
4.1 KiB
Makefile
Raw Normal View History

first commit
2013-04-17 22:34:27 +02:00
# Kore Makefile
Alter where the version number comes from. Now if we are a git repo we fetch the branch name and commitid to build the version string. If there is no git repo we'll look at the RELEASE file.
2018-06-19 19:05:55 +02:00
CC?=cc
Added ability to set path prefix during make.
2014-12-11 23:58:15 +01:00
PREFIX?=/usr/local
Allow "kore build" to produce single binaries. Producing single binaries can now be done with building with "kore build". To get started edit your build.conf and add the following directives: single_binary = yes kore_source = /path/to/kore optionally you can add kore_flavor to instruct how kore should be built: kore_flavor = NOTLS=1 When doing this your build.conf must also include the correct linking options as the linking is now done fully by kore build. The binary produced will include your configuration and takes over a few of kore its command line flags (such as -f, -n or -r).
2016-07-06 16:16:15 +02:00
OBJDIR?=obj
Hook orbit into the build
2014-08-01 10:46:50 +02:00
KORE=kore
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
KODEV=kodev/kodev
Added ability to set path prefix during make.
2014-12-11 23:58:15 +01:00
INSTALL_DIR=$(PREFIX)/bin
install kodev manual page.
2018-06-19 22:40:55 +02:00
MAN_DIR=$(PREFIX)/share/man
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
SHARE_DIR=$(PREFIX)/share/kore
Added ability to set path prefix during make.
2014-12-11 23:58:15 +01:00
INCLUDE_DIR=$(PREFIX)/include/kore
first commit
2013-04-17 22:34:27 +02:00
Alter where the version number comes from. Now if we are a git repo we fetch the branch name and commitid to build the version string. If there is no git repo we'll look at the RELEASE file.
2018-06-19 19:05:55 +02:00
VERSION=src/version.c
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
S_SRC= src/kore.c src/buf.c src/config.c src/connection.c \
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
src/domain.c src/mem.c src/msg.c src/module.c src/net.c \
Add initial python support. Based on work done by Stanislav Yudin.
2017-01-12 23:38:51 +01:00
src/pool.c src/runtime.c src/timer.c src/utils.c src/worker.c \
Alter where the version number comes from. Now if we are a git repo we fetch the branch name and commitid to build the version string. If there is no git repo we'll look at the RELEASE file.
2018-06-19 19:05:55 +02:00
src/keymgr.c $(VERSION)
first commit
2013-04-17 22:34:27 +02:00
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
FEATURES=
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
FEATURES_INC=
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
Build option changes. - Build with -O2 unless NOOPT is set to 1. - Hide -g behind DEBUG instead of always building with it. - Explicitely set the standard used to c99, use pedantic.
2016-02-01 15:33:40 +01:00
CFLAGS+=-Wall -Werror -Wstrict-prototypes -Wmissing-prototypes
first commit
2013-04-17 22:34:27 +02:00
CFLAGS+=-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual
Move header files to include/kore. Mimics how the header files are installed on a system as PREFIX/include/kore. This is required for getting kodev to use the headers from the kore_source option instead of requiring the kore headers to be installed on the system even when building as a single_binary.
2018-03-30 13:45:29 +02:00
CFLAGS+=-Wsign-compare -Iinclude/kore -std=c99 -pedantic
Rework HTTP and worker processes. The HTTP layer used to make a copy of each incoming header and its value for a request. Stop doing that and make HTTP headers zero-copy all across the board. This change comes with some api function changes, notably the http_request_header() function which now takes a const char ** rather than a char ** out pointer. This commit also constifies several members of http_request, beware. Additional rework how the worker processes deal with the accept lock. Before: if a worker held the accept lock and it accepted a new connection it would release the lock for others and back off for 500ms before attempting to grab the lock again. This approach worked but under high load this starts becoming obvious. Now: - workers not holding the accept lock and not having any connections will wait less long before returning from kore_platform_event_wait(). - workers not holding the accept lock will no longer blindly wait an arbitrary amount in kore_platform_event_wait() but will look at how long until the next lock grab is and base their timeout on that. - if a worker its next_lock timeout is up and failed to grab the lock it will try again in half the time again. - the worker process holding the lock will when releasing the lock double check if it still has space for newer connections, if it does it will keep the lock until it is full. This prevents the lock from bouncing between several non busy worker processes all the time. Additional fixes: - Reduce the number of times we check the timeout list, only do it twice per second rather then every event tick. - Fix solo worker count for TLS (we actually hold two processes, not one). - Make sure we don't accidentally miscalculate the idle time causing new connections under heavy load to instantly drop. - Swap from gettimeofday() to clock_gettime() now that MacOS caught up.
2018-02-14 13:48:49 +01:00
CFLAGS+=-DPREFIX='"$(PREFIX)"' -fstack-protector-all
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
LDFLAGS=-rdynamic -lssl -lcrypto
Add BSD kqueue(2) support. Compile with make bsd (or make linux for linux)
2013-06-17 23:39:17 +02:00
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
ifneq ("$(KORE_SINGLE_BINARY)", "")
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
CFLAGS+=-DKORE_SINGLE_BINARY
FEATURES+=-DKORE_SINGLE_BINARY
endif
fix brocken DEBUG define
2013-11-21 12:00:07 +01:00
ifneq ("$(DEBUG)", "")
Build option changes. - Build with -O2 unless NOOPT is set to 1. - Hide -g behind DEBUG instead of always building with it. - Explicitely set the standard used to c99, use pedantic.
2016-02-01 15:33:40 +01:00
CFLAGS+=-DKORE_DEBUG -g
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
FEATURES+=-DKORE_DEBUG
Debug builds imply NOOPT
2016-02-13 14:21:09 +01:00
NOOPT=1
Build option changes. - Build with -O2 unless NOOPT is set to 1. - Hide -g behind DEBUG instead of always building with it. - Explicitely set the standard used to c99, use pedantic.
2016-02-01 15:33:40 +01:00
endif
ifneq ("$(NOOPT)", "")
CFLAGS+=-O0
else
Rework HTTP and worker processes. The HTTP layer used to make a copy of each incoming header and its value for a request. Stop doing that and make HTTP headers zero-copy all across the board. This change comes with some api function changes, notably the http_request_header() function which now takes a const char ** rather than a char ** out pointer. This commit also constifies several members of http_request, beware. Additional rework how the worker processes deal with the accept lock. Before: if a worker held the accept lock and it accepted a new connection it would release the lock for others and back off for 500ms before attempting to grab the lock again. This approach worked but under high load this starts becoming obvious. Now: - workers not holding the accept lock and not having any connections will wait less long before returning from kore_platform_event_wait(). - workers not holding the accept lock will no longer blindly wait an arbitrary amount in kore_platform_event_wait() but will look at how long until the next lock grab is and base their timeout on that. - if a worker its next_lock timeout is up and failed to grab the lock it will try again in half the time again. - the worker process holding the lock will when releasing the lock double check if it still has space for newer connections, if it does it will keep the lock until it is full. This prevents the lock from bouncing between several non busy worker processes all the time. Additional fixes: - Reduce the number of times we check the timeout list, only do it twice per second rather then every event tick. - Fix solo worker count for TLS (we actually hold two processes, not one). - Make sure we don't accidentally miscalculate the idle time causing new connections under heavy load to instantly drop. - Swap from gettimeofday() to clock_gettime() now that MacOS caught up.
2018-02-14 13:48:49 +01:00
CFLAGS+=-O3
If DEBUG is set in the environment, define KORE_DEBUG
2013-11-16 13:30:47 +01:00
endif
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
ifneq ("$(NOHTTP)", "")
CFLAGS+=-DKORE_NO_HTTP
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
FEATURES+=-DKORE_NO_HTTP
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
else
S_SRC+= src/auth.c src/accesslog.c src/http.c \
Kill off zlib_dict.c
2015-12-04 14:11:37 +01:00
src/validator.c src/websocket.c
Add KORE_PENDANTIC_MALLOC option. This option tells Kore to zero out memory when allocated, freed or when get/put from the pools.
2014-04-22 12:46:23 +02:00
endif
Call it NOTLS instead. Per @jorisvink's feedback.
2015-05-25 15:42:34 +02:00
ifneq ("$(NOTLS)", "")
CFLAGS+=-DKORE_NO_TLS
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
FEATURES+=-DKORE_NO_TLS
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
ifneq ("$(NOHTTP)", "")
LDFLAGS=-rdynamic
else
LDFLAGS=-rdynamic -lcrypto
endif
Add a BENCHMARK compile option which compiles without OpenSSL. Personally use this for testing Kore its performance without letting the OpenSSL stack get in the way too much. Note that it leaves data structures as is, and just removes any calls to OpenSSL (and removes the linking vs OpenSSL).
2014-08-01 10:22:32 +02:00
endif
Initial stab at entering postgresql contrib code. Has support for full async pgsql queries. Most of the logic is hidden behind a KORE_PGSQL() macro allowing you to insert these pgsql calls in your page handlers without blocking the kore worker while the query is going off. There is place for improvement here, and perhaps KORE_PGSQL won't stay as I feel this might overcomplicate things instead of making them simpler as I thought it would.
2014-03-30 23:54:35 +02:00
ifneq ("$(PGSQL)", "")
Move actual code out of contrib into src/.
2014-07-02 12:19:38 +02:00
S_SRC+=src/pgsql.c
Support postgresl under the bsds
2014-04-02 00:06:24 +02:00
LDFLAGS+=-L$(shell pg_config --libdir) -lpq
When compiling with PGSQL, note the include dir for "kore build"
2014-08-03 17:33:40 +02:00
CFLAGS+=-I$(shell pg_config --includedir) -DKORE_USE_PGSQL \
-DPGSQL_INCLUDE_PATH="\"$(shell pg_config --includedir)\""
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
FEATURES+=-DKORE_USE_PGSQL
FEATURES_INC+=-I$(shell pg_config --includedir)
Initial stab at entering postgresql contrib code. Has support for full async pgsql queries. Most of the logic is hidden behind a KORE_PGSQL() macro allowing you to insert these pgsql calls in your page handlers without blocking the kore worker while the query is going off. There is place for improvement here, and perhaps KORE_PGSQL won't stay as I feel this might overcomplicate things instead of making them simpler as I thought it would.
2014-03-30 23:54:35 +02:00
endif
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
ifneq ("$(TASKS)", "")
Move actual code out of contrib into src/.
2014-07-02 12:19:38 +02:00
S_SRC+=src/tasks.c
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
LDFLAGS+=-lpthread
CFLAGS+=-DKORE_USE_TASKS
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
FEATURES+=-DKORE_USE_TASKS
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
endif
JSONRPC Changed Makefile option location
2016-07-12 13:33:21 +02:00
ifneq ("$(JSONRPC)", "")
S_SRC+=src/jsonrpc.c
LDFLAGS+=-lyajl
CFLAGS+=-DKORE_USE_JSONRPC
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
FEATURES+=-DKORE_USE_JSONRPC
JSONRPC Changed Makefile option location
2016-07-12 13:33:21 +02:00
endif
Add initial python support. Based on work done by Stanislav Yudin.
2017-01-12 23:38:51 +01:00
ifneq ("$(PYTHON)", "")
S_SRC+=src/python.c
LDFLAGS+=$(shell python3-config --ldflags)
CFLAGS+=$(shell python3-config --includes) -DKORE_USE_PYTHON
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
FEATURES+=-DKORE_USE_PYTHON
FEATURES_INC+=$(shell python3-config --includes)
Add initial python support. Based on work done by Stanislav Yudin.
2017-01-12 23:38:51 +01:00
endif
add shorthand for building with fsanitize.
2018-06-12 19:43:10 +02:00
ifneq ("$(SANITIZE)", "")
CFLAGS+=-fsanitize=$(SANITIZE)
LDFLAGS+=-fsanitize=$(SANITIZE)
endif
Detect OS rather then supplying a build target
2013-11-16 12:41:58 +01:00
OSNAME=$(shell uname -s | sed -e 's/[-_].*//g' | tr A-Z a-z)
ifeq ("$(OSNAME)", "darwin")
Allow kore to build with openssl from osx brew.
2014-10-13 11:53:56 +02:00
CFLAGS+=-I/opt/local/include/ -I/usr/local/opt/openssl/include
LDFLAGS+=-L/opt/local/lib -L/usr/local/opt/openssl/lib
Detect OS rather then supplying a build target
2013-11-16 12:41:58 +01:00
S_SRC+=src/bsd.c
else ifeq ("$(OSNAME)", "linux")
Rework HTTP and worker processes. The HTTP layer used to make a copy of each incoming header and its value for a request. Stop doing that and make HTTP headers zero-copy all across the board. This change comes with some api function changes, notably the http_request_header() function which now takes a const char ** rather than a char ** out pointer. This commit also constifies several members of http_request, beware. Additional rework how the worker processes deal with the accept lock. Before: if a worker held the accept lock and it accepted a new connection it would release the lock for others and back off for 500ms before attempting to grab the lock again. This approach worked but under high load this starts becoming obvious. Now: - workers not holding the accept lock and not having any connections will wait less long before returning from kore_platform_event_wait(). - workers not holding the accept lock will no longer blindly wait an arbitrary amount in kore_platform_event_wait() but will look at how long until the next lock grab is and base their timeout on that. - if a worker its next_lock timeout is up and failed to grab the lock it will try again in half the time again. - the worker process holding the lock will when releasing the lock double check if it still has space for newer connections, if it does it will keep the lock until it is full. This prevents the lock from bouncing between several non busy worker processes all the time. Additional fixes: - Reduce the number of times we check the timeout list, only do it twice per second rather then every event tick. - Fix solo worker count for TLS (we actually hold two processes, not one). - Make sure we don't accidentally miscalculate the idle time causing new connections under heavy load to instantly drop. - Swap from gettimeofday() to clock_gettime() now that MacOS caught up.
2018-02-14 13:48:49 +01:00
CFLAGS+=-D_GNU_SOURCE=1 -D_FORTIFY_SOURCE=2
Detect OS rather then supplying a build target
2013-11-16 12:41:58 +01:00
LDFLAGS+=-ldl
S_SRC+=src/linux.c
else
S_SRC+=src/bsd.c
Add /usr/local/[include|lib] for BSD / JSONRPC.
2016-07-15 22:33:58 +02:00
ifneq ("$(JSONRPC)", "")
Typo.
2016-07-15 22:34:21 +02:00
CFLAGS+=-I/usr/local/include
Add /usr/local/[include|lib] for BSD / JSONRPC.
2016-07-15 22:33:58 +02:00
LDFLAGS+=-L/usr/local/lib
endif
Detect OS rather then supplying a build target
2013-11-16 12:41:58 +01:00
endif
Allow "kore build" to produce single binaries. Producing single binaries can now be done with building with "kore build". To get started edit your build.conf and add the following directives: single_binary = yes kore_source = /path/to/kore optionally you can add kore_flavor to instruct how kore should be built: kore_flavor = NOTLS=1 When doing this your build.conf must also include the correct linking options as the linking is now done fully by kore build. The binary produced will include your configuration and takes over a few of kore its command line flags (such as -f, -n or -r).
2016-07-06 16:16:15 +02:00
S_OBJS= $(S_SRC:src/%.c=$(OBJDIR)/%.o)
Alter where the version number comes from. Now if we are a git repo we fetch the branch name and commitid to build the version string. If there is no git repo we'll look at the RELEASE file.
2018-06-19 19:05:55 +02:00
all: $(VERSION) $(KORE) $(KODEV)
$(VERSION): force
@if [ -d .git ]; then \
GIT_REVISION=`git rev-parse --short=8 HEAD`; \
GIT_BRANCH=`git rev-parse --abbrev-ref HEAD`; \
rm -f $(VERSION); \
printf "const char *kore_version = \"%s-%s\";\n" \
$$GIT_BRANCH $$GIT_REVISION > $(VERSION); \
elif [ -f RELEASE ]; then \
printf "const char *kore_version = \"%s\";\n" \
`cat RELEASE` > $(VERSION); \
else \
echo "No version information found (no .git or RELEASE)"; \
exit 1; \
fi
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
$(KODEV):
$(MAKE) -C kodev
Allow "kore build" to produce single binaries. Producing single binaries can now be done with building with "kore build". To get started edit your build.conf and add the following directives: single_binary = yes kore_source = /path/to/kore optionally you can add kore_flavor to instruct how kore should be built: kore_flavor = NOTLS=1 When doing this your build.conf must also include the correct linking options as the linking is now done fully by kore build. The binary produced will include your configuration and takes over a few of kore its command line flags (such as -f, -n or -r).
2016-07-06 16:16:15 +02:00
$(KORE): $(OBJDIR) $(S_OBJS)
Correct order for linking
2014-08-02 13:01:58 +02:00
$(CC) $(S_OBJS) $(LDFLAGS) -o $(KORE)
make sure FEATURES_INC hits kore.features.
2017-08-30 12:03:58 +02:00
@echo $(FEATURES) $(FEATURES_INC) > kore.features
first commit
2013-04-17 22:34:27 +02:00
Allow "kore build" to produce single binaries. Producing single binaries can now be done with building with "kore build". To get started edit your build.conf and add the following directives: single_binary = yes kore_source = /path/to/kore optionally you can add kore_flavor to instruct how kore should be built: kore_flavor = NOTLS=1 When doing this your build.conf must also include the correct linking options as the linking is now done fully by kore build. The binary produced will include your configuration and takes over a few of kore its command line flags (such as -f, -n or -r).
2016-07-06 16:16:15 +02:00
objects: $(OBJDIR) $(S_OBJS)
Improve single binary builds. Allow kore build to pickup the required libraries for kore when building single binaries so that you no longer have to manually add them to ldflags.
2017-02-09 11:30:44 +01:00
@echo $(LDFLAGS) > $(OBJDIR)/ldflags
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
@echo "$(FEATURES) $(FEATURES_INC)" > $(OBJDIR)/features
Don't link object files if not needed
2015-07-25 19:10:48 +02:00
Allow "kore build" to produce single binaries. Producing single binaries can now be done with building with "kore build". To get started edit your build.conf and add the following directives: single_binary = yes kore_source = /path/to/kore optionally you can add kore_flavor to instruct how kore should be built: kore_flavor = NOTLS=1 When doing this your build.conf must also include the correct linking options as the linking is now done fully by kore build. The binary produced will include your configuration and takes over a few of kore its command line flags (such as -f, -n or -r).
2016-07-06 16:16:15 +02:00
$(OBJDIR):
@mkdir -p $(OBJDIR)
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
install: $(KORE) $(KODEV)
mkdir -p $(SHARE_DIR)
Install kore headers under /usr/local/include/kore
2014-07-03 22:39:16 +02:00
mkdir -p $(INCLUDE_DIR)
Added ability to set path prefix during make.
2014-12-11 23:58:15 +01:00
mkdir -p $(INSTALL_DIR)
install kodev manual page.
2018-06-19 22:40:55 +02:00
mkdir -p $(MAN_DIR)/man1
install -m 644 share/man/kodev.1 $(MAN_DIR)/man1/kodev.1
Hook orbit into the build
2014-08-01 10:46:50 +02:00
install -m 555 $(KORE) $(INSTALL_DIR)/$(KORE)
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
install -m 644 kore.features $(SHARE_DIR)/features
install headers correct again
2018-03-30 13:47:12 +02:00
install -m 644 include/kore/*.h $(INCLUDE_DIR)
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
$(MAKE) -C kodev install
Add install/uninstall targets.
2014-07-03 21:38:16 +02:00
uninstall:
Hook orbit into the build
2014-08-01 10:46:50 +02:00
rm -f $(INSTALL_DIR)/$(KORE)
Install kore headers under /usr/local/include/kore
2014-07-03 22:39:16 +02:00
rm -rf $(INCLUDE_DIR)
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
rm -rf $(SHARE_DIR)
$(MAKE) -C kodev uninstall
Add install/uninstall targets.
2014-07-03 21:38:16 +02:00
Allow "kore build" to produce single binaries. Producing single binaries can now be done with building with "kore build". To get started edit your build.conf and add the following directives: single_binary = yes kore_source = /path/to/kore optionally you can add kore_flavor to instruct how kore should be built: kore_flavor = NOTLS=1 When doing this your build.conf must also include the correct linking options as the linking is now done fully by kore build. The binary produced will include your configuration and takes over a few of kore its command line flags (such as -f, -n or -r).
2016-07-06 16:16:15 +02:00
$(OBJDIR)/%.o: src/%.c
first commit
2013-04-17 22:34:27 +02:00
$(CC) $(CFLAGS) -c $< -o $@
clean:
Alter where the version number comes from. Now if we are a git repo we fetch the branch name and commitid to build the version string. If there is no git repo we'll look at the RELEASE file.
2018-06-19 19:05:55 +02:00
rm -f $(VERSION); \
Initial stab at entering postgresql contrib code. Has support for full async pgsql queries. Most of the logic is hidden behind a KORE_PGSQL() macro allowing you to insert these pgsql calls in your page handlers without blocking the kore worker while the query is going off. There is place for improvement here, and perhaps KORE_PGSQL won't stay as I feel this might overcomplicate things instead of making them simpler as I thought it would.
2014-03-30 23:54:35 +02:00
find . -type f -name \*.o -exec rm {} \;
Split up kore cli tools into new binary. Having the create, build, run tools baked into the kore binary made things harder then they had to be for multiple projects with each different build flavors. So move away this functionality into a new "kodev" (name may change) binary that is installed next to kore. The new build tools will automatically pick up the correct flavors the kore binary it points to is installed with. Or for single builds what flavors where enabled. The new tool also will honor looking into PREFIX for the kore binary when doing a `kodev run`. Additionally add a new command "info" that shows some basic info about your project and how it will be built. For example it will show you the flavors of the kore binary installed on the system or the flavors you configured for a single binary build. Obligitory, hacking on a plane comment.
2017-02-19 06:52:29 +01:00
rm -rf $(KORE) $(OBJDIR) kore.features
$(MAKE) -C kodev clean
Detect OS rather then supplying a build target
2013-11-16 12:41:58 +01:00
Alter where the version number comes from. Now if we are a git repo we fetch the branch name and commitid to build the version string. If there is no git repo we'll look at the RELEASE file.
2018-06-19 19:05:55 +02:00
.PHONY: all clean force