On Sat, Jan 2, 2016 at 11:42 PM, Alex Harui wrote:
>
>
> On 1/2/16, 6:28 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
> wrote:
>
> >
> >
> >With the same exact code, on Mac, when I run:
> >omuppirala$ asjsc
>
I have been able to make progress on this front.
I am able to install flexjs using this command on Windows and Mac:
npm cache clear
npm install http://bigosmallm.github.io/flexjs/npm/flexjs-0.5.0.tgz -g
On Windows, in Cygwin, when I run this:
asjsc
asjsc does not create an HTML file.
- Josh
On Jan 2, 2016 6:28 PM, "OmPrakash Muppirala" wrote:
> I have been able to make progress on this front.
>
> I am able to install flexjs using this command on Windows and Mac:
> npm cache clear
> npm install
On 1/2/16, 6:28 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>
>
>With the same exact code, on Mac, when I run:
>omuppirala$ asjsc
>/usr/local/lib/node_modules/flexjs/examples/native/USStatesMap/src/USState
>sMap.as
>
Yes, the folder structures are (should be) the same. The weird thing is
that asjscompc is working fine without this error.
Can you try it out based on the instructions in the other thread? I am
sure some things are obvious to you and easy to catch.
Thanks,
Om
On Dec 29, 2015 7:09 AM, "Alex
I got the FlexJS 0.5 installed via the Installer and the call to asjsc from
that folder seems to work fine.
So, I don't think it is a Java version conflict.
Any other ideas?
Thanks,
Om
On Mon, Dec 28, 2015 at 3:03 AM, Michael Schmalle wrote:
> Just shooting in the
Have you compared the folder structures from npm install vs the installer?
Should they be the same?
-Alex
On 12/29/15, 1:04 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>I got the FlexJS 0.5 installed via the Installer
I have this working locally. If the user has npm and Java installed on
their machine, they can now simply do:
*npm install flexjs -g*
(or should it be npm install apache-flexjs -g?)
This will download all the dependencies (which has some bugs for now, will
get to that in a bit), register the
Just shooting in the dark but some type of Java version conflict? It seems
familiar to me like that could be a possibility.
Mike
On Mon, Dec 28, 2015 at 4:34 AM, OmPrakash Muppirala
wrote:
> I have this working locally. If the user has npm and Java installed on
> their