On Wed, Jan 6, 2016 at 3:33 PM, Josh Tynjala <joshtynj...@gmail.com> wrote:
> Yes, on the Windows command prompt (and PowerShell), you need to run .bat > version of the script. The shell script may work correctly in Cygwin, > though. > Is there a good way to npm to register asjsc for OSX/Cygwin and asjsc.bat for Command Prompt/PowerShell? Thanks, Om > > - Josh > > On Wed, Jan 6, 2016 at 3:23 PM, OmPrakash Muppirala <bigosma...@gmail.com> > wrote: > > > On Wed, Jan 6, 2016 at 1:26 AM, OK <okrue...@edscha.com> wrote: > > > > > OmPrakash Muppirala wrote > > > > If we can use FlexJS on Windows without Cygwin, that would be a big > > win. > > > > > > For me it seems that it works without Cygwin. > > > > > > > > > OmPrakash Muppirala wrote > > > > What error do you get when you simply try to run asjsc without the > full > > > > path on Command Prompt? > > > > > > "The system can't find the specified path" (Translated from german) > > > > > > > I am seeing this problem as well from Command Prompt. I think we need to > > use asjsc.cmd instead of asjsc for Command Prompt. I will tinker with > this > > a bit and see if we can get this working. > > > > Thanks, > > Om > > > > > > > > > > > > > OmPrakash Muppirala wrote > > > > We are discussing if we should have asjsc generate this > > > > simple html file by default so that newcomers like you have a better > > > first > > > > impression and an easier starting point with FlexJS. > > > > > > +1 (If there are no disadvantages with creating this html file) > > > > > > Thanks, > > > Olaf > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Need-your-help-testing-the-flexjs-npm-module-tp50911p51050.html > > > Sent from the Apache Flex Development mailing list archive at > Nabble.com. > > > > > >
