well⦠Latest VM is intended to work with latest Pharo, not with older versions. Latest VM is *always* an experimental/unstable VM that needs to be considered⦠that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). BTW⦠Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) Said that⦠I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. Esteban
On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak@gmail.com> wrote:
The new "fixed" compactor VM has broken FT...
So any text drawn on Athens canvas results in red cross...
Error in...
CairoFontFace class>>primFtFace:loadFlags:
'Unable to find function address'
Apparently because someone renamed libfreetype-6.dll to libfreetype.dll
(Windows VM latest, Pharo 5)