Hi.
I'd like to get a list of what command line parameters
eagle can be run with on linux.
I'm looking for a way to open a (schematic) file from the
command line (so that i can create a .desktop file to
open eagle files).
Anybody? Thanks.
Hi.
I'd like to get a list of what command line parameters
eagle can be run with on linux.
I'm looking for a way to open a (schematic) file from the
command line (so that i can create a .desktop file to
open eagle files).
Anybody? Thanks.
On 03/03/2010 06:00 PM, Thomas Lundgaard wrote:
Chuck Huber wrote:
Not sure about schematics specifically, but
shell> eagle eagle.epf
works at the project level. I have also added a file
association in
Konqueror to associate .epf files with eagle. So a
single-click in
Konqueror (or any other file browser) will launch
eagle.
That doesn't works for schematics files. If I run
sheel> eagle document.sch
eagle will start and first complain that the directory
document.sch doesn't exists (oviously, it's a file) and
then sets the library directory in Options >
Directories to /home/user/path/to/document.sch. I
really consider this weird behaviour, don't know if
it's a bug?
I'm using eagle 5.7.0 on Archlinux.
Good morning,
That is odd behavior. I did a little experimenting this morning and
found that I could supply eagle with any .sch .epf .brd or .lbr, and it
starts without complaint. The elements in Options->Directories did not
change.
Furthermore, I can:
shell> eagle 513941.sch 513951.brd
and I get a control panel, a schematic editor, and a layout editor windows.
I, too, am using 5.7.0. I'm running opensuse 11.1, KDE4 window manager.
"uname -a" shows
Linux lightning 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100
x86_64 x86_64 x86_64 GNU/Linux
This is a fairly new kernel - I installed it two days ago, but I doubt
that has anything to do with the behavior exhibited by your installation.
I'm not sure if this provides any useful information.
Enjoy,
- Chuck
Hi All,
Thanks for your help so far.
I found the issue now. I'm running archlinux and for some reason the eagle
package in AUR installs an eagle executable in both /usr/bin/eagle and
/opt/eagle-5.7.0/bin/eagle. If i run
/usr/bin/eagle file.sch
it does the aforementioned weired behaviour, but if i run:
/opt/eagle-5.7.0/bin/eagle file.sch
it opens the schematic as it's supposed to.
I guess it's some sort of packaging issue, so I'll post it in the AUR
comments.
Cheers, Thomas
Hi All,
Thanks for your help so far.
I found the issue now. I'm running archlinux and for some reason the eagle
package in AUR installs an eagle executable in both /usr/bin/eagle and
/opt/eagle-5.7.0/bin/eagle. If i run
/usr/bin/eagle file.sch
it does the aforementioned weired behaviour, but if i run:
/opt/eagle-5.7.0/bin/eagle file.sch
it opens the schematic as it's supposed to.
I guess it's some sort of packaging issue, so I'll post it in the AUR
comments.
Cheers, Thomas