After updating to XE6 recently, we're having issues with frequent, but random, instances of compiler error F2063 - Could not compile unit.
After updating to XE6 recently, we're having issues with frequent, but random, instances of compiler error F2063 - Could not compile unit.
However, there are no other errors at all, and a full build always solves the issue, so there's not an actual code issue. Simply recompiling usually lets it move on, though it usually fails on another unit.
The units it fails on is completely arbitrary and there is no discernable pattern at all.
This is especially an issue in our CI builder, as doing full rebuilds there significantly slows down the CI cycle. However all of us are plagued with the issue, so it's not a OS or installation thing.
We've not had any such issues with our previous Delphi versions.
Anyone else been experiencing this?
However, there are no other errors at all, and a full build always solves the issue, so there's not an actual code issue. Simply recompiling usually lets it move on, though it usually fails on another unit.
The units it fails on is completely arbitrary and there is no discernable pattern at all.
This is especially an issue in our CI builder, as doing full rebuilds there significantly slows down the CI cycle. However all of us are plagued with the issue, so it's not a OS or installation thing.
We've not had any such issues with our previous Delphi versions.
Anyone else been experiencing this?
Not sure really, as I have a habit of building instead of compiling. I'll try to see if it happens to me as well.
ReplyDeleteLars Fosdal Yeah personally I usually build as well, as there was some issues similar to this back in the D3-D7 times. I haven't been able to nail it down, but it seems to happen most frequently when compiling first time after loading a project. Even if you just closed the very same project and had recently compiled it.
ReplyDeleteWell, I can verify that it happens. Another F9 goes straight past it though.
ReplyDeleteDon't know if this applies here, but these two approaches might help: 1. avoid circular unit references and 2. add all used units to the project.
ReplyDeleteYeah, that's gonna happen :D
ReplyDeleteUwe Raabe Circular unit refs, that's pretty much unavoidable.
ReplyDeleteAll used units... well, a quick count gives me roughly 3500 units, in a ton of directories... urgh.
Asbjørn Heid I am still waiting for a proof that circular unit refs are unavoidable. Cumbersome, yes - but possible.
ReplyDeleteFor the used units, I don't refer to standard or library units, of course. But I admit, there might be cases where this is less desirable.
Uwe Raabe Of course it's technically possible. Just put all your code in the dpr file! However in any sane practice, it's unavoidable.
ReplyDeleteIt'll check out our unit references though, might be some direct references that are missing but are found due to include file paths.
My Delphi Unit Dependency Scanner can help you visualise your unit structure and highlight circular references -http://www.easy-ip.net/delphi-unit-dependency-scanner.html
ReplyDeletePaul Thornton Cheers, I'll take it for a spin and see.
ReplyDeletePaul Thornton Seems it ignores files which are included in a "side directory", ie uses foo in '..\dir\foo.pas'.
ReplyDelete+Asbjørn Heid-As long as you add the correct path in the settings, all the files should be found.
ReplyDeletePaul Thornton Yeah ok, then it finds them. That's not strictly correct though, is it? I mean, I was under the impression the compiler ignored the search path when you used the "in" keyword. Perhaps I'm just rusty.
ReplyDeleteAnd yeah, found some circular dependencies (as well as several "semi-circular" ones). Time to clean up and see if that helps. Thanks again :)
ReplyDelete