On 17.01.12 20:30, gene heskett wrote:
> On Tuesday, January 17, 2012 07:15:33 PM Fox Mulder did opine:
> > Am 17.01.2012 21:47, schrieb gene heskett:
> > > Checking requirements, I see that libpng14.so.14 is required so
> > > you helped me build a script: gene@shop:/opt/eagle-6.1.0$ cat
> > > bin/eagle LD_LIBRARY_PATH="$(dirname "$0")" "$(dirname "$0")/eagle.orig"
> > > $@
That's a good way to do it if you want to keep the .so with eagle.
Another way is to drop a copy of it into /lib, and then run ldconfig,
to update the cache for ld.so, so it can find it without further ado.
A third way is to leave the .so in its current odd spot, and just add
the path to /etc/ld.so.conf before running ldconfig.
> > > It doesn't complain about a missing library so I assume that is
> > > working, but for a universal launcher, should I not have a /usr/bin
> > > bash script that first does a cd to /opt/eagle-6.1.0/ in order to
> > > setup the pwd, and then do a 'bin/eagle'? In any event, it seems to
> > > work.
Then it's fine. Setting LD_LIBRARY_PATH is an entirely acceptable way to
get by, even if it can be done without a script. Those GUI configs you did
(Options -> Directories?) allow eagle to find your projects, so there's
no need for a cd.
...
> Ah, now I see a totally different selection window. I left click on the +
> sign of library you sent, and see the devices name. Now I have managed to
> get 3 copies of it planted on the schematic,
If that's via the "Add" icon on the schematic editor, then you're cooking.
> & a few wires drawn, at which point I note that pin assignments on the
> device aren't exactly correct, and to match the device itself, I'll
> have to swap on end of it or the other around as the GND's are on the
> diagonal corners. I'll need to think on which I swap that around as I
> assume the xml part description in the library is where to fix it.
If the part is OK, but for the pinout, the easiest fix is to create a
variant of the existing part, if you want to keep the original pinout as
well. To avoid loss when updating the supplied libraries, and to keep
customised stuff handy, it is good to copy the part over to your own
library, and edit that, I think.
> Apparently not, the schematic doesn't change with the current contents
> of the library. Throw it out & start over.
Nope, to update the library info used in an open schematic editor, hit
Library->Update and select the modified library, or just use
Library->Update_All.
> Probably tomorrow after I read for a couple hours.
Yeah. And they claim GUIs are intuitive.
...
> > > But in eagle, I have yet to find that command line box talked
> > > about in the tuts so I can't run the setup utility it talks about
> > > in its install.html.
Any of eagle's commands can be run in that white strip at the top of the
schematic editor's drawing area. There's a blinking cursor, inviting
input.
> If I fix the library, will that fix the schematic when it is next
> loaded?
If the library has changed, then eagle usually warns on next startup,
that schematic and/or board may be affected, and makes you click to
confirm, IIRC.
A Library->Update after editing the part naturally avoids such
surprises.
Erik
--
The meta-problem here is that the configuration wizard does all the approved
rituals (GUI with standardized clicky buttons, help popping up in a browser,
etc. etc.) but doesn't have the central attribute these are supposed to achieve:
discoverability. That is, the quality that every point in the interface has
prompts and actions attached to it from which you can learn what to do next.
- Eric Raymond, in "The Luxury of Ignorance."
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
