From: "Wiktor Żelazny" <wz@freeshell.de>
To: 57337@debbugs.gnu.org
Cc: ludo@gnu.org
Subject: [bug#57337] [v2 0/2] Add docxbox
Date: Mon, 26 Dec 2022 15:57:30 +0100 [thread overview]
Message-ID: <20221226145732.1237-1-wz@freeshell.de> (raw)
In-Reply-To: <20220822092753.31295-1-wz@freeshell.de>
From: wzel <wzel@users.noreply.github.com>
Hi there,
Some pending issues:
1. For miniz-cpp, I tried and failed
(arguments
'(#:install-plan
#~'(("zip_file.hpp" "include/")
("README.md" #$(string-append "share/doc/" name "-" version "/"))
("examples" #$(string-append "share/doc/" name "-" version "/")))))
, as this results in unknown gexp variable error.
2. For docxbox, I had to keep (package-source tinyxml2). This is
because, as I understand it, docxbox does not link to the compiled
library, and given my zero cmake experience I have no idea how to modify
the build process so that it does. Instead, it does what is described in
https://github.com/leethomason/tinyxml2 readme.md:
TinyXML-2 is designed to be easy and fast to learn. It is one header
and one cpp file. Simply add these to your project and off you go.
3. For docxbox, (file-name (git-file-name name version)) is not crashing
the build, anymore, but strangely during build --rounds=2 --check I
noticed four rounds taking place instead of two.
Thanks for taking a look,
WŻ
Wiktor Żelazny (2):
gnu: Add miniz-cpp.
gnu: Add docxbox.
gnu/local.mk | 1 +
gnu/packages/cpp.scm | 35 +
.../miniz-cpp-fixed-duplicated-symbols.patch | 2734 +++++++++++++++++
gnu/packages/textutils.scm | 76 +-
4 files changed, 2845 insertions(+), 1 deletion(-)
create mode 100644 gnu/packages/patches/miniz-cpp-fixed-duplicated-symbols.patch
base-commit: c50cd1bbece27097456242f246f89c053e7cc1a2
--
2.38.1
next prev parent reply other threads:[~2022-12-26 14:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:27 [bug#57337] [PATCH 0/2] Add docxbox Wiktor Żelazny
2022-08-22 9:36 ` [bug#57337] [PATCH 1/2] gnu: Add miniz-cpp Wiktor Żelazny
2022-08-22 9:36 ` [bug#57337] [PATCH 2/2] gnu: Add docxbox Wiktor Żelazny
2022-09-08 12:49 ` [bug#57337] [PATCH 0/2] " Ludovic Courtès
2022-09-23 18:04 ` Wiktor Żelazny
2022-09-08 12:46 ` Ludovic Courtès
2022-09-23 17:46 ` Wiktor Żelazny
2022-09-08 12:44 ` Ludovic Courtès
2022-09-23 18:21 ` Wiktor Żelazny
2022-12-26 14:57 ` Wiktor Żelazny [this message]
2022-12-26 14:57 ` [bug#57337] [v2 1/2] gnu: Add miniz-cpp Wiktor Żelazny
2023-01-25 22:17 ` Ludovic Courtès
2022-12-26 14:57 ` [bug#57337] [v2 2/2] gnu: Add docxbox Wiktor Żelazny
2023-01-25 22:21 ` Ludovic Courtès
2023-01-28 19:50 ` Wiktor Żelazny
2023-02-05 20:18 ` [bug#57337] [PATCH v3 1/2] gnu: Add miniz-cpp Wiktor Żelazny
2023-02-05 20:18 ` [bug#57337] [PATCH v3 2/2] gnu: Add docxbox Wiktor Żelazny
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221226145732.1237-1-wz@freeshell.de \
--to=wz@freeshell.de \
--cc=57337@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).