Basically, I don't want Cygwin and I don't want to use a build process that is dependant upon other parts of my installed and working system for it's operation.

I have tried to use the --ask switch to bypass the automated (and incorrect) detection of the build tools I wish to use, and would like a little help in working my way through the existing build process in order to construct a standard makefile. I have been trying to track my way through the existing build process, but am finding this to be an extremely difficult thing to do and hope that someone who is familiar with it will be able to guide me.

For example: What is the route of the dependancy tree. The obvious starting place is the file in the root of the build directories parrot.c, but all this does is include parrot.h. This is further complicated by the precence of other source files in this same directory which apparently are not directly a part of the parrot binary such as jit.c

I realise that the JIT and several other subprojects are related, but I can find no clear delineation between the sub-projects nor any simple roadmap of the dependancies of any given source file.

Examine what is said, not who speaks.
1) When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
2) The only way of discovering the limits of the possible is to venture a little way past them into the impossible
3) Any sufficiently advanced technology is indistinguishable from magic.
Arthur C. Clarke.

In reply to Re: Re: Parrot build mechanism expertise required. by BrowserUk
in thread Parrot build mechanism expertise required. by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.