jcward / ascsh Goto Github PK

When I use ascsh with FlashDevelop, incremental compilation works fine but any compiler errors do not get reported to the results panel. The errors still show up in the Output panel so you can see what went wrong, but without outputting to the Results panel, a user cannot double click and go directly to a compiler error's location in code.

hello,

i've just tried the current 'master' branch with 'ant install' on the latest AIR SDK / win32.

it works great, but one problem that i've noticed is that if you run 'compile 1' on the simplest of Main.as projects with a deliberate small error you will find that after MXMLC displays the error, java.exe locks the file (assuming LockFile() from the WINAPI) and the file cannot be changed until ASCSH is stopped (i.e. the jave.exe process is stopped) or the file is manually unlocked by another process.

this issue prevents fixing errors / warnings in any source file that was just compiled by MXMLC via ASCSH.

any possible solutions?

ascsh only supports 1 compile target reliably. This is because it uses MXMLC.staticMainNoExit() -- however, using the non-static MXMLC.mainNoExit(), the compile process hangs on the second compile attempt.

For ascshd, this means killing the server when you switch projects.

I'd need a JAR so as to comply with fcsh.jar - is that possible to build?

IDEA compile AS project so slow , can it work with intellij IDEA ?

Or perhaps a cross-platform makefile

I've downloaded latest ant, setup the env variables, downloaded ascsh and run ant install as instructed. I got:

e:\FlashDevelop2\Tools\ascsh-master>ant install
Buildfile: e:\FlashDevelop2\Tools\ascsh-master\build.xml

compile:
    [javac] Compiling 2 source files to e:\FlashDevelop2\Tools\ascsh-master\build\classes
    [javac] e:\FlashDevelop2\Tools\ascsh-master\src\java\ascsh.java:1: package com.adobe.flash.compiler.clients doe
s not exist
    [javac] import com.adobe.flash.compiler.clients.MXMLC;
    [javac]                                        ^
    [javac] e:\FlashDevelop2\Tools\ascsh-master\src\java\ascsh.java:2: package com.adobe.flash.compiler.clients doe
s not exist
    [javac] import com.adobe.flash.compiler.clients.COMPC;
    [javac]                                        ^
    [javac] e:\FlashDevelop2\Tools\ascsh-master\src\java\ascsh.java:79: cannot find symbol
    [javac] symbol  : class MXMLC
    [javac] location: class ascsh
    [javac]         if (compiler instanceof MXMLC) {
    [javac]                                 ^
    [javac] e:\FlashDevelop2\Tools\ascsh-master\src\java\ascsh.java:81: cannot find symbol
    [javac] symbol  : class MXMLC
    [javac] location: class ascsh
    [javac]           exitCode = ((MXMLC)compiler).staticMainNoExit(args);
 (...)
    [javac] Note: e:\FlashDevelop2\Tools\ascsh-master\src\java\Commandline.java uses unchecked or unsafe operations
.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 9 errors

BUILD FAILED
e:\FlashDevelop2\Tools\ascsh-master\build.xml:14: Compile failed; see the compiler error output for details.

Total time: 1 second

What I'm doing wrong? :)

In a (nested ruby) build system, if I simply run:

ascshd mxmlc ...

It hangs on the first call (server startup). If I start the server manually (outside the build system), all works fine.

Ideally you wouldn't have to start the server manually... I'm not sure if this is due to how I'm handling processes in ascshd, or how my build scripts work.

ascshd is a ruby script that uses fork, process IO, etc. As-is, it doesn't work in Windows. This is a problem because Flash Develop is a big potential user of ascsh. However, perhaps FD itself can manage the ascsh process without the help of ascshd? Did it manage the fcsh process?

Existing builds likely have FCSHD support built-in (well, mine does.) I'd like an ascshd drop-in replacement for fcshd.