Yep, we expect you to have cloned several of our repos and try to assume
some variables based on that. Folks testing source packages often have to
set these variables to point to repos or other source packages. If you
can think of a good place for us to document that or a better way to deal
with
Yeah that is because the build script looks for it in the sibling
directory, if you had it somewhere else you would need the vars, I think
that goes for most of the env variables as well.
Mike
On Sun, May 31, 2015 at 5:42 AM, Harbs wrote:
> FYI:
>
> Simply checking out the repo solved it for me
FYI:
Simply checking out the repo solved it for me. As long as the directories are
not renamed and all in the same parent directory, build.xml finds all the
dependencies.
On May 31, 2015, at 12:37 PM, Harbs wrote:
> Ah. I did not think to look for a separate repo…
>
> Thanks!
> Harbs
>
> On
Ah. I did not think to look for a separate repo…
Thanks!
Harbs
On May 31, 2015, at 12:33 PM, Michael Schmalle
wrote:
> Check out the repo and set it to the flex-blazeds directory.
>
> I don't know what it's for either but I did this and it built, I think you
> need to checkout flex-flexunit a
Check out the repo and set it to the flex-blazeds directory.
I don't know what it's for either but I did this and it built, I think you
need to checkout flex-flexunit and build that as well, or maybe that is for
flex-asjs.(not looking at the README)
Mike
On Sun, May 31, 2015 at 5:01 AM, Harbs w
I just tried building the Flex SDK for the first time in a while and I see that
env.BLAZEDS_HOME is a required variable.
I have not been following the progress with Blaze DS, so I’m not sure what that
should be set to. Any pointers?
Thanks,
Harbs
