Bug 120533 - ebuild request: kicad
|
Bug#:
120533
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: calchan@gentoo.org
|
Reported By: dev@urriellu.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: ebuild request: kicad
|
|
Keywords: REQUEST
|
|
Status Whiteboard:
|
|
Opened: 2006-01-27 07:39 0000
|
...I forgot to mention, I recommend sci-electronics...
Firstly, thanks for the ebuild. I was working toward my first ebuild with
kicad, but had only got as far as sorting out necessary patches and a build
script.
FYI, your ebuild ran successfully on my x86 system, given the necessary extra
keyword. Note also that 20010119 kicad sources are available, which used after
making the trivial changes to your ebuild.
There is a collection of additional materials from the kicad site: component
library, demos, help, modules, template. Have you any intention of writing
ebuilds to fetch and install these? If not, I'd be willing to make some/all of
these - a learning exercise for me.
(In reply to comment #1)
> Created an attachment (id=80229) [edit] [details]
> kicad-0.0.20060118.ebuild
>
> First shot at the ebuild. Compiles fine under amd64. Not tested thoroughly,
> yet...
>
(In reply to comment #5)
> Firstly, thanks for the ebuild. I was working toward my first ebuild with
> kicad, but had only got as far as sorting out necessary patches and a build
> script.
You're welcome...
> FYI, your ebuild ran successfully on my x86 system, given the necessary extra
> keyword. Note also that 20010119 kicad sources are available, which used after
> making the trivial changes to your ebuild.
I didn't use the latest version because it was in different dir than the others
so when new version is released, the link becomes dead. :-(
> There is a collection of additional materials from the kicad site: component
> library, demos, help, modules, template. Have you any intention of writing
> ebuilds to fetch and install these? If not, I'd be willing to make some/all of
> these - a learning exercise for me.
>
Feel free to continue, my ebuild was meant as a starting point. I don't even
use kicad :-)
The author of kicad has obliged by making the current-version sources also
available in the old_versions collection. The ebuilds can now easily use the
current release and I'm having a go at making an updated ebuild based on
Radek's original ebuild.
Also, the support material I mentioned might be better handled out of portage
as there is no version numbering.
Created an attachment (id=83122) [details]
kicad-20060321.ebuild
Could you guys please try this ebuild ? It's for the latest available version,
and it installs all additional material (libraries, modules, templates, demos,
etc...) plus Wings for 3D models.
Can you please make it selectable (using the USE flag) to decide whether you
want the docs/demos/whatever installed? It's too much bloat... :-(
Denis, just to confirm: it works fine here.
Created an attachment (id=83238) [details]
kicad-20060321.ebuild
New ebuild. Changelog :
* Cleaned-up wxGTK setup and added opengl detection.
* Added desktop menu entry.
* Added evince support to already existing xpdf, gpdf, and konqueror support
(this will be reported upstream).
Radek : I understand your problem with the total size. However adding a USE
flag isn't something that I can't decide alone. So, I talked about this issue
with a gentoo dev, and he said in that particular case it wasn't an option.
Paul, FYI your ebuild worked for me too - many thanks.
Can I draw your attention though, to comment 6 from Radek regarding the
location of the current kicad sources? Since then, as in Comment 8 from me, the
kicad author has obliged by adding a copy of the current sources to
old_versions. This ought to prevent older kicad ebuilds from breaking when new
sources are released.
Regarding the bloat problem, I agree with Radek that control over the
installation of docs, demos, library files etc. should be an option. Instead of
a USE flag, do you think that a set of ebuilds would work? For example,
kicad-component_doc, kicad-library, kicad-help etc.
The component doc is a collection of technical data sheets for the library
components. A PCB designer is quite probably already in possession of the
required data sheets prior to design entry in kicad, so component_docs is not
essential. I think I see your reason for using the precompiled version in
addition to the current sources. I would propose that library updates could be
handled using an rsync-like action to avoid the duplication that can be
expected with frequent kicad updates.
Kicad is now in CVS. So give it a few hours and then you can emerge it.
Testing on amd64:
eeschema doesn't link even with wxwidget >= 2.6.3.2
(In reply to comment #18)
> Testing on amd64:
> eeschema doesn't link even with wxwidget >= 2.6.3.2
OK. You should have reopened the bug, though, because I found you report only
by luck.
Could we please get more details on the linking failure, as well as the output
of 'emerge info' on your system ?
Denis.
(In reply to comment #19)
> (In reply to comment #18)
> > Testing on amd64:
> > eeschema doesn't link even with wxwidget >= 2.6.3.2
>
> OK. You should have reopened the bug, though, because I found you report only
> by luck.
>
> Could we please get more details on the linking failure, as well as the output
> of 'emerge info' on your system ?
>
> Denis.
Hi,
Sorry but if I remember correctly, I wasn't able to change the bug status
because I wasn't the 'owner' of this bug.
It's seems to be a problem with wxwidget too old version.
I have tried with wxGTK-2.6.2-r1 and =x11-libs/wxGTK-2.6.3.2 ~amd64.
Please find here after the error messages and the output of emmerge -info.
--Thierry
pinedit.o: In function
`WinEDA_PinPropertiesFrame::WinEDA_PinPropertiesFrame()':
pinedit.cpp:(.text+0x9f): undefined reference to `vtable for
WinEDA_PinPropertiesFrame'
pinedit.o: In function
`WinEDA_PinPropertiesFrame::WinEDA_PinPropertiesFrame()':
pinedit.cpp:(.text+0x20f): undefined reference to `vtable for
WinEDA_PinPropertiesFrame'
pinedit.o: In function
`WinEDA_PinPropertiesFrame::WinEDA_PinPropertiesFrame(WinEDA_LibeditFrame*,
int, wxString const&, wxPoint const&, wxSize const&, long)':
pinedit.cpp:(.text+0x2b2b): undefined reference to `vtable for
WinEDA_PinPropertiesFrame'
pinedit.o: In function
`WinEDA_PinPropertiesFrame::WinEDA_PinPropertiesFrame(WinEDA_LibeditFrame*,
int, wxString const&, wxPoint const&, wxSize const&, long)':
pinedit.cpp:(.text+0x35db): undefined reference to `vtable for
WinEDA_PinPropertiesFrame'
symbtext.o: In function
`WinEDA_bodytext_PropertiesFrame::WinEDA_bodytext_PropertiesFrame()':
symbtext.cpp:(.text+0x9f): undefined reference to `vtable for
WinEDA_bodytext_PropertiesFrame'
symbtext.o: In function
`WinEDA_bodytext_PropertiesFrame::WinEDA_bodytext_PropertiesFrame()':
symbtext.cpp:(.text+0x20f): undefined reference to `vtable for
WinEDA_bodytext_PropertiesFrame'
symbtext.o: In function
`WinEDA_bodytext_PropertiesFrame::WinEDA_bodytext_PropertiesFrame(WinEDA_LibeditFrame*,
int, wxString const&, wxPoint const&, wxSize const&, long)':
symbtext.cpp:(.text+0x1494): undefined reference to `vtable for
WinEDA_bodytext_PropertiesFrame'
symbtext.o: In function
`WinEDA_bodytext_PropertiesFrame::WinEDA_bodytext_PropertiesFrame(WinEDA_LibeditFrame*,
int, wxString const&, wxPoint const&, wxSize const&, long)':
symbtext.cpp:(.text+0x1984): undefined reference to `vtable for
WinEDA_bodytext_PropertiesFrame'
collect2: ld returned 1 exit status
make[1]: *** [eeschema] Error 1
Gentoo Base System version 1.6.14
Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.6-r3,
2.6.15-gentoo-r7-amd64 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r7-amd64 x86_64 AMD Athlon(tm) 64 Processor 3400+
dev-lang/python: 2.4.2
dev-python/pycrypto: [Not Present]
dev-util/ccache: [Not Present]
dev-util/confcache: [Not Present]
sys-apps/sandbox: 1.2.12
sys-devel/autoconf: 2.13, 2.59-r7
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils: 2.16.1
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LINGUAS="fr en"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa arts audiofile avi berkdb bitmap-fonts busybox bzip2 cdr
cli crypt cups curl dhcp dri dvd eds emboss encode expat extensions fam flac
foomaticdb fortran ftp gcc gdb gif gimp gpm gstreamer gtk gtk2 iconv idn
ieee1394 imlib iptables isdnlog java javascript jpeg kde lcms lm_sensors
logrotate lzw lzw-tiff mad md5sum mng mozilla mp3 mpeg ncurses nls nptl
nsplugin ogg opengl pam pcre pdflib perl png pppd python qt quicktime readline
reflection scanner sdl session spell spl ssl syslog tcpd tiff truetype
truetype-fonts type1-fonts udev urandom usb video_cards_nvidia vorbis vxwindows
xft xine xml2 xmms xorg xpm xprint xv zlib linguas_fr linguas_en userland_GNU
kernel_linux elibc_glibc"
Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, MAKEOPTS,
PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS, PORTDIR_OVERLAY
> Sorry but if I remember correctly, I wasn't able to change the bug status
> because I wasn't the 'owner' of this bug.
Actually, opening a new one was probably the best choice.
> It's seems to be a problem with wxwidget too old version.
> I have tried with wxGTK-2.6.2-r1 and =x11-libs/wxGTK-2.6.3.2 ~amd64.
I don't think so. I may be wrong, but I'm convinced that's a real bug from
Kicad itself. The problem is I don't have access to an amd64 machine as often
as I'd like. When I tried this ebuild on one, it worked without a hitch so I
marked it ~amd64.
So here's the deal. You contact me directly by email, and we'll sort this out
together. Something tells me you might prefer to use French, so feel free to do
so.
Denis.
