I experience some weird behavior with respect to compile build times:
R2 and R3 do not build at all. Only when I change optimization from aggressive to default. But still half a minute is very long. Fans start whirring and computer is having a hard time (Core i7 16 Gb). What could cause this?
ps I noticed that HoudiniAssistant becomes active in the taskmanager in the Xojo process item
You may not know.
In the first run, a cache folder is filed and NOT ERASED when you quit.
The successive runs modify - in that cache folder - only the parts corresponding at what you changed in the project.
That what was said (in the Forum or in the Release Notes) when this was implemented.
This explain why we cad erase the Cache folder in the Preferences. (this can be moved, with a Keyboard Shortcut, elsewhere in the MenuBar.)
Xojo should take a look at your project, attached in a private issue.
You should try Moderate instead of Aggressive just as a test. If that works, check and see if you have any extraordinarily long methods (hundreds of lines). If so, break it up into smaller chunks and try again.
There’s a known bug with Aggressive compilation.
The key seems to be the use of Variants with string or double constants. Something about the "code constant [string or double] to variant” conversion
There is a change in 2025r2 about aggressive compilation if I remember correctly, that could explain why it changes with that version.
I mean this:
2025r2 Highlights
- Optimized (faster, larger) frameworks are used when compiling with Aggressive Optimization
Switching to moderate prevents the build process from hanging luckily. Still takes about 15 secs. Thanks.
Wondering what Houdini Assistant is doing. Probably freeing up hanging processes or something.
Keep in mind that Moderate is different from Aggressive in what it does for you. IIRC Moderate optimizes for size over speed whereas Aggressive optimized for speed over size.
