C
Charlie E.
Guest
On Mon, 10 Nov 2008 11:14:26 -0800, Joerg
<notthisjoergsch@removethispacbell.net> wrote:
And this doesn't just apply to open source! If you are a dedicated
user of Cadence ConceptHDL, then you learn pretty quickly to have perl
and other scripts where you exit the software, delete all the *.b and
*.c files, automatically do edits on the .a files, and then reopen the
software and do a hard save of the project. (You have to delete the
..b binary files, and .c files because these are compiled from the .a,
but have precedence over the .a (ascii) files.)
And users spend mucho bucks for this type of thing!
Charlie
<notthisjoergsch@removethispacbell.net> wrote:
Hi Jeorge,JosephKK wrote:
On Fri, 07 Nov 2008 15:53:41 -0800, Joerg
notthisjoergsch@removethispacbell.net> wrote:
Jan Panteltje wrote:
On a sunny day (Fri, 07 Nov 2008 15:23:32 -0800) it happened Joerg
notthisjoergsch@removethispacbell.net> wrote in
w24Rk.5018$D32.3407@flpi146.ffdc.sbc.com>:
I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory. In Linux you cannot do that. You could theoretically copy
them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore. Because it would then not see
those libraries. Honestly, that doesn't make much sense to me.
I am not sure, but I think that is not correct.
man chown
for example if there is a user joerg, then, as root you can do:
mkdir mylibs
ls -ld mylibs
drwxr-xr-x 2 root root 48 2008-11-08 00:42 mylibs/
Change the owner, and group now you program should see it:
chown joerg:joerg mylibs
drwxr-xr-x 2 joerg joerg 48 2008-11-08 00:42 mylibs/
That directory can be anywhere.
Or
chown joerg:users
drwxr-xr-x 2 joerg users 48 2008-11-08 00:42 mylibs/
Anywhere, as in anywhere but root. At least that's what people told me.
This means you now need to start stuff like gschem from the new
directory where the libs are, by command line. Because it will otherwise
not see its gafrc and thus not load your libraries.
As a long time linux user/self admin i have never found a case where i
could not access any file as root i wanted to. ...
Of course I can get to those as root. But from within the application I
can not.
... As for setting the
environment variables up properly yo need more instruction.
I asked this question in a forum of knowledgeable Linux users and they
said the only way is to put the special libraries under
/home/joerg/whatever, place a gafrc there and forget about running
gschem from the GUI. I began to wonder what the GUI in Ubunutu is really
for. Ok, I thought, not nice but can be done. So I did just that. After
all I grew up with DOS where almost everything was command line.
However, piece by piece came the next "workarounds" where I was told
that I'd have to close the schematic, run some script from the command
line, then re-open the schematic. For example for simple tasks such as
renumbering a schematic properly, meaning without trampling over
multiple opamp instantations. Well, that'all doable but it begins to
crimp my productivity.
This is so much easier in Windows SW. You don't need to do anything,
just start to create your own libraries and remain disciplined enough
not to mess with original libraries. I've had that discipline for over
20 years now
And this doesn't just apply to open source! If you are a dedicated
user of Cadence ConceptHDL, then you learn pretty quickly to have perl
and other scripts where you exit the software, delete all the *.b and
*.c files, automatically do edits on the .a files, and then reopen the
software and do a hard save of the project. (You have to delete the
..b binary files, and .c files because these are compiled from the .a,
but have precedence over the .a (ascii) files.)
And users spend mucho bucks for this type of thing!
Charlie