* VS2015 build of libffi?
@ 2016-08-04 12:13 Ed VanVliet
2016-08-04 12:24 ` LRN
0 siblings, 1 reply; 2+ messages in thread
From: Ed VanVliet @ 2016-08-04 12:13 UTC (permalink / raw)
To: libffi-discuss
Dear libffi crew,
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).
Sincerely,
Ed
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: VS2015 build of libffi?
2016-08-04 12:13 VS2015 build of libffi? Ed VanVliet
@ 2016-08-04 12:24 ` LRN
0 siblings, 0 replies; 2+ messages in thread
From: LRN @ 2016-08-04 12:24 UTC (permalink / raw)
To: libffi-discuss
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-08-04 12:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-04 12:13 VS2015 build of libffi? Ed VanVliet
2016-08-04 12:24 ` LRN
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).