summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/apr/apr/0002-apr-Remove-workdir-path-references-from-installed-ap.patch
blob: d63423f3a1929c0ca41d56db74d9ff22c74e6f93 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
From 689a8db96a6d1e1cae9cbfb35d05ac82140a6555 Mon Sep 17 00:00:00 2001
From: Hongxu Jia <hongxu.jia@windriver.com>
Date: Tue, 30 Jan 2018 09:39:06 +0800
Subject: [PATCH] apr: Remove workdir path references from installed apr files

Upstream-Status: Inappropriate [configuration]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

The generated `apr-1-config' is used by other recipes at build time or
packages at target run time, the workdir path caused confusion.

Rebase to 1.6.3

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>

---
 apr-config.in | 32 ++------------------------------
 1 file changed, 2 insertions(+), 30 deletions(-)

diff --git a/apr-config.in b/apr-config.in
index bed47ca..47874e5 100644
--- a/apr-config.in
+++ b/apr-config.in
@@ -164,16 +164,7 @@ while test $# -gt 0; do
     flags="$flags $LDFLAGS"
     ;;
     --includes)
-    if test "$location" = "installed"; then
         flags="$flags -I$includedir $EXTRA_INCLUDES"
-    elif test "$location" = "crosscompile"; then
-        flags="$flags -I$APR_TARGET_DIR/$includedir $EXTRA_INCLUDES"
-    elif test "$location" = "source"; then
-        flags="$flags -I$APR_SOURCE_DIR/include $EXTRA_INCLUDES"
-    else
-        # this is for VPATH builds
-        flags="$flags -I$APR_BUILD_DIR/include -I$APR_SOURCE_DIR/include $EXTRA_INCLUDES"
-    fi
     ;;
     --srcdir)
     echo $APR_SOURCE_DIR
@@ -197,33 +188,14 @@ while test $# -gt 0; do
     exit 0
     ;;
     --link-ld)
-    if test "$location" = "installed"; then
-        ### avoid using -L if libdir is a "standard" location like /usr/lib
-        flags="$flags -L$libdir -l${APR_LIBNAME}"
-    elif test "$location" = "crosscompile"; then
-        flags="$flags -L$APR_TARGET_DIR/$libdir -l${APR_LIBNAME}"
-    else
-        ### this surely can't work since the library is in .libs?
-        flags="$flags -L$APR_BUILD_DIR -l${APR_LIBNAME}"
-    fi
+        flags="$flags -l${APR_LIBNAME}"
     ;;
     --link-libtool)
     # If the LA_FILE exists where we think it should be, use it.  If we're
     # installed and the LA_FILE does not exist, assume to use -L/-l
     # (the LA_FILE may not have been installed).  If we're building ourselves,
     # we'll assume that at some point the .la file be created.
-    if test -f "$LA_FILE"; then
-        flags="$flags $LA_FILE"
-    elif test "$location" = "installed"; then
-        ### avoid using -L if libdir is a "standard" location like /usr/lib
-        # Since the user is specifying they are linking with libtool, we
-        # *know* that -R will be recognized by libtool.
-        flags="$flags -L$libdir -R$libdir -l${APR_LIBNAME}"
-    elif test "$location" = "crosscompile"; then
-        flags="$flags  -L${APR_TARGET_DIR}/$libdir  -l${APR_LIBNAME}"
-    else
-        flags="$flags $LA_FILE"
-    fi
+        flags="$flags -l${APR_LIBNAME}"
     ;;
     --shlib-path-var)
     echo "$SHLIBPATH_VAR"