#11 make build cache transparent (produce cached compiler output)
I'm using makepp in IDE (Eclipse) which parses compiler output from console to update internal index.
But when I enable build cache, do some changes invisible by IDE and do build which results in makepp import files from cache, IDE doesn't update index because makepp doesn't provide compiler output.
This would be a rule option (disabled by default).
I kindly ask you to add this feature in next release. makepp is awesome but this limitation very frustrating. I'm sure this feature is very demanded.
(Currently I have to disable cache in my projects to make IDE features work correctly. This degrades performance dramatically because projects are large and I switch between git branches often. Alternatively I've tried use of ccache but it didn't helped to increase performance, seems overhead is too large.)
Hi Artem,
Glad you like it, but I'm not sure I understand. Do you want it to output the command, as though it had actually just run it again? That would be easy.
Or do you want it to also re-output all warnings, which would be more work, since we don't store them, and I'm not sure what would be the right place. Some commands might output megabytes of blabla, though that is admittedly uncommon. But catering to this possibility would make a separate file a strong option, alas one that alas means another level of administering things. In the eye of potential concurrent writes to the cache, which currently seems to be handled safely, a new risk! :-(
regards -- Daniel
Hi, Daniel
I meant all output, including warnings. But if you make just command output, it would be still great! It's better than nothing.
Regarding saving warnings, it would be optional, although I don't understand why you bother about blabla size. It should be treaten as other compiler output, such as object file, which size could be any. It's a user care. Concurrent access issue could be resolved by placing all things in single file (archive) with atomic read/write.
Regards,
Artem