On Dec 12, 2005, at 11:32 AM, Jim Grandy wrote:
Thanks. I wasn't looking at the Internal Documentation page (which
is the only link to this page). I'll take down my page and make
sure the content on this page is up to day. We should probably
change the Internal Documentation page name as well.
I agree. To what?
I couldn't find it either from the toc. I ended up searching for
buildlfc instead.
jim
On Dec 12, 2005, at 3:48 AM, Oliver Steele wrote:
On Dec 11, 2005, at 11:58 PM, Jim Grandy wrote:
Thanks (and thanks, Adam!). I started a new page on the wiki with
this:
http://wiki.openlaszlo.org/Incremental_Builds
Also see <http://wiki.openlaszlo.org/How_to_Build#Incremental_build>:
Incremental build
You will soon discover that 'ant build' takes a long time to
recompile every file ten times after every one-line change that
you make. Here's what we actually do during development:
1. Pick a version to debug against, say swf6 debug. (It's
generally easier to develop against the debug versions.)
2. In a shell terminal window that is open to the lfc
directory, invoke the 'buildlfc' command that builds that version
of the LFC library --- say, 'buildlfcdebug'. It will spin for a
while, and create a new build of that library, but it will stay
open so that you can rebuild the library more quickly. You've
already saved time because you're not building the other library
versions.
3. Open your test app with a URL that links against that
version (in this case http://localhost:8080/lps-3.0b2/test.lzx?
lzr=swf6&debug=true, to pick up the +debug swf6 version --- krank
and profile default to off).
4. Edit the LFC source(s).
5. Press Enter in the 'buildlfc' terminal. This will rebuild
the LFC library much faster than the first compilation.
6. Press the browser Reload button, to relink the application
and run it again.
Your edit-compile-debug cycle is (4-6), which is reasonably fast.
(It's about the same speed as working on an LZX source file.
You've got one more window to cycle through to rebuild the LFC
library, but the monkeys here who are smarter than me use macros
for this.)
The failure mode is to rebuild ONE version of the library, and
link against ANOTHER. My favorite debugging technique if nothing
seems to be having any effect is to introduce some change that you
know will break everything, and see if it actually does.
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
