From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] kodi-platform: fix cross-build
Date: Thu, 18 Feb 2021 07:46:14 +0100 [thread overview]
Message-ID: <20210218064614.tr8uBtqaX3mcw1boeuTE7NYR7rwjcrD8QjZqfmoz2C4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27608@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/27608#discussion_r578168482
Comment:
Given that the file looks like
```
prefix=/usr
libdir=/usr//usr/lib
includedir=/usr/include
CXX=/usr/lib/ccache/bin/g++
CC=/usr/lib/ccache/bin/cc
DEPENDENCIES=/usr/lib/libtinyxml.so
Name: kodiplatform
Description: Kodi add-on platform support library 18.0
Version: 18.0
Libs: -L -l:kodiplatform -ltinyxml
Cflags: -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -g -std=c++11 -fPIC
```
for native builds, the issue is that `/usr//usr/lib` appears at all. I would attribute it to `-DCMAKE_INSTALL_LIBDIR=/usr/lib`.
next prev parent reply other threads:[~2021-02-18 6:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 20:33 [PR PATCH] " ndowens
2021-01-01 20:34 ` [PR PATCH] [Updated] " ndowens
2021-01-03 1:14 ` [PR PATCH] [Updated] [WIP]kodi-platform: " ndowens
2021-01-03 1:15 ` ndowens
2021-01-03 1:15 ` [PR PATCH] [Closed]: " ndowens
2021-01-03 1:15 ` ndowens
2021-01-03 1:19 ` [PR PATCH] [Updated] " ndowens
2021-01-03 1:19 ` ndowens
2021-01-03 1:30 ` [PR PATCH] [Updated] " ndowens
2021-01-03 1:32 ` ndowens
2021-01-03 1:36 ` ndowens
2021-01-03 2:39 ` [PR PATCH] [Updated] " ndowens
2021-01-03 2:48 ` ndowens
2021-02-18 6:46 ` [PR REVIEW] kodi-platform: " ericonr
2021-02-18 6:46 ` ericonr [this message]
2021-03-16 21:03 ` ericonr
2021-03-16 21:03 ` [PR PATCH] [Closed]: " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210218064614.tr8uBtqaX3mcw1boeuTE7NYR7rwjcrD8QjZqfmoz2C4@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).