FYI https://lists.launchpad.net/kicad-developers/msg21521.html
If that is accepted, that should get rid of the openssl dependency.
2015-11-02 19:14 GMT+01:00 Gregor Riepl :
>> Sorry, I rephrase: Kicad 4.0.0~rc1 is *not* installable in a Jessie
>> environment now, as long as you want to keep other
You will simply need to set -DCMAKE_BUILD_TYPE=Debug to cmake. And make
that a clean build. But please test on latest product, there have been pns
fixes after rc2 (in 6322).
Den 27/11/2015 19.39 skrev "Gregor Riepl" :
> I tested the new features of KiCad 4.0 quite extensively and found some
> pro
I tested the new features of KiCad 4.0 quite extensively and found some
problems with the avoid & shove code. It crashes quite frequently when there
are lots of obstacles.
To debug these, it would be great to have kicad-dbg package with debugging
symbols.
I tried to build one myself, but the pack
Yes, see http://kicad-pcb.org/post/kicad-4.0.0-RC2/
I think Wayne just forgot to tag it in the product branch.
Den 15/11/2015 16.17 skrev "Georges Khaznadar" :
> Hi,
>
> Thank you for the hints about flags for cmake.
>
> Nick Østergaard a écrit :
> > [...]
> > Also, the RC2 has now been released.
Hi,
Thank you for the hints about flags for cmake.
Nick Østergaard a écrit :
> [...]
> Also, the RC2 has now been released. Remember to update the
> KICAD_BUILD_VERSION string when you upgrade the source :)
Is this new release candidate supported officially ?
$ bzr log lp:kicad/4.0 2>/dev/null
Also, I have heard that the default install path definition is wrong
in the package in testing. It tries to set the KISYSMOD env var to
/usr/local/share/kicad/modules, while the footprints are installed to
/usr/share/kicad/modules.
You can fix this by setting -DDEFAULT_INSTALL_PATH=/usr when inv
Hi Gregor,
Please do as suggested by Wayne here:
https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg15285.html
I realise that it is not well documented yet, but anyways that is the
way to do it for now.
A note to everyone maintaining auto builders, please add
"-DKICAD_REPO_NAME
> I shall upload the fixed revision soon, and include your hints.
Ok, so I got kicad-4.0.0~rc1 from the package server today.
There's one thing I noticed: Version information seems to be missing.
The project window title shows "no-vcs-found-product".
I believe there's a script that generates vers
> Sorry, I rephrase: Kicad 4.0.0~rc1 is *not* installable in a Jessie
> environment now, as long as you want to keep other packages qui depend on
> libc prior to gcc-5.
Ah, that makes more sense.
I was only testing on stretch, where things are (mostly) settled in favor of
gcc5 AFAIK. Does jessie h
Hi Gregor,
Gregor Riepl a écrit :
> > It is uninstallable in Jessie and even in Stretch, due to the GCC-5
> > transition.
>
> I'm a bit confused there. How is gcc-5 affecting uninstallation?
Sorry, I rephrase: Kicad 4.0.0~rc1 is *not* installable in a Jessie
environment now, as long as you want
Hi Georges and everyone else.
I'm sorry that I left the discussion, I didn't see that it was moved to a
different bug report (which I wasn't subscribed to). Sorry.
> Also, where are your latest scripts located? Someone linked
> https://github.com/onitake/kicad.debian at one time on the list, but
Hello, I am uploading the new release, kicad_4.0.0~rc1-1, to Debian.
It should reach the pools in a few hours.
The new packages does work satisfactorily, from a schroot based upon
Debian/Sid.
It is uninstallable in Jessie and even in Stretch, due to the GCC-5
transition.
I could build a backport
2015-10-25 21:44 GMT+01:00 Georges Khaznadar :
> Hi Bas,
>
> Bas Wijnen a écrit :
>> Hi,
>>
>> On Sun, Oct 25, 2015 at 08:16:46PM +0100, Georges Khaznadar wrote:
>> > - I was touched by the issue which you already mentioned : building the
>> > core of Kicad depends on "calling home" to sourceforg
Hi Bas,
Bas Wijnen a écrit :
> Hi,
>
> On Sun, Oct 25, 2015 at 08:16:46PM +0100, Georges Khaznadar wrote:
> > - I was touched by the issue which you already mentioned : building the
> > core of Kicad depends on "calling home" to sourceforge, to get the
> > release 1.54.0 of Boost libraries.
>
Hello Nick,
Nick Østergaard a écrit :
> Why not just use the cmake option -DKICAD_SKIP_BOOST=ON ? You just
> need to make sure that the system you are building on have at least
> boost 1.56. Then no boost paching is needed.
Thank you for the hint, it is fine.
So, patches applied to Boost1.54.0
2015-10-25 20:16 GMT+01:00 Georges Khaznadar :
> Hello,
>
> I have got a few vacation days now, thank you for the tries which you
> documented recently.
>
> I began yesterday with some exploratory work:
>
> - rewrote the script get-kicad.sh; this one keeps the principles of the
> former one, whic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sun, Oct 25, 2015 at 08:16:46PM +0100, Georges Khaznadar wrote:
> - I was touched by the issue which you already mentioned : building the
> core of Kicad depends on "calling home" to sourceforge, to get the
> release 1.54.0 of Boost librari
Hello,
I have got a few vacation days now, thank you for the tries which you
documented recently.
I began yesterday with some exploratory work:
- rewrote the script get-kicad.sh; this one keeps the principles of the
former one, which are : source packages from three difference
locations are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Oct 22, 2015 at 04:10:58PM +0200, Nick Østergaard wrote:
> 2015-10-21 19:39 GMT+02:00 Bas Wijnen :
> > The default library path mentions lots of things on github (but it doesn't
> > seem
> > to look there, which is good). It doesn't include t
2015-10-21 19:39 GMT+02:00 Bas Wijnen :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I had some trouble building it, because cmake refused to build in-source. So
> I
> changed it to build out of source. The package installs fine, but so far I
> see
> some problems:
>
> The defa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I had some trouble building it, because cmake refused to build in-source. So I
changed it to build out of source. The package installs fine, but so far I see
some problems:
The default library path mentions lots of things on github (but it does
>>> Yes, both. Report upstream and patch it in Debian until they fix it.
>>> /usr/bin should only contain executables, nothing else.
>
>> I reported the problem upstream, but it looks like it will be addressed
>> post-release as it's not a critical issue.
>
> I agree. But it should be fixed in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 11, 2015 at 03:30:40PM +0200, Gregor Riepl wrote:
> > Yes, both. Report upstream and patch it in Debian until they fix it.
> > /usr/bin should only contain executables, nothing else.
>
> I reported the problem upstream, but it looks like
2015-10-11 15:30 GMT+02:00 Gregor Riepl :
> If you would like to help, you can check my packaging scripts at the github
> link I posted previously. Note that compiling KiCad takes a while, and partial
> rebuilds do not work very well. On the other hand, parallel builds are
> supported, but there m
Hi Bas
>> - UI plugins (_cvpcb.kiface, _eeschema.kiface, _gerbview.kifacem
>> _pcb_calculator.kiface, _pcbnew.kifacem _pl_editor.kiface) are currently
>> installed to /usr/bin. Should I report this upstream and request they be
>> installed to /usr/lib/kicad instead? Or write a patch specifically f
2015-10-10 19:00 GMT+02:00 Bas Wijnen :
>> - The KiCAD developers have designated their new stable release as 4.0.
>> Debian
>> currently uses a date+revision version scheme. Should the Debian versioning
>> be
>> changed to reflect this? What is the proper way to do so? 4.0+bzr is what
>> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
On Fri, Sep 18, 2015 at 04:20:15PM +0100, matt.notting...@zen.co.uk wrote:
> Going by the current blockages due to the GCC5 transition, even if you
> had it packaged now, it wouldn't be available!
Yes, I recently updated my system and ha
>> The existing build process is slightly quirky.
>> First, it executes cmake, make and make install in the main kicad source
>> tree.
>> This will build kicad for a /usr/local/bin prefix (I want to change that
>> later), then install it into a temp dir.
>
> Why don't you use -DCMAKE_PREFIX_PATH=
2015-09-21 12:42 GMT+02:00 Gregor Riepl :
>>> More importantly, how do all these sub-packages tie into the build process?
>>> I assume that the main kicad CMakeFiles will only build kicad itself, and
>>> not
>>> pick up additional subdirectories like kicad-i18n, kicad-doc, kicad-library
>>> or
>>
>> More importantly, how do all these sub-packages tie into the build process?
>> I assume that the main kicad CMakeFiles will only build kicad itself, and not
>> pick up additional subdirectories like kicad-i18n, kicad-doc, kicad-library
>> or
>> library-repos. The current Debian packaging script
2015-09-20 14:41 GMT+02:00 Gregor Riepl :
>> The doc source is available at https://github.com/kicad/kicad-doc
>>
>> It takes quite some time to build with asciidoc, so you might want to
>> fetch the precompiled docs from http://docs.kicad-pcb.org/
>
> Thanks, Nick.
>
> I'm not strongly familiar wi
> The doc source is available at https://github.com/kicad/kicad-doc
>
> It takes quite some time to build with asciidoc, so you might want to
> fetch the precompiled docs from http://docs.kicad-pcb.org/
Thanks, Nick.
I'm not strongly familiar with the DFSG rules concerning documentation, but I
w
2015-09-19 16:24 GMT+02:00 Gregor Riepl :
>> Just for your information. The old kicad doc bzr repo,
>> https://code.launchpad.net/~kicad-developers/kicad/doc is not to be
>> used any more. The translations have moved to
>> https://github.com/KiCad/kicad-i18n/
>
> Thanks, I'll use that.
> But the re
> Just for your information. The old kicad doc bzr repo,
> https://code.launchpad.net/~kicad-developers/kicad/doc is not to be
> used any more. The translations have moved to
> https://github.com/KiCad/kicad-i18n/
Thanks, I'll use that.
But the repository only contains the .po files.
Where can I f
Just for your information. The old kicad doc bzr repo,
https://code.launchpad.net/~kicad-developers/kicad/doc is not to be
used any more. The translations have moved to
https://github.com/KiCad/kicad-i18n/
2015-09-18 17:25 GMT+02:00 Gregor Riepl :
> Hi Matt
>
>> Going by the current blockages due
Hi Matt
> Going by the current blockages due to the GCC5 transition, even if you
> had it packaged now, it wouldn't be available!
>
> Thanks for letting us know that you hope to start work on it soon. Let
> us know if there is testing or other things we could do to help.
It looks like the blocka
Hi Georges,
Thanks for your reply.
Going by the current blockages due to the GCC5 transition, even if you
had it packaged now, it wouldn't be available!
Thanks for letting us know that you hope to start work on it soon. Let
us know if there is testing or other things we could do to help.
Thank
Hi Georges
> many people are eager to have a package of the so long awaited stable
> version of Kicad in Debian. I am currently the maintainer of this
> package.
>
> unfortunately, this event happens when I have an increase of business: I
> work as a teacher in France, and now is a tought period:
Hi Simon, Gregor, Matt,
many people are eager to have a package of the so long awaited stable
version of Kicad in Debian. I am currently the maintainer of this
package.
unfortunately, this event happens when I have an increase of business: I
work as a teacher in France, and now is a tought period
39 matches
Mail list logo
