Mail Archives: geda-user/2020/12/05/06:40:25
On Fri, 4 Dec 2020, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> 3, when I cd /<some_path>/top, I want a gafrc file (or something) that
> tells me where sym and sub_sheets are (./sym and ./sub_sheet)
> 4, when I cd /<some_path>/top/sub_proj_a, I want a gafrc file (or something) that
> tells me where sym and sub_sheets are (../sym and ../sub_sheet)
> 5, when I cd /<some_path>/top/sub_proj_a/sub_aa, I want a gafrc file (or something) that
> tells me where sym and sub_sheets are (../../sym and ../../sub_sheet)
> 6, thoose config files (gafrc) better be the same (e.g. with soft links) so that I
> don't need to maintain more than one config file
Ah, now I understand.
On Fri, 4 Dec 2020, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> So, how do I set up the configs so that I can access the same component
> and source library regardless of where I start the schematic editor and
> without resorting to useing absolute paths (different people check it
> out and places it in different paths) ?
Well, "the usual answer" would be to cd into the top directory and start
gschem from there. If this doesn't work for your workflow, the answer is
to write some script that guesses where to find the libraries, just as you
did. AFAIK, there's no way to do this with non-executable configuration
files, but these aren't deprecated, so no need to worry about this.
If there's anything I missed, please let me know.
Roland
- Raw text -