[Laszlo-dev] LzTrack.lzs

[Rami Ojares / AMG Oy]

Hi,

What I ment was that how could I build just the webapplication so it 
would not be mixed with the source.
I mean the contents of what goes currently with the name 
openlaszlo-4.7.x-servlet.war.
I have a build system that assumes laszlo to be somewhere without the 
source (and possibly some intermediary build artefacts) mixed in.
And best would be if I could get this as folder structure not as war file.

I think that now when I call ant build Everything is built in the middle 
of the source code.

- rami


P T Withington wrote:
> If I use the targets `make` or `build`, the doc does not get built.  
> What target are you using that builds the doc?
>
> On 2009-09-01, at 08:11, Raju Bitter wrote:
>
>> if you modify the build.properties, you can skip generation of the 
>> documentation.
>>
>> # Comment out this line to enable the doc build
>> # With this line present, we will skip the doc build
>> # skip.doc = true
>>
>> On Sep 1, 2009, at 1:56 PM, P T Withington wrote:
>>
>>> `ant build` will build the server jar and the lfc.  You don't need 
>>> to use this path if you are just debugging the lfc, as noted in my 
>>> previous message.  Build and install the server jar, then use the 
>>> buildlfc scripts to rebuild the lfc and test by forcing your browser 
>>> to reload the app with the new lfc (e.g., clearing the browser cache 
>>> or setting the browser to always reload from the server).
>>>
>>> If you cannot update the build instructions on the wiki directly, 
>>> yes please report them.  We try to keep them up to date for 
>>> contributors like you!
>>>
>>> On 2009-09-01, at 07:38, Rami Ojares / AMG Oy wrote:
>>>
>>>> Thanks PT,
>>>>
>>>> Yes I did find the build instructions and they were great...but had 
>>>> some (very minor) mistakes.
>>>> I could report them to Henry if he wants.
>>>> Anyway the more challanging issue I had with building was that the 
>>>> forked laszlo compiler was running
>>>> out of memory so I had to also set "JAVA_OPTS=-Xmx256m" in order to 
>>>> get enough of memory for the forked jvm.
>>>>
>>>> And I found the answer to my own question.
>>>> The core lfc classes are compiled into
>>>> LASZLO_ROOT/lps/includes/lfc directory
>>>> .swc files for swf9 & swf10
>>>> .lzl files for swf8
>>>> .js files for dhtml
>>>>
>>>> I provided a fix for LPP-8379 in Jira so have a look.
>>>> What I would like is to have a build target that
>>>> - creates the laszlo servlet
>>>> - does not need tomcat
>>>> - does not invoke any documentation tasks (so I don't have to wait 
>>>> forever)
>>>>
>>>> Is there such a thing?
>>>>
>>>> - Rami Ojares
>>>>
>>>> P T Withington wrote:
>>>>> 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
>>>>>
>>>>
>>>
>>
>