Dear Arnaud,
thank you for the clarification.
Please, find below my comments.
Best Regards,
Massimo
Dear Massimo,Thank you for your feedback. I think here we have a issue with the way you are using StellarIP. In our point of view, StellarIP users are using a global library. We have that one called mainlib and this mainlib is part of our SVN repository. All our firmware engineer, about a dozen are using the same main library.
> Yes, this is my goal too. However, I am versioning the library too, since I am developing my stars and so the library is evolving. For this reason, I ended up in having 2 library, since for debug reasons, I had to do a fresh check out from my repository of a release that I knew to be stable. At that point, the tool was still pointing to the last library and not to the one I just check-out. Hence I got the issue that I described in my first post.
There is a library merge utility in StellarIP that is able to merge any library into one main library, I assume this is what you missed here, you could create one library at of as many libraries you have and then only have one local library.
> Yes, thank you, I used the merge function at very beginning to merge stars coming in different libraries. When you are prompted to load the local library, you can answer NO and check the box about not asking me again, you will not be prompted after anymore.As a side note, after merging the libraries you will need to copy subfolder (relatives to the .tclib) into your main library.
> OK. Let me know if this helps!
> Yes, thank you. I have a further question. If I have one single library located somewhere in my file system, and several design folders, the compilation of a certain .dsn includes the vhd files that the tool spots in the star_lib/ folder contained on level of hierarchy below the design file .dsn? I ask this because this is what I would need to have in the end.
Arnaud