Multiple target libraries

[Blebowski]

Is your feature request related to a problem? Please describe.
I am trying to visualize a PNR netlist written by a commercial PNR toolchain.
We have multiple .lib files that are used in this "chip-top" netlist: Standard cells, Analog models, RAMs, Pads, etc...

However, when loading the netlist, I can choose only single library. But then my netlist loading errors out
since it can't map e.g. the SRAM cell to a cell from STD cell library.

Describe the solution you'd like
Choose "multiple" target libraries, e.g. by importing all liberty files and allowing all of them to be used.
I think this can be made like that when you "import" a library, it will automatically be part of "available"
libraries list. Such list would implicitly contain the built-in libraries. Each item of the list would contain
a checkbox saying if this library shall be used when reading the netlist.

Describe alternatives you've considered
Copy paste all the used libraries into single .lib file -> Sorry too hackish for our files.

• Alternative could be throwing only warning if the cell could not be mapped to a target library, but it would create a black-box. This would then allow displaying library with STD cells .lib only, but all the analog and pad macros would be "black-boxed" out. This does not mind at all...

Additional context
Nice work on the tool, thank you for the effort.

[Blebowski]

Any clue on what to do with this ?

I like HAL, and I would like to try to use it instead of commercial equivalent called GateVisionPRO,
but the fact that I can't load my netlist is making it... well... unusable.

Is there alternatively option to use "no-technology" and treat every module in the netlist as black-box ?