The instructions for rebuilding the LFC are here:

  http://wiki.openlaszlo.org/SubversionBuildInstructions

The top-level build target is

  ant make

This will recompile any changes and re-install the server in tomcat.

---

If you have set up that environment and want to quickly build a test lfc for a particular back-end, you need to be in the directory

  WEB-INF/lps/lfc

In there are shell scripts for invoking the correct ant procedure to build. Note that there is a separate script for building the non- debug, debug, and backtrace-enabled LFC, unfortunately. It is easy to confuse yourself by building one version and testing another. Also, you may have to use your browser's debugger to empty its cache and force it to reload the LFC. These are the scripts:

  ./buildlfc
  ./buildlfcdebug
  ./buildlfcbacktrace

The all take a --runtime option. To build the swf9 debug runtime, you would say:

  ./buildlfc --runtime=swf9

There is no bactracing in swf9 (yet). But the wiki article above tells how to get the Flash debug player and use fdb to debug swf9 code.

If you are debugging generic code (not code for a particular platform), you may find it easier to debug using the DHTML runtime which has built-in backtracing and which you can use the browser debugger (e.g., Firebug for Firefox) to do low-level debugging with.

We hope you will consider contributing your fixes back!

On 2009-08-31, at 07:03, Rami Ojares / AMG Oy wrote:

Hi,

I am trying to fix some bugs in LzTrackService.
I got the compilation process working but I don't have a clear grasp yet of what is going in there although I browsed through the ant files.

My question is this:

The source file: LzTrack.lzs is located in WEB-INF/lps/lfc/services/ LzTrack.lzs
But where is the generated compiled file?

I tracked it down to app.swc in some obscure tmp folder but there the tracks got colder.

I would just like to compile this lzTrack.lzs and then put it in my own laszlo distribution for trying it out.
But which file do I copy and from where?

- Rami Ojares

Reply via email to