Re: Exportability of EDA industry from North America?
From: Chuck Harris (cf-NO-SPAM-harris_at_erols.com)
Date: 01/18/05
- Previous message: Mark Jones: "Re: Wild Weather"
- In reply to: Chuck Harris: "Re: Exportability of EDA industry from North America?"
- Next in thread: Stuart Brorson: "Re: Exportability of EDA industry from North America?"
- Reply: Stuart Brorson: "Re: Exportability of EDA industry from North America?"
- Reply: Stuart Brorson: "Re: Exportability of EDA industry from North America?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 17 Jan 2005 22:44:37 -0500
Chuck Harris wrote:
> Hi Ales,
>
> Ales Hvezda wrote:
>
>> Hi,
>>
>> I usually like spending my free time working on the code rather than
>> posting to USENET, but I want to address some of the points from the
>> previous poster in this thread.
>
>
> Thank you, I appreciate your time. I would prefer not to use this
> forum for detailed debugging, but since I started this, and have no
> interest in performing a hit-and-run tar & feather job, I guess we have
> to resolve the problems here in public.
>
Hi Ales and Stuart,
I have finally spent the time to track down all of the problems I was
having installing the gEDA suite, and I now think I have a successful
build from using the CDROM.
The two things that messed up my build were:
1) I installed pkg-config using the package included with gEDA, only
I think I built it as user, and installed it as root. This made the
search paths all be based in my home directory, and not in /usr.
My redhat installed pkg-config was in /usr/bin, and my gEDA installed
pkg-config was in /usr/local/bin. /usr/local/bin comes first in my
path, so I was working with the defective version. That's what I get
for trying to upgrade pkg-config outside of the rpm/apt-get system.
2) my /etc/ld.so.conf file was stock RedHat, with some additions by other
package installations. It did not include /usr/local/lib in its search
paths.
Problems/complaints:
1) I don't like to see LD_LIBRARY_PATH and PKG_CONFIG_PATH globally set.
They provide a capability for testing new versions of system libraries.
I don't believe they were intended to be used system wide. For that
you should add the path to the appropriate /etc/xxxx.conf file. It's
a shame there isn't one for pkg-config (AFAIK)
2) The schematics in the examples are all composed of main pages with
the transistors and diodes being subpages. There is no obvious (to me
the new user) way of making the link so the transistors appear on the
schematic. Examples are presumably meant for new inexperienced users,
and as such should work flawlessly.
3) There are no examples of projects for use with the gEDA project manager.
4) I know it is easier for the developer to run ./configure at the root of
each package, but there ought to be a way to only do it once for the whole
system when you are using Stuart's installer program.
5) There is really no good reason to rebuild and reinstall the symbols a
dozen or more times. It significantly adds to the build time.
Anyway, it seems to be running, and I will begin to explore the construction
of a project from start to finish. I'm sure that task will keep me quite
busy.
Thanks for the help, and inspite of the problems I had installing, please
know that I think you guys have done a magnificent jog thus far.
-Chuck Harris
- Previous message: Mark Jones: "Re: Wild Weather"
- In reply to: Chuck Harris: "Re: Exportability of EDA industry from North America?"
- Next in thread: Stuart Brorson: "Re: Exportability of EDA industry from North America?"
- Reply: Stuart Brorson: "Re: Exportability of EDA industry from North America?"
- Reply: Stuart Brorson: "Re: Exportability of EDA industry from North America?"
- Messages sorted by: [ date ] [ thread ]