On Tue, May 7, 2013 at 2:01 AM, Gabor Szabo <ga...@szabgab.com> wrote:
> I started to write a stand-alone script that would build and test > Rakudo and then a bunch of modules, > but probably it would be easier to just try to build Rakudo * > including all the modules and > put together a report on issues encountered. > > I cloned Rakodo * from https://github.com/rakudo/star and tried to build > it with > > perl Configure.pl --gen-parrot > > it complained I am in a .git directory and then quit. > These are the directions for building a distribution of rakudo-star that has already been constructed (e.g. http://rakudo.org/downloads/star/rakudo-star-2013.02.tar.gz); the warning here tells you as much. > > I tried to force it using > > perl Configure.pl --gen-parrot --force > > this time it stopped with > > Unable to read rakudo/tools/build/NQP_REVISION > > The README of Rakudo * tells me there is supposed to be a rakudo/ > subdirectory, but there > isn't and the subdirectories inside modules/ are also empty. > > Do I first need to manually clone Rakudo and the modules from Gihub > and then use the --force or is > there something else I need to do? > README.star has the pointers for creating a rakudo star distribution. I'm thinking this isn't mentioned in the README or the output you got before because we're expecting most people at this point to be trying to get an already-constructed distribution version, not build their own. > Do I understand correctly that in a real Rakudo * release you'd check out > the > labeled release of Rakudo and the latest versions of the modules and > then start the build process? > > regards > Gabor > The released copy has everything bundled in it. Creating the distribution will pull in everything from the various repositories. Hope this helps. -- Will "Coke" Coleda
