I think that I screwed up the MC parenting for this, sorry for that. My intent is to temporarily bypass Freetype-Plugin-eem.70 until compilation issues can be resolved.

Freetype-plugin-dtl.71.mcz (this update) is identical to FreetypePlugin-eem.69.mcz. The updates in Freetype-Plugin-eem-70.mcz do not yet compile in VMM trunk, and the plugin has been excluded from oscog, so the Freetype-Plugin-eem70.mcz changes should be reapplied when those issues are resolved.

Sorry for the confusion, I should pay closer attention when the Adopt button in the MC browser says "do not do this unless you know what you are doing".

Dave

On Wed, Apr 30, 2014 at 03:07:32AM +0000, squeak-dev-noreply@lists.squeakfoundation.org wrote:

Dave Lewis uploaded a new version of Freetype-Plugin to project FT2Plugin for Freetype: http://www.squeaksource.com/FreetypePlugin/Freetype-Plugin-dtl.71.mcz

==================== Summary ====================

Name: Freetype-Plugin-dtl.71 Author: dtl Time: 29 April 2014, 10:02:21.108 pm UUID: 6329a996-8fa7-4097-bed4-f1e62c9a1445 Ancestors: Freetype-Plugin-eem.70

Temporarily hold back Freetype-Plugin-eem.70, to be reapplied when compilation issues are resolved. Updates through Freetype-Plugin-eem.69 compile cleanly in VMM trunk, changes for Cog are on hold as per:

Name: VMMaker.oscog-eem.687 Author: eem Time: 28 April 2014, 2:56:03.445 pm UUID: 501501b0-dad7-4305-b25e-96ed74c92fd2 Ancestors: VMMaker.oscog-eem.686

Fix source paths in the Squeak VM config. Exclude the FT2Plugin; it's not robust enough to load and generate yet.