Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qucs-S user library portability #567

Closed
3 tasks done
tomhajjar opened this issue Feb 15, 2024 · 3 comments · Fixed by #640 or #676
Closed
3 tasks done

Qucs-S user library portability #567

tomhajjar opened this issue Feb 15, 2024 · 3 comments · Fixed by #640 or #676

Comments

@tomhajjar
Copy link

tomhajjar commented Feb 15, 2024

I noticed that the two RF resistor examples "Test_chip_res_basic.sch" and "Test_RATF_EquivCircD.sch" don't work anymore. The devices used in these examples work in the 7 other examples in the attached project.

https://github.com/ra3xdh/qucs_s/tree/current/examples/ngspice/RFLumpComp

One issue is the examples you uploaded point to your user_lib folder. I didn't dig too deeply into the other issues but it got me thinking how to make user created projects and libraries "portable". LTspice allows placing everything required into a single folder. Is there a way other than making subcircuits containing the symbol information to place a user created Qucs compatible library in the project folder?

TODO list

  • Add schematic directory to library search paths;
  • Resolve relative paths in the library device property dialog
  • Make the libraries from the project directory visible in the library manager; Add group Project libraries

Resistor_RF-Models_prj.zip

@ra3xdh
Copy link
Owner

ra3xdh commented Feb 15, 2024

Is there a way other than making subcircuits containing the symbol information to place a user created Qucs compatible library in the project folder?

There is no way to place library at the project directory. Library devices support specifying the full path to libraries, but library manager will look only at system library or user_lib directories. This was already reported and related to #4. It still be unclear how to introduce library search paths and improve the library portability.

@ra3xdh
Copy link
Owner

ra3xdh commented Apr 7, 2024

Relative paths implemented with #640. I will implement the visibility of the libraries in project directory myself.

@ra3xdh
Copy link
Owner

ra3xdh commented Apr 7, 2024

The #676 implements showing the libraries from the project directory in the library tree.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants