[Pharo-project] Do you still need a Linux VM with FreeType?
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? Exupery already needs VMs for all major platforms, so I'm thinking about merging that requirement with what Pharo needs. I can build Linux VMs easily as it's my main development platform. Other platforms depend on time, so far development has been more important than maintaining ports for me. Bryce
2008/9/25 <bryce@kampjes.demon.co.uk>:
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?
Exupery already needs VMs for all major platforms, so I'm thinking about merging that requirement with what Pharo needs. I can build Linux VMs easily as it's my main development platform. Other platforms depend on time, so far development has been more important than maintaining ports for me.
Hi Bryce, i'm already added platform source for linux. You can see it on https://gforge.inria.fr/frs/?group_id=1299 page. I would appreciate if you help how to add dependency in linker (to link with -lfreetype) , if plugin is compiled in. Otherwise it require to change a makefile to complete a build. Btw, same for B3DAcceleratorPlugin - it needs adding -lgl
Bryce
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
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. Marcus -- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker
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.
So marcus focus on that and let us deal with crap removal. The list you gave is good. I think that this is important to turn the TODO into issue (may be you did that) so that people can focus on one task. Stef
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.
Igor Stasenko writes:
Hi Bryce, i'm already added platform source for linux. You can see it on https://gforge.inria.fr/frs/?group_id=1299 page. I would appreciate if you help how to add dependency in linker (to link with -lfreetype) , if plugin is compiled in. Otherwise it require to change a makefile to complete a build. Btw, same for B3DAcceleratorPlugin - it needs adding -lgl
If you're trying to do Linux builds frequently you might want to look at VirtualBox or other virtualisation software. I'm using VirtualBox here to run Windows from Linux, according to the website, it should run Linux from Windows as well. It's free. Rebooting between OSes gets tedious fast. Bryce
Marcus Denker writes:
On 24.09.2008, at 23:16, <bryce@kampjes.demon.co.uk> <bryce@kampjes.demon.co.uk 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.
What platforms do you have to work with? The Linux build now runs. I've a few loose ends to tidy up. I still haven't finished reviewing the changes. Bryce
bryce@kampjes.demon.co.uk writes:
Marcus Denker writes:
On 24.09.2008, at 23:16, <bryce@kampjes.demon.co.uk> <bryce@kampjes.demon.co.uk 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.
What platforms do you have to work with? The Linux build now runs. I've a few loose ends to tidy up. I still haven't finished reviewing the changes.
Sorry, I should have added, I'd prefer not to integrate the image changes. Someone else should be able to do that. Bryce
participants (4)
-
bryce＠kampjes.demon.co.uk -
Igor Stasenko -
Marcus Denker -
Stéphane Ducasse