> > We just finished fixing a couple of issues in this compile mode (one > around JSOs and a couple around rerunning Generators). > > Any more feedback you have would be appreciated. If you see any bugs > please report them. >
Just tried it yesterday. Compile time of normal SDM was about 40-50 seconds and with per-file it dropped down to 17-20 seconds when changing a single file. From this 17-20 seconds it was about 5-8 seconds pure compilation and the rest was linking. Since I use an SSD I don't think linking was limited by IO. I tried using -Dgwt.speedtracerlog but it seems like recompilation using per-file does not emit any speedtracer log, only the first precompile does so. During the initial precompile there was a warning about certain css files loaded via class loader, although I am not sure why these few files caused the warning. These css files were referenced using @Source of CssRessource and had a relative path. Other css files did work fine. Also a warning about source maps was emitted (Unable to find all source code needed by debuggers, X files form source maps weren't found). So in general it seems to work well however linking slows it down quite a bit. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/b754c836-12ed-44c7-99fa-abb41b8c9373%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
