Hello, i updated the ConfigurationOfCog and added verison 2.3 which now also loads freetype plugin into vmmaker image. I also made sure that plugin automatically builds on macs (no other platforms yet) and included it by default into CMakeVMMaker configs. There was some hiccups, i had to deal with: The autoconf toolchain (or most probably the configuration scripts for freetype library) don't like the spaces in path. So i have to rename all jobs on Hudson to avoid using spaces (because hudson creating a subdirectory for jobs with same name). The renamed jobs are: https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Cocoa/ https://pharo-ic.lille.inria.fr/hudson/job/CogMT-Mac-Cocoa/ https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Cocoa/ There is another idiosyncrasy: outdated toolchain for autoconf. I had to install mac ports on slave server. See http://code.google.com/p/cog/wiki/FT2Plugin for details. ( i tested Carbon builds, now they are including FT2Plugin). Esteban, could you please verify that it also works for Cocoa configs? I changed configs to include FT2Plugin by default in Cocoa configs as well, but i haven't tested builds. So, currently following builds should contain FT2Plugin by default: https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ Freetype library are built from scratch by downloading library sources directly from git repository (maybe its a bit too much, but it works). See /unixbuild/FT2Plugin/makeFreetype.sh this script is then used by cmake config to build libfreetype.a which is statically linked with freetype plugin. -- Best regards, Igor Stasenko AKA sig. |
This is the engineering I like to hear in Software Engineering: make the machines do it for us. Tx Igor. Soon we will be able to focus on more creative parts. Stef On Jul 5, 2011, at 5:04 PM, Igor Stasenko wrote: > > Hello, > > i updated the ConfigurationOfCog and added verison 2.3 which now also > loads freetype plugin into vmmaker image. > > I also made sure that plugin automatically builds on macs (no other > platforms yet) and included it by default into CMakeVMMaker configs. > > There was some hiccups, i had to deal with: > The autoconf toolchain (or most probably the configuration scripts for > freetype library) don't like the spaces in path. > So i have to rename all jobs on Hudson to avoid using spaces (because > hudson creating a subdirectory for jobs with same name). > > The renamed jobs are: > https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ > https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Cocoa/ > https://pharo-ic.lille.inria.fr/hudson/job/CogMT-Mac-Cocoa/ > https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ > https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Cocoa/ > > There is another idiosyncrasy: outdated toolchain for autoconf. > I had to install mac ports on slave server. > See > http://code.google.com/p/cog/wiki/FT2Plugin > for details. > > ( i tested Carbon builds, now they are including FT2Plugin). > > Esteban, could you please verify that it also works for Cocoa configs? > I changed configs to include FT2Plugin by default in Cocoa configs as > well, > but i haven't tested builds. > > So, currently following builds should contain FT2Plugin by default: > > https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ > https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ > > Freetype library are built from scratch by downloading library sources > directly from git repository (maybe its a bit too much, but it works). > See /unixbuild/FT2Plugin/makeFreetype.sh > > this script is then used by cmake config to build libfreetype.a which > is statically linked with freetype plugin. > > -- > Best regards, > Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
On 5 July 2011 17:04, Igor Stasenko <[hidden email]> wrote: > Hello, > > i updated the ConfigurationOfCog and added verison 2.3 which now also > loads freetype plugin into vmmaker image. > > I also made sure that plugin automatically builds on macs (no other > platforms yet) and included it by default into CMakeVMMaker configs. > > There was some hiccups, i had to deal with: > The autoconf toolchain (or most probably the configuration scripts for > freetype library) don't like the spaces in path. > So i have to rename all jobs on Hudson to avoid using spaces (because > hudson creating a subdirectory for jobs with same name). > > The renamed jobs are: > https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ > https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Cocoa/ > https://pharo-ic.lille.inria.fr/hudson/job/CogMT-Mac-Cocoa/ > https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ > https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Cocoa/ > > There is another idiosyncrasy: outdated toolchain for autoconf. > I had to install mac ports on slave server. > See > http://code.google.com/p/cog/wiki/FT2Plugin > for details. > > ( i tested Carbon builds, now they are including FT2Plugin). > > Esteban, could you please verify that it also works for Cocoa configs? > I changed configs to include FT2Plugin by default in Cocoa configs as > well, > but i haven't tested builds. > > So, currently following builds should contain FT2Plugin by default: > > https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ > https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ > > Freetype library are built from scratch by downloading library sources > directly from git repository (maybe its a bit too much, but it works). > See /unixbuild/FT2Plugin/makeFreetype.sh > it is in /macbuild/FT2Plugin/makeFreetype.sh apparently... > this script is then used by cmake config to build libfreetype.a which > is statically linked with freetype plugin. > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
On Tue, Jul 5, 2011 at 5:04 PM, Igor Stasenko <[hidden email]> wrote:
Hi Igor. You have been working so much that I am now lost ;) are all those jobs already building from blessed? There is another idiosyncrasy: outdated toolchain for autoconf. Would that mean that http://code.google.com/p/pharo/issues/detail?id=4374 is fixed? because last comment of Alain says it is not. Esteban, could you please verify that it also works for Cocoa configs? -- Mariano http://marianopeck.wordpress.com |
One more question, how did you load COnfigurationOfCog in latest pharo 1.3 if there is still the problem of the dependency to AbstractLauncher ? In an interactive image I can do proceed but how do you solve that in Hudson? On Wed, Jul 6, 2011 at 9:44 AM, Mariano Martinez Peck <[hidden email]> wrote:
-- Mariano http://marianopeck.wordpress.com |
In reply to this post by Mariano Martinez Peck
On 6 July 2011 09:44, Mariano Martinez Peck <[hidden email]> wrote: > > > > On Tue, Jul 5, 2011 at 5:04 PM, Igor Stasenko <[hidden email]> wrote: >> >> Hello, >> >> i updated the ConfigurationOfCog and added verison 2.3 which now also >> loads freetype plugin into vmmaker image. >> >> I also made sure that plugin automatically builds on macs (no other >> platforms yet) and included it by default into CMakeVMMaker configs. >> >> There was some hiccups, i had to deal with: >> The autoconf toolchain (or most probably the configuration scripts for >> freetype library) don't like the spaces in path. >> So i have to rename all jobs on Hudson to avoid using spaces (because >> hudson creating a subdirectory for jobs with same name). >> >> The renamed jobs are: >> https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ >> https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Cocoa/ >> https://pharo-ic.lille.inria.fr/hudson/job/CogMT-Mac-Cocoa/ >> https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ >> https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Cocoa/ >> > > Hi Igor. You have been working so much that I am now lost ;) > are all those jobs already building from blessed? > Yes. >> >> There is another idiosyncrasy: outdated toolchain for autoconf. >> I had to install mac ports on slave server. >> See >> http://code.google.com/p/cog/wiki/FT2Plugin >> for details. >> >> ( i tested Carbon builds, now they are including FT2Plugin). >> > > Would that mean that http://code.google.com/p/pharo/issues/detail?id=4374 is fixed? because last comment of Alain says it is not. > I just tested to build VMs using latest configs: everything works perfectly. It runs well by building either as external or as internal. Maybe Alain used outdated/wrong CMakeVMMaker version? > >> >> Esteban, could you please verify that it also works for Cocoa configs? >> I changed configs to include FT2Plugin by default in Cocoa configs as >> well, >> but i haven't tested builds. >> >> So, currently following builds should contain FT2Plugin by default: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ >> https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ >> >> Freetype library are built from scratch by downloading library sources >> directly from git repository (maybe its a bit too much, but it works). >> See /unixbuild/FT2Plugin/makeFreetype.sh >> >> this script is then used by cmake config to build libfreetype.a which >> is statically linked with freetype plugin. >> >> -- >> Best regards, >> Igor Stasenko AKA sig. > > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
Hi, El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: > Freetype library are built from scratch by downloading library sources > directly from git repository (maybe its a bit too much, but it works). > See /unixbuild/FT2Plugin/makeFreetype.sh > > this script is then used by cmake config to build libfreetype.a which > is statically linked with freetype plugin. > sorry, this is very unclear for me how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? cheers, Esteban |
In reply to this post by Mariano Martinez Peck
On 6 July 2011 10:10, Mariano Martinez Peck <[hidden email]> wrote: > > One more question, how did you load COnfigurationOfCog in latest pharo 1.3 if there is still the problem of the dependency to AbstractLauncher ? > In an interactive image I can do proceed but how do you solve that in Hudson? > It loads because automatic build system, when building VMMaker image, just ignores all warnings and forcely loads stuff. And if you do it manually, it will show you all those warnings, which you must click to continue. Yes, we should add the AbstractLauncher to the compatibility package. But it is not critical, since code generation not depending on that. > On Wed, Jul 6, 2011 at 9:44 AM, Mariano Martinez Peck <[hidden email]> wrote: >> >> >> On Tue, Jul 5, 2011 at 5:04 PM, Igor Stasenko <[hidden email]> wrote: >>> >>> Hello, >>> >>> i updated the ConfigurationOfCog and added verison 2.3 which now also >>> loads freetype plugin into vmmaker image. >>> >>> I also made sure that plugin automatically builds on macs (no other >>> platforms yet) and included it by default into CMakeVMMaker configs. >>> >>> There was some hiccups, i had to deal with: >>> The autoconf toolchain (or most probably the configuration scripts for >>> freetype library) don't like the spaces in path. >>> So i have to rename all jobs on Hudson to avoid using spaces (because >>> hudson creating a subdirectory for jobs with same name). >>> >>> The renamed jobs are: >>> https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ >>> https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Cocoa/ >>> https://pharo-ic.lille.inria.fr/hudson/job/CogMT-Mac-Cocoa/ >>> https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ >>> https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Cocoa/ >>> >> >> Hi Igor. You have been working so much that I am now lost ;) >> are all those jobs already building from blessed? >> >>> >>> There is another idiosyncrasy: outdated toolchain for autoconf. >>> I had to install mac ports on slave server. >>> See >>> http://code.google.com/p/cog/wiki/FT2Plugin >>> for details. >>> >>> ( i tested Carbon builds, now they are including FT2Plugin). >>> >> >> Would that mean that http://code.google.com/p/pharo/issues/detail?id=4374 is fixed? because last comment of Alain says it is not. >> >> >>> >>> Esteban, could you please verify that it also works for Cocoa configs? >>> I changed configs to include FT2Plugin by default in Cocoa configs as >>> well, >>> but i haven't tested builds. >>> >>> So, currently following builds should contain FT2Plugin by default: >>> >>> https://pharo-ic.lille.inria.fr/hudson/job/Cog-Mac-Carbon/ >>> https://pharo-ic.lille.inria.fr/hudson/job/StackVM-Mac-Carbon/ >>> >>> Freetype library are built from scratch by downloading library sources >>> directly from git repository (maybe its a bit too much, but it works). >>> See /unixbuild/FT2Plugin/makeFreetype.sh >>> >>> this script is then used by cmake config to build libfreetype.a which >>> is statically linked with freetype plugin. >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by EstebanLM
On 6 July 2011 14:56, Esteban Lorenzano <[hidden email]> wrote: > > Hi, > > El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: > >> Freetype library are built from scratch by downloading library sources >> directly from git repository (maybe its a bit too much, but it works). >> See /unixbuild/FT2Plugin/makeFreetype.sh >> >> this script is then used by cmake config to build libfreetype.a which >> is statically linked with freetype plugin. >> > > sorry, this is very unclear for me > how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? > The argument is where to copy the resulting libfreetype.a file. But see MacOSConfig>>configureFT2Plugin: maker it is used there. It should work with cocoa builds without any changes. So, just try to build it and see what happens :) > cheers, > Esteban -- Best regards, Igor Stasenko AKA sig. |
hi, yes... this is another case of "premature questioning" :) now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? is a port? cheers, Esteban El 06/07/2011, a las 9:59a.m., Igor Stasenko escribió: > > On 6 July 2011 14:56, Esteban Lorenzano <[hidden email]> wrote: >> >> Hi, >> >> El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: >> >>> Freetype library are built from scratch by downloading library sources >>> directly from git repository (maybe its a bit too much, but it works). >>> See /unixbuild/FT2Plugin/makeFreetype.sh >>> >>> this script is then used by cmake config to build libfreetype.a which >>> is statically linked with freetype plugin. >>> >> >> sorry, this is very unclear for me >> how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? >> > > The argument is where to copy the resulting libfreetype.a file. > > But see > > MacOSConfig>>configureFT2Plugin: maker > > it is used there. > It should work with cocoa builds without any changes. > So, just try to build it and see what happens :) > >> cheers, >> Esteban > > -- > Best regards, > Igor Stasenko AKA sig. |
On 6 July 2011 15:06, Esteban Lorenzano <[hidden email]> wrote: > > hi, > yes... this is another case of "premature questioning" :) > now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? > is a port? > yes, please read the http://code.google.com/p/cog/wiki/FT2Plugin (looks like you asked another premature question ;) > cheers, > Esteban > > El 06/07/2011, a las 9:59a.m., Igor Stasenko escribió: > >> >> On 6 July 2011 14:56, Esteban Lorenzano <[hidden email]> wrote: >>> >>> Hi, >>> >>> El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: >>> >>>> Freetype library are built from scratch by downloading library sources >>>> directly from git repository (maybe its a bit too much, but it works). >>>> See /unixbuild/FT2Plugin/makeFreetype.sh >>>> >>>> this script is then used by cmake config to build libfreetype.a which >>>> is statically linked with freetype plugin. >>>> >>> >>> sorry, this is very unclear for me >>> how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? >>> >> >> The argument is where to copy the resulting libfreetype.a file. >> >> But see >> >> MacOSConfig>>configureFT2Plugin: maker >> >> it is used there. >> It should work with cocoa builds without any changes. >> So, just try to build it and see what happens :) >> >>> cheers, >>> Esteban >> >> -- >> Best regards, >> Igor Stasenko AKA sig. > > -- Best regards, Igor Stasenko AKA sig. |
On Wed, Jul 6, 2011 at 3:08 PM, Igor Stasenko <[hidden email]> wrote:
Igor: if I understand correctly, there is something extra we should do now while building the VM (this stuff about FT2Plugin). Since Pharo does not use FT2Plugin by default since Pharo 1.0 what abut letting the default plugins as easier as possible for people trying to build VMs? for those that want FT2Plugin then they can easily do it. Even Hudson can be configured to do: | config |
-- Mariano http://marianopeck.wordpress.com |
+1 El 06/07/2011, a las 10:22a.m., Mariano Martinez Peck escribió:
|
In reply to this post by Mariano Martinez Peck
On 6 July 2011 15:22, Mariano Martinez Peck <[hidden email]> wrote: > > > > On Wed, Jul 6, 2011 at 3:08 PM, Igor Stasenko <[hidden email]> wrote: >> >> On 6 July 2011 15:06, Esteban Lorenzano <[hidden email]> wrote: >> > >> > hi, >> > yes... this is another case of "premature questioning" :) >> > now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? >> > is a port? >> > >> yes, please read the http://code.google.com/p/cog/wiki/FT2Plugin >> (looks like you asked another premature question ;) >> > > Igor: if I understand correctly, there is something extra we should do now while building the VM (this stuff about FT2Plugin). Since Pharo does not use FT2Plugin by default since Pharo 1.0 what abut letting the default plugins as easier as possible for people trying to build VMs? for those that want FT2Plugin then they can easily do it. Even Hudson can be configured to do: > > | config | > config := CogUnixConfig new. > config externalPlugins: (config externalPlugins copyWith: #MyHackyFirstPlugin). > config generateWithSources. > you don't want freetype plugin to be there by default in configs? Okay, i will change that. But i think freetype is mustbe. As well as OSProcessPlugin. Maybe not in configs by default, but in hudson builds. -- Best regards, Igor Stasenko AKA sig. |
On Wed, Jul 6, 2011 at 4:23 PM, Igor Stasenko <[hidden email]> wrote:
exactly :) But it is just my thought. Change it only if you agree ;) Okay, i will change that. Exactly that was my point: why to add by default a plugin which is not used since 2 years by default and adds problems or extra work? So, -1 to put it in #defaultInternalPlugins or #defaultExternalPlugins and +1 tu set Hudson to add it. If OSProcessPlugin is easy to compile as the rest of the plugins, then I don't care to add it to #defaultXXXPlugins. -- -- Mariano http://marianopeck.wordpress.com |
On 6 July 2011 16:27, Mariano Martinez Peck <[hidden email]> wrote: > > > > On Wed, Jul 6, 2011 at 4:23 PM, Igor Stasenko <[hidden email]> wrote: >> >> On 6 July 2011 15:22, Mariano Martinez Peck <[hidden email]> wrote: >> > >> > >> > >> > On Wed, Jul 6, 2011 at 3:08 PM, Igor Stasenko <[hidden email]> wrote: >> >> >> >> On 6 July 2011 15:06, Esteban Lorenzano <[hidden email]> wrote: >> >> > >> >> > hi, >> >> > yes... this is another case of "premature questioning" :) >> >> > now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? >> >> > is a port? >> >> > >> >> yes, please read the http://code.google.com/p/cog/wiki/FT2Plugin >> >> (looks like you asked another premature question ;) >> >> >> > >> > Igor: if I understand correctly, there is something extra we should do now while building the VM (this stuff about FT2Plugin). Since Pharo does not use FT2Plugin by default since Pharo 1.0 what abut letting the default plugins as easier as possible for people trying to build VMs? for those that want FT2Plugin then they can easily do it. Even Hudson can be configured to do: >> > >> > | config | >> > config := CogUnixConfig new. >> > config externalPlugins: (config externalPlugins copyWith: #MyHackyFirstPlugin). >> > config generateWithSources. >> > >> >> you don't want freetype plugin to be there by default in configs? > > exactly :) > But it is just my thought. Change it only if you agree ;) > >> >> Okay, i will change that. >> >> But i think freetype is mustbe. As well as OSProcessPlugin. >> Maybe not in configs by default, but in hudson builds. >> > > Exactly that was my point: why to add by default a plugin which is not used since 2 years by default and adds problems or extra work? well, it is not used because we had problems with it. However guys who using pharo with other than latin-1 set of languages have no other options. I don't like that people had to copy a prebuilt plugin from other vms in order to make it work. We should ship it with VMs , so people could use it. > So, -1 to put it in #defaultInternalPlugins or #defaultExternalPlugins and +1 tu set Hudson to add it. Alright. I will make changes then. > If OSProcessPlugin is easy to compile as the rest of the plugins, then I don't care to add it to #defaultXXXPlugins. > Good thing that it doesn't requires third-party source code. It should be much easier to build. But also, multiple people wants it. And generally, if we could have this plugin in our vms by default, then we could run build(s) from image , without need to deal with tedious and bizarre shell scripting. -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
yes... I'm sorry. It was too early in the morning. Looks working here. I will integrate it to hudson builds now. cheers, Esteban El 06/07/2011, a las 10:08a.m., Igor Stasenko escribió: > > On 6 July 2011 15:06, Esteban Lorenzano <[hidden email]> wrote: >> >> hi, >> yes... this is another case of "premature questioning" :) >> now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? >> is a port? >> > yes, please read the http://code.google.com/p/cog/wiki/FT2Plugin > (looks like you asked another premature question ;) > >> cheers, >> Esteban >> >> El 06/07/2011, a las 9:59a.m., Igor Stasenko escribió: >> >>> >>> On 6 July 2011 14:56, Esteban Lorenzano <[hidden email]> wrote: >>>> >>>> Hi, >>>> >>>> El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: >>>> >>>>> Freetype library are built from scratch by downloading library sources >>>>> directly from git repository (maybe its a bit too much, but it works). >>>>> See /unixbuild/FT2Plugin/makeFreetype.sh >>>>> >>>>> this script is then used by cmake config to build libfreetype.a which >>>>> is statically linked with freetype plugin. >>>>> >>>> >>>> sorry, this is very unclear for me >>>> how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? >>>> >>> >>> The argument is where to copy the resulting libfreetype.a file. >>> >>> But see >>> >>> MacOSConfig>>configureFT2Plugin: maker >>> >>> it is used there. >>> It should work with cocoa builds without any changes. >>> So, just try to build it and see what happens :) >>> >>>> cheers, >>>> Esteban >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
btw... ConfigurationOfCog should load latest version of FT2Plugin, and it is not doing it... how your builds are working? El 06/07/2011, a las 10:08a.m., Igor Stasenko escribió: > > On 6 July 2011 15:06, Esteban Lorenzano <[hidden email]> wrote: >> >> hi, >> yes... this is another case of "premature questioning" :) >> now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? >> is a port? >> > yes, please read the http://code.google.com/p/cog/wiki/FT2Plugin > (looks like you asked another premature question ;) > >> cheers, >> Esteban >> >> El 06/07/2011, a las 9:59a.m., Igor Stasenko escribió: >> >>> >>> On 6 July 2011 14:56, Esteban Lorenzano <[hidden email]> wrote: >>>> >>>> Hi, >>>> >>>> El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: >>>> >>>>> Freetype library are built from scratch by downloading library sources >>>>> directly from git repository (maybe its a bit too much, but it works). >>>>> See /unixbuild/FT2Plugin/makeFreetype.sh >>>>> >>>>> this script is then used by cmake config to build libfreetype.a which >>>>> is statically linked with freetype plugin. >>>>> >>>> >>>> sorry, this is very unclear for me >>>> how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? >>>> >>> >>> The argument is where to copy the resulting libfreetype.a file. >>> >>> But see >>> >>> MacOSConfig>>configureFT2Plugin: maker >>> >>> it is used there. >>> It should work with cocoa builds without any changes. >>> So, just try to build it and see what happens :) >>> >>>> cheers, >>>> Esteban >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
On Wed, Jul 6, 2011 at 4:34 PM, Igor Stasenko <[hidden email]> wrote:
+1
+1 -- -- Mariano http://marianopeck.wordpress.com |
In reply to this post by EstebanLM
On 6 July 2011 16:39, Esteban Lorenzano <[hidden email]> wrote: > > btw... ConfigurationOfCog should load latest version of FT2Plugin, and it is not doing it... > how your builds are working? > huh? it loads them. Have you updated to latest ConfigurationOfCog? version23: spec <version: '2.3' imports: #('1.6-baseline' )> spec for: #'common' do: [ spec blessing: #'development'. spec description: 'Added freetype plugin'. spec author: 'IgorStasenko'. spec timestamp: '4/07/2011 11:15'. spec package: 'FFI-Pools' with: 'FFI-Pools-eem.3'; package: 'SharedPool-Speech' with: 'SharedPool-Speech-dtl.2'; package: 'Balloon-Engine-Pools' with: 'Balloon-Engine-Pools-JB.2'; package: 'Alien-Core' with: 'Alien-Core-IgorStasenko.68'; package: 'Sound' with: 'Sound-StephaneDucasse.62'; package: 'VMConstruction-Plugins-OSProcessPlugin' with: 'VMConstruction-Plugins-OSProcessPlugin-dtl.27'; >>> package: 'Freetype-Plugin' with: 'Freetype-Plugin-IgorStasenko.61'; package: 'Cog' with: 'Cog-eem.44'; package: 'VMMaker-oscog' with: 'VMMaker-oscog-IgorStasenko.92'; package: 'Qwaq-VMProfiling-Plugins' with: 'Qwaq-VMProfiling-Plugins-JB.5'; package: 'CMakeVMMaker' with: 'CMakeVMMaker-IgorStasenko.115'. ]. > El 06/07/2011, a las 10:08a.m., Igor Stasenko escribió: > >> >> On 6 July 2011 15:06, Esteban Lorenzano <[hidden email]> wrote: >>> >>> hi, >>> yes... this is another case of "premature questioning" :) >>> now... a stupid one: I don't have "configure" tool installed on my system. Do you know what I need to install to have it? >>> is a port? >>> >> yes, please read the http://code.google.com/p/cog/wiki/FT2Plugin >> (looks like you asked another premature question ;) >> >>> cheers, >>> Esteban >>> >>> El 06/07/2011, a las 9:59a.m., Igor Stasenko escribió: >>> >>>> >>>> On 6 July 2011 14:56, Esteban Lorenzano <[hidden email]> wrote: >>>>> >>>>> Hi, >>>>> >>>>> El 05/07/2011, a las 12:04p.m., Igor Stasenko escribió: >>>>> >>>>>> Freetype library are built from scratch by downloading library sources >>>>>> directly from git repository (maybe its a bit too much, but it works). >>>>>> See /unixbuild/FT2Plugin/makeFreetype.sh >>>>>> >>>>>> this script is then used by cmake config to build libfreetype.a which >>>>>> is statically linked with freetype plugin. >>>>>> >>>>> >>>>> sorry, this is very unclear for me >>>>> how do I execute makeFreetype.sh? what are expecting as a parameter? any further instruction? >>>>> >>>> >>>> The argument is where to copy the resulting libfreetype.a file. >>>> >>>> But see >>>> >>>> MacOSConfig>>configureFT2Plugin: maker >>>> >>>> it is used there. >>>> It should work with cocoa builds without any changes. >>>> So, just try to build it and see what happens :) >>>> >>>>> cheers, >>>>> Esteban >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. > > -- Best regards, Igor Stasenko AKA sig. |
Free forum by Nabble | Edit this page |