From: "Michal Vlasák via ntg-context" <ntg-context@ntg.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: "Michal Vlasák" <lahcim8@gmail.com>
Subject: Re: zint module on LMTX
Date: Sun, 04 Sep 2022 14:23:27 +0200 [thread overview]
Message-ID: <CMNM48R6AKPK.2E42F61TDS512@phobos> (raw)
In-Reply-To: <6823c596-2bdf-2c44-11db-d30b1d49f2c9@freedom.nl>
On Sun Sep 4, 2022 at 1:25 PM CEST, Hans Hagen via ntg-context wrote:
> although i don't like top do it i cloned the zint repos and tried to
> compile (after migrating the proj file to vs2022) but it fails on some
> png.h file missing and i see no way to disable png)
Sorry, I don't have native windows compiler to test, but the options you
probably want with zint's cmake are:
-DZINT_USE_PNG=OFF -DZINT_USE_QT=OFF
For example I use:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release -DZINT_USE_PNG=OFF -DZINT_USE_QT=OFF
from the root of repository. IIRC older versions may not support
-S for source directory and -B for build directory so something like you
had can be used:
mkdir build
cd build
cmake -DZINT_USE_PNG=OFF -DZINT_USE_QT=OFF ..
The ZINT_USE_PNG cmake option decides whether to pass -DNO_PNG to the
compiler. In my repository I don't use zint's cmake at all, and compile
the files manually (though also with cmake), and I set NO_PNG
unconditionally:
https://github.com/vlasakm/context-optional-libraries/blob/12085e89688332d2d672471ea47ef9a2c066a14f/CMakeLists.txt#L58
On Sun Sep 4, 2022 at 1:43 PM CEST, Hans Hagen via ntg-context wrote:
> For some reason i get
>
> CMake Error: Unknown argument --toolchain
>
For older versions following should work:
-DCMAKE_TOOLCHAIN_FILE=cross-windows.cmake
instead of the newer:
--toolchain cross-windows.cmake
Michal
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-09-04 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.272.1662280561.1198.ntg-context@ntg.nl>
2022-09-04 9:59 ` Ivan Pešić via ntg-context
2022-09-04 10:59 ` Michal Vlasák via ntg-context
2022-09-04 11:27 ` Hans Hagen via ntg-context
2022-09-04 11:43 ` Hans Hagen via ntg-context
2022-09-04 11:25 ` Hans Hagen via ntg-context
2022-09-04 12:23 ` Michal Vlasák via ntg-context [this message]
[not found] <mailman.0.1662285601.13547.ntg-context@ntg.nl>
2022-09-04 12:53 ` Ivan Pešić via ntg-context
[not found] <mailman.2658.1647466369.1172.ntg-context@ntg.nl>
2022-09-03 23:36 ` Ivan Pešić via ntg-context
2022-09-04 8:51 ` Hans Hagen via ntg-context
2022-03-16 16:37 Pablo Rodriguez via ntg-context
2022-03-16 17:05 ` Hans Hagen via ntg-context
2022-03-16 18:11 ` Adam Reviczky via ntg-context
2022-03-16 21:32 ` Pablo Rodriguez via ntg-context
2022-03-16 23:04 ` Adam Reviczky via ntg-context
2022-03-17 15:26 ` Pablo Rodriguez via ntg-context
2022-03-25 10:43 ` Lutz Haseloff via ntg-context
2022-03-16 18:12 ` Pablo Rodriguez via ntg-context
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=CMNM48R6AKPK.2E42F61TDS512@phobos \
--to=ntg-context@ntg.nl \
--cc=lahcim8@gmail.com \
/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).