On Thu, Aug 12, 2010 at 11:42 AM, Sebastian Wagner <[email protected]>wrote:

> Would it be possible to summarize those hooks needs for the incremental
> compilation in some ant tasks?
> I think that would make it a lot easier to handle
>
> Also is there any chance to implement this feature into the dev-console?
>

It would be a fair amount of work to graft this into  the LPS server. The
server currently invokes the flex compiler through some top level
command-line
entry points, which are not really the ideal place to call into.

Adobe  supplied the "fcsh" utility, which uses more fine grained calls to
invoke their compiler, and it keeps the flex compiler state in memory, and
handles incremental
compilation, so I just kind of cut and pasted their compile command in a
routine that first calls the LPS compiler. I think that
the calls that fcsh uses may not be a public API though.  I guess that code
could be carved out and added to the LPS, though it
really uses a lot of internal flex classes.


There is what looks like a  recommended  public API to control the flex
compiler that is documented,
 their so-called Compiler OEM API [1] .  I tried using it when it came out a
couple of years ago,
but ran into some stupid issues with spaces in pathnames on OSX, and never
got that fixed.  I'm not actually sure whether that API
is supported fully or not (e.g., is anyone else using it, does it have
bugs?)  but I do have some old code around someplace that uses it, that
might serve as a
starting point.


[1]
http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBkQFjAA&url=http%3A%2F%2Flivedocs.adobe.com%2Fflex%2F3%2FcompilerAPI_flex3.pdf&ei=zStkTLD2KYa8lQfdkbDDCg&usg=AFQjCNHuhtl11rtUXjrI9-r9lTOtZjXs9g&sig2=oPB0qjRISiOIq0ibWg-e-Q



> Sebastian
>
> 2010/8/12 André Bargull <[email protected]>
>
> From the wiki-page:
>>
>>> Short how-to for incremental compilation under Windows:
>>>
>>>   1. open command line interpreter, for example Win+R and enter cmd
>>>   2. set FLEX_HOME environment variable: set
>>> FLEX_HOME=C:\apache-tomcat\webapps\openlaszlo-4.8.1\WEB-INF
>>>   3. change %FLEX_HOME%\bin\jvm.config file to include lps-4.8.1.jar to
>>> java classpath: java.class.path={application.home}/lib/lps-4.8.1.jar (thanks
>>> to forum user AxelP)
>>>   4. change %FLEX_HOME%\bin\jvm.config file to set LPS_HOME environment
>>> variable for java: java.args=-Xmx384m -Dsun.io.useCanonCaches=false
>>> -DLPS_HOME={application.home}/..
>>>   5. go to the application source directory, e.g. cd
>>> C:\apache-tomcat\webapps\openlaszlo-4.8.1\my-apps
>>>   6. start fcsh with %FLEX_HOME%\bin\fcsh.exe
>>>         1. create initial compilation: lzc --runtime=swf10 app.lzx
>>>         2. edit source files and recompile application with lcompile
>>> TARGET_ID where TARGET_ID is the compile target id assigned by fcsh
>>>
>>
>>
>> On 8/12/2010 5:03 PM, Henry Minsky wrote:
>>
>>> Can you post the setup you needed for Windows?
>>>
>>> I'll check on a clean unix shell that doesn't have my .bashrc running.
>>>
>>> On Thu, Aug 12, 2010 at 10:08 AM, André Bargull <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>>      There seem to be some environment variables required for
>>>    incremental compilation, but this isn't covered in the release notes
>>>    [1]. After downloading 4.8.1 (dev-kit release), I needed to perform
>>>    a few more steps before incremental compilation worked under Windows
>>>    [2]. I guess someone should try out incremental compilation on
>>>    Unix-based systems, to make sure it's working there, too. This
>>>    should happen in a clean environment, so without the various
>>>    environment variables which are needed to build from source.
>>>
>>>
>>>    [1] http://download.openlaszlo.org/4.8.1/release-notes.html
>>>    [2] http://wiki.openlaszlo.org/Incremental_Compilation
>>>
>>>
>>>
>>>
>>> --
>>> Henry Minsky
>>> Software Architect
>>> [email protected] <mailto:[email protected]>
>>>
>>>
>>>
>
>
> --
> Sebastian Wagner
> http://www.webbase-design.de
> http://openmeetings.googlecode.com
> http://www.wagner-sebastian.com
> [email protected]
>



-- 
Henry Minsky
Software Architect
[email protected]

Reply via email to