| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
uwsgi is using pkg-config to detect whether or not yajl is present
in the build. We do want to use yajl, so we add an explicit dependency
and pkgconfig inherit.
Without this, build errors may occur, since the build paths that don't
use yajl are not supported.
And finally, to prevent the searching of host include paths, we set
UWSGI_REMOVE_INCLUDES and purge local directories. This ensures that
only the sysroot and package config settings are used.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
uwsgi needs uuid/uuid.h to be present, otherwise we get the following
build error:
| In file included from core/utils.c:1:0:
| ./uwsgi.h:188:23: fatal error: uuid/uuid.h: No such file or directory
| #include <uuid/uuid.h>
| ^
| compilation terminated.
Adding a e2fsprogs dependency gets the header file properly installed before
the build starts.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
While other wsgi integrations are possible (apache, nginx), barbican is developed
and supported via uwsgi. So we integrate uwsgi, with the default configuration
capable of acting as a gateway for python applications.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
