Re: fribidi and meson
John Emmas <[email protected]> Sun, 11 Mar 2018 11:54:51 +0000
| Newsgroups | gmane.comp.internationalization.fribidi |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============0153502471==
Content-Type: multipart/alternative;
boundary="------------030305050400050900090209"
This is a multi-part message in MIME format.
--------------030305050400050900090209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 11/03/2018 10:21, John Emmas wrote:
>
> Yes, the ones with glib dependencies are weird ('BidiTest.exe' and
> 'BidiCharacterTest.exe'). The 32-bit versions get built okay with
> VS2005 - but strangely, the Release builds try to link to Microsoft's
> Debug libraries and they then fail to run.
>
Okay, I got a bit further with this and discovered 2 things...
1) AFAICT I do need to specify "--buildtype debug" or "--buildtype
release" for each build. If I leave that instruction out, the generated
manifest seems to link arbitrarily to either the MS DebugCRT or the
ReleaseCRT (maybe it just repeats the previous setting?)
2) For 'BidiTest.exe' and 'BidiCharacterTest.exe" the built exe's won't
run unless I use Microsoft's "mt" application to embed those manifests.
To be honest, that doesn't surprise me. What does surprise me is that
the other built executables DO run - even without a manifest embedded!!
Anyway... having taken the above steps I can now run both my Debug
builds of 'BidiTest.exe' and 'BidiCharacterTest.exe" and also their
Release builds and in each case, both programs show me this output:-
No errors found! :-)
(and in all cases, that's building with VS2005). I still can't make
those particular exe's build with VS2015... :-(
John
--------------030305050400050900090209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/03/2018 10:21, John Emmas wrote:<br>
</div>
<blockquote cite="mid:[email protected]"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix"><br>
</div>
Yes, the ones with glib dependencies are weird ('BidiTest.exe' and
'BidiCharacterTest.exe'). The 32-bit versions get built okay with
VS2005 - but strangely, the Release builds try to link to
Microsoft's Debug libraries and they then fail to run.<br>
<br>
</blockquote>
<br>
Okay, I got a bit further with this and discovered 2 things...<br>
<br>
1) AFAICT I do need to specify "--buildtype debug" or "--buildtype
release" for each build. If I leave that instruction out, the
generated manifest seems to link arbitrarily to either the MS
DebugCRT or the ReleaseCRT (maybe it just repeats the previous
setting?)<br>
<br>
2) For 'BidiTest.exe' and 'BidiCharacterTest.exe" the built exe's
won't run unless I use Microsoft's "mt" application to embed those
manifests. To be honest, that doesn't surprise me. What does
surprise me is that the other built executables DO run - even
without a manifest embedded!!<br>
<br>
Anyway... having taken the above steps I can now run both my Debug
builds of 'BidiTest.exe' and 'BidiCharacterTest.exe" and also their
Release builds and in each case, both programs show me this output:-<br>
<br>
No errors found! :-)<br>
<br>
(and in all cases, that's building with VS2005). I still can't make
those particular exe's build with VS2015... :-(<br>
<br>
John<br>
</body>
</html>
--------------030305050400050900090209--
--===============0153502471==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZnJpYmlkaSBt
YWlsaW5nIGxpc3QKZnJpYmlkaUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m
cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmliaWRpCg==
--===============0153502471==--