Github messages for voidlinux
 help / color / mirror / Atom feed
From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: xnotify-0.5.0
Date: Wed, 28 Apr 2021 17:07:24 +0200	[thread overview]
Message-ID: <20210428150724.9PMg-p8rtDKFHTAg-SkXggsocnL9IjiKowZsMjU0f_4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25035@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

New comment by natrys on void-packages repository

https://github.com/void-linux/void-packages/pull/25035#issuecomment-828533311

Comment:
hi @biopsin do you mean:

```
make_build_args="LOCALINC=${XBPS_CROSS_BASE}/usr/include
 LOCALLIB=${XBPS_CROSS_BASE}/usr/lib
 FREETYPEINC=${XBPS_CROSS_BASE}/usr/include/freetype2
 X11INC=${XBPS_CROSS_BASE}/usr/include/X11
 LDFLAGS+=\$(LIBS) CFLAGS+=\$(INCS)"
```

This works but I feel like this is more indirect and implicit than just setting up CFLAGS/LDFLAGS directly which is the desired effect.

```
CFLAGS="-I${XBPS_CROSS_BASE}/usr/include"
CFLAGS+=" -I${XBPS_CROSS_BASE}/usr/include/X11"
CFLAGS+=" -I${XBPS_CROSS_BASE}/usr/include/freetype2"
LDFLAGS="-lfontconfig -lXft -lXinerama -lX11 -lImlib2"
```

Perhaps @ericonr can weigh in.

  parent reply	other threads:[~2021-04-28 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 20:30 [PR PATCH] New package: xnotify-0.3.1 natrys
2020-09-22 20:40 ` natrys
2020-09-29  6:30 ` [PR PATCH] [Updated] " natrys
2021-04-28 11:36 ` New package: xnotify-0.5.0 biopsin
2021-04-28 15:01 ` [PR PATCH] [Updated] " natrys
2021-04-28 15:07 ` natrys [this message]
2021-04-28 16:17 ` New package: xnotify-0.8.1 ericonr
2021-04-28 16:40 ` [PR PATCH] [Updated] " natrys
2021-04-28 16:44 ` natrys
2022-04-19  2:12 ` github-actions
2022-04-19 17:33 ` [PR PATCH] [Closed]: " natrys

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=20210428150724.9PMg-p8rtDKFHTAg-SkXggsocnL9IjiKowZsMjU0f_4@z \
    --to=natrys@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).