[squeak-dev] re: A Bounty for CMake-ifying stack/Cog vm build process

Frank Shearar frank.shearar at gmail.com
Thu Nov 7 20:36:16 UTC 2013


But Tim's point still stands, because deployment is the problem you
solve after having solved the "build it" problem :)

frank

On 7 November 2013 20:13, Chris Muller <asqueaker at gmail.com> wrote:
> Deployment should be regarded a separate problem than building.
>
> On Thu, Nov 7, 2013 at 2:00 PM, tim Rowledge <tim at rowledge.org> wrote:
>>
>>
>> One important thing to remember is coping with a first build on a new machine. Having a squeak app that can drive cc to build a vm would be very neat, but if you don't yet have a working vm for a device you could be in trouble.
>> An advantage of the cmake process is that it bypasses that issue. Actually running the configure on the target machine means you get (hopefully!) accurate results when querying facilities. There is also some benefit in a production environment in being able to pass a 'normal' build job to someone else without having to find a squeak buildomatic cognizant person.
>>
>


More information about the Squeak-dev mailing list