We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi All. I am generating Salvo libraries for a new release, and have stumbled onto a problem that I believe is v7.x-related ... I say this because our last release for 8051 was generated with v6.x ... Using the same makefiles as before, our libraries have grown from 20-100k to around 2.5MB each (!). When generating libraries, we use DB BR OE (and some others). Playing around with v7.x, I find that If I omit BR, file size drops from 2.5MB down to, say, 70KB, and omitting DB drops it to 20KB. I can live with the DB effects, but enabling the browse functionality results in enormous libraries. Is this standard / expected behavior? Thanks,
OK, I did some more research and it appears that we did not use BR when we built with v6.x ... my bad. So, I guess my question boils down to "Is it normal for BR to affect the size of a library so much (e.g. 70KB becomes 2.5MB)?" Thanks,
Browser Information adds many references to the OBJ files that are used to track all accesses to variables, structs, struct members, defines, ect. Therefore this can be normal.
Thank you. Do either DB or BR cause source code to be included in the library (for debug / viewing purposes)? Regards,
No, the source code itself is not included, just the references to it. When you do not supply source code, DEBUG or BROWSE information make typically no sense.
Thanks -- that clears things up for me. Regards,