Marcus Denker writes:
On 24.09.2008, at 23:16, <bryce@kampjes.demon.co.uk> <bryce@kampjes.demon.co.uk
wrote:
I've stabilised the changes I was working on so now's a reasonable time for me to look at this if it's still required. Is it?
For now, I just used the vm from the seaside package and copied all th dll's in from the freetype package. This seems to work...
The recompiling gets really more important as soon as we go for example for Eliot's closure implementation... that I would want to have in as soon as possible.
OK, then my plan is this: 1) Build a VM dev environment with the latest mainstream source 2) Merge in Exupery 3) Add TrueType support 4) Automate the image build using Universes. (Probably starting with one of Damien's pharo-dev images) 4.5) Look at the makefiles (Igor's post) 5) Document the C setup 6) Review where I'm at 7) Review Eliot's closure impementation 8) Merge them assuming no problems My aim here is to make sure that the image used to build the VM is automatically buildable. I'll leave automating the C sources for later. This is where Exupery VM building currently is. Eliot's changes shouldn't effect build automation as I'll merge them into the Exupery VMMaker if they're acceptable. Exupery's VMMaker source is on SqueakSource Bryce P.S. Marcus, if you don't have the bitblit extensions then you'll not be getting sub-pixel aliasing. So with a re-built VM the fonts should look slightly nicer.