From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: luv-1.30.1.0
Date: Mon, 16 Sep 2019 22:06:32 +0200 [thread overview]
Message-ID: <20190916200632.hTkqj6AVax0uibMDDKnLHbsRg-RMJjhIflp2EtBum_I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13648@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
New comment by andry-dev on void-packages repository
https://github.com/void-linux/void-packages/pull/13648#issuecomment-531927892
Comment:
I __think__ it should be possible to build it as a module, I have to check the CMakeLists.txt again (the last time I did that was in August, so I don't remember every option; it's kinda complicated if you take a look at it)
Now I'll fix the two comments and investigate the CMakeLists
Update: Looking at it and I don't think it's feasible, the includes are not exported when built as a module (so this breaks neovim builds)
I made this package to compile neovim 0.4 (the nightly at the time) and the module worked when called inside a Lua block (this is neovim, I don't know how they export the library to users)
Maybe it's possible to create a separate package just for the module?
next prev parent reply other threads:[~2019-09-16 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13648@inbox.vuxu.org>
2019-09-15 22:39 ` [PR PATCH] [Updated] New package: libluv-1.30.1 voidlinux-github
2019-09-15 22:39 ` voidlinux-github
2019-09-16 17:15 ` [PR PATCH] [Updated] New package: luv-1.30.1.0 voidlinux-github
2019-09-16 17:15 ` voidlinux-github
2019-09-16 19:42 ` voidlinux-github
2019-09-16 20:06 ` voidlinux-github [this message]
2019-09-16 20:08 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-16 20:08 ` voidlinux-github
2019-09-17 7:22 ` voidlinux-github
2019-09-17 8:59 ` voidlinux-github
2019-09-17 20:05 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-17 20:05 ` voidlinux-github
2019-09-19 17:10 ` voidlinux-github
2019-09-19 21:19 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-19 21:19 ` voidlinux-github
2019-09-19 21:22 ` voidlinux-github
2019-09-19 21:33 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-19 21:33 ` voidlinux-github
2019-09-19 21:46 ` voidlinux-github
2019-09-19 21:46 ` voidlinux-github
2019-09-20 17:20 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190916200632.hTkqj6AVax0uibMDDKnLHbsRg-RMJjhIflp2EtBum_I@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).