From: LRN <lrn1986@gmail.com>
To: libffi-discuss@sourceware.org
Subject: Re: VS2015 build of libffi?
Date: Thu, 04 Aug 2016 12:24:00 -0000 [thread overview]
Message-ID: <b71c8e39-674a-0370-9d85-fa5e0fca626b@gmail.com> (raw)
In-Reply-To: <F793DE7E-A5CC-43DE-842D-052F5BC550CB@vvi.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 740 bytes --]
On 04.08.2016 15:13, Ed VanVliet wrote:
> Is there a prescribed way to build (or use) libffi for x86 and x64 using visual studio 2015? Noting that VS2015 has the clang front end (which I don’t think existed in 2014).
Not being libffi crew, i would still like to point out 2 things:
1) libffi is a hard dependency for GTK+ stack, and GTK+ stack is known to
be reliably buildable with MSVS.
2) Threre are meson[1] build definitions[2] for libffi, and meson has some
support for MSVS projects (although i would probably guess that ninja +
cl.exe is better supported, but that's just a guess)
[1] http://mesonbuild.com/
[2] https://github.com/mesonbuild/libffi
--
O< ascii ribbon - stop html email! - www.asciiribbon.org
[-- Attachment #1.1.2: 0x6759BA74.asc --]
[-- Type: application/pgp-keys, Size: 3540 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-04 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 12:13 Ed VanVliet
2016-08-04 12:24 ` LRN [this message]
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=b71c8e39-674a-0370-9d85-fa5e0fca626b@gmail.com \
--to=lrn1986@gmail.com \
--cc=libffi-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).