kicad-developers team mailing list archive
Mailing list archive
Re: Re: libstdc++
Terry Barnaby <terry1@...>
Thu, 25 Mar 2010 08:00:56 +0000
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3
On 25/03/10 06:36, jean-pierre.charras@... wrote:
Dick Hollenbeck a écrit :
Good point. But I was thinking that Jean Pierre was statically linking
in the wxWidgets libraries to the apps. If not, I don't see how he has
gotten as far as he has with these "universal x86 linux binaries".
Of course, wxWidgets is linked statically (and it is also patched)
Preinstalled wxWidgets versions (when exist) never work.
I tried to link statically libsupc++ (under Ubuntu 9.10 and GCC 4.4),
and I was lucky! it worked:
1 - Locate libsupc++.a and add it to libs list
2 - use gcc instead of g++ to call the linker.
Note: I used my old makefiles to test that, because it was more easier
to quickly test different link options.
I now must test binaries under different Linux distribs.
As a matter of interest I presume kicad is thinking of making the binaries
available in simple tar form rather than packages as RPM or DEB packages ?
I wonder how many users install from this type of package these days. I
certainly haven't for many years.
I wonder if it would be better to more closely work with the Debian/Ubuntu
and Fedora/Centos packagers and help formulate standard *.spec etc files
for kicad as part of the source tree ? This will make it easier for the
packagers to package new releases and put it into the distribution's testing
or main repositories.
I note that someone was on this forum (Alain Portal?) recently asking for
help to package for Fedora, Redhat EL5/Centos5 recently. They tend to
know the particular distributions better and probably can help provide
the basic testing for binary packages on the core used platforms out there.
For the less used/maintained Linux distributions maybe kicad could produce
and distribute a RPM and DEB package source package that can
then be easily built by users (as well as the source in tar form) ? Also
it would be possible to produce a generic binary RPM and DEB with
statically linked libraries etc if needed.