The newly introduced KICAD_CONFIG_HOME variable has a minor typo in a comment
line. The attached patch corrects this.
Steve
>From 607f01077e8e0dc77371895309be2697c7da5dd0 Mon Sep 17 00:00:00 2001
From: "Steven A. Falco" <stevenfa...@gmail.com>
Date: Fri, 27 Apr
On 05/10/2018 09:15 AM, Jeff Young wrote:
> Oh, and yes the diff issue was line-endings. I tried CLion’s visual diff
> tool and it worked fine.
Regarding line-endings, git can help keep Linux, Windows, and Mac users happy.
For details, please search for core.autocrlf in the following page:
rom 607f01077e8e0dc77371895309be2697c7da5dd0 Mon Sep 17 00:00:00 2001
From: "Steven A. Falco" <stevenfa...@gmail.com>
Date: Fri, 27 Apr 2018 09:29:53 -0400
Subject: [PATCH] Fix comment typo.
Comment has XDG_CONFIG_HOME, but it should be KICAD_CONFIG_HOME.
---
common/common.cpp | 2 +-
1 file changed
@lkundrak, the Fedora KiCad package admin, should pick up my -rc2 changes very
soon - they will go into Fedora Rawhide.
So we should be well positioned for a stable release to appear there soon after
everything is tagged for the official 5.0.0 release.
Steve
On 06/12/2018 10:18 AM,
I am starting to look at packaging KiCad 5.0.0 for Fedora. I can download
source tars from the 4.X series using URLs like:
https://code.launchpad.net/kicad/4.0/4.0.0-rc2/+download/kicad-4.0.0-rc2.tar.xz
However, if I try this with 5.0, I get an error:
via git-archive, but I
think it would be preferable if the 5.x tars followed the 4.0.7 structure and
had a top level directory.
Steve
On 06/01/2018 06:18 PM, Steven A. Falco wrote:
> On 06/01/2018 05:17 PM, Steven A. Falco wrote:
>> On 06/01/2018 05:10 PM, Wayne Stambaugh wrote:
On 06/01/2018 05:10 PM, Wayne Stambaugh wrote:
> On 6/1/2018 3:58 PM, Steven A. Falco wrote:
>> On 06/01/2018 03:35 PM, Wayne Stambaugh wrote:
>>> If you are just looking for a source archive, then I can upload one
>>> launchpad for rc2. If you are looking for rc2 of li
On 06/01/2018 05:17 PM, Steven A. Falco wrote:
> On 06/01/2018 05:10 PM, Wayne Stambaugh wrote:
>> On 6/1/2018 3:58 PM, Steven A. Falco wrote:
>>> On 06/01/2018 03:35 PM, Wayne Stambaugh wrote:
>>>> If you are just looking for a source archive, then I can upload one
&
On 06/01/2018 03:35 PM, Wayne Stambaugh wrote:
> If you are just looking for a source archive, then I can upload one
> launchpad for rc2. If you are looking for rc2 of libraries, doc, i18n,
> etc, then that is far more involved.
I guess maybe I'm asking for too much, but I'd like to be able to
On 06/02/2018 01:29 AM, Carsten Schoenert wrote:
> Am 02.06.2018 um 02:46 schrieb Steven A. Falco:
>> Wayne - I downloaded the kicad-5.0.0-rc2.tar.xz file you set up.
>> Unfortunately it looks like it was created from inside the
>> kicad-5.0.0-rc2 directory - there is n
e more I
> like it.
Thanks! I like it too. :-)
Steve
>
> Cheers,
>
> Wayne
>
> On 6/1/2018 8:46 PM, Steven A. Falco wrote:
>> Wayne - I downloaded the kicad-5.0.0-rc2.tar.xz file you set up.
>> Unfortunately it looks like it was created from inside the kicad
A small typo - the last note in the file has the phrase "by using opening".
That should either be "by using" or "by opening".
Steve
On 06/22/2018 12:10 PM, Wayne Stambaugh wrote:
> I pushed the v5 upgrade document to my personal repo[1] on git hub. I
> made it part of the KiCad
If possible, it would also be great if a tar file for -rc3 could be uploaded to
launchpad, analogous to what was done for -rc2.
We do have an -rc2 build in the official Fedora Rawhide now, and I'm ready to
step that up to -rc3 once available.
Thanks,
Steve
On 06/29/2018 10:15
Stambaugh wrote:
> I will do this when I tag rc3. I think I have done it for every release tag.
>
> On 06/30/2018 08:28 AM, Steven A. Falco wrote:
>> If possible, it would also be great if a tar file for -rc3 could be uploaded
>> to launchpad, analogous to what was done for -
On 02/04/2018 03:46 PM, Nick Østergaard wrote:
> I just did test cdad023 by compiling myself, but I don't get any issue with
> the filling here.
>
> This is on archlinux.
>
> 2018-02-04 3:40 GMT+01:00 Steven A. Falco <stevenfa...@gmail.com
> <mailto:stevenfa...@gma
I have been using Kicad 4.0.7 successfully. I just decided to give the
upcoming 5 series a try, so I set up a Fedora VM and loaded the COPR
100:r11969.dc66b73-nightlies.fc27 build.
Most everything I've tried works fine, but zone fill in pcbnew just appears to
hang. Running "top" doesn't show
On 02/03/2018 12:28 PM, Tomasz Wlostowski wrote:
> On 03/02/18 16:57, Steven A. Falco wrote:
>> I have been using Kicad 4.0.7 successfully. I just decided to give the
>> upcoming 5 series a try, so I set up a Fedora VM and loaded the COPR
>> 100:r11969.dc66b73-nightlies.f
I continue to have problems performing a zone fill with the latest kicad 5
builds. A copy of the project that is causing me trouble is here:
https://www.dropbox.com/sh/lw7lhg7jyigvyi7/AAB0ALAWmYS2LmOlw7-spqP6a?dl=0
I can reproduce the problem on both a Windows 10 VM, running
On 02/08/2018 04:28 PM, Tomasz Wlostowski wrote:
> On 08/02/18 21:15, Steven A. Falco wrote:
>> I continue to have problems performing a zone fill with the latest kicad 5
>> builds. A copy of the project that is causing me trouble is here:
>>
>> https://www.dro
On 02/03/2018 04:41 PM, Henner Zeller wrote:
> On 3 February 2018 at 13:29, Steven A. Falco <stevenfa...@gmail.com> wrote:
>> On 02/03/2018 12:40 PM, Steven A. Falco wrote:
>>> On 02/03/2018 12:28 PM, Tomasz Wlostowski wrote:
>>>> On 03/02/18 16:57, Steven A.
On 02/03/2018 08:40 PM, Steven A. Falco wrote:
> On 02/03/2018 07:04 PM, Tomasz Wlostowski wrote:
>> On 03/02/18 18:40, Steven A. Falco wrote:
>>> Thanks, but now I'm confused.
>>
>> Sorry, I got confused by the date of your PCB file. You're indeed
>> running f
On 02/03/2018 12:40 PM, Steven A. Falco wrote:
> On 02/03/2018 12:28 PM, Tomasz Wlostowski wrote:
>> On 03/02/18 16:57, Steven A. Falco wrote:
>>> I have been using Kicad 4.0.7 successfully. I just decided to give the
>>> upcoming 5 series a try, so I set up a Fe
On 02/03/2018 07:04 PM, Tomasz Wlostowski wrote:
> On 03/02/18 18:40, Steven A. Falco wrote:
>> Thanks, but now I'm confused.
>
> Sorry, I got confused by the date of your PCB file. You're indeed
> running fresh Feb 2018 build. I tried opening your design in today's
> latest
;
> Regards,
> Orson
>
> On 02/08/2018 09:15 PM, Steven A. Falco wrote:
>> I continue to have problems performing a zone fill with the latest kicad 5
>> builds. A copy of the project that is causing me trouble is here:
>>
>> https://www.dropbox.com/sh/lw7lhg7jyi
On 02/12/2018 12:05 PM, Jeff Young wrote:
> I want to test the progress reporter for zones to make sure I didn’t break
> anything.
>
> Anyone have a file with a bunch of zones that isn’t quite as diabolical as
> JP’s WRS?
I have one with 7 zones or so in this folder:
++ is insufficient to
switch compilers.
Steve
> On 02/07/2018 02:34 PM, Steven A. Falco wrote:
>> On 02/07/2018 08:16 AM, Maciej Sumiński wrote:
>>> Hi Steven,
>>>
>>> Could you confirm that e0f7958d breaks Fedora builds? It is a bit
>
ave ~40 years of embedded C development experience, but very little C++.
Steve
>
> On 02/07/2018 02:13 PM, Steven A. Falco wrote:
>> On 02/07/2018 06:37 AM, Nick Østergaard wrote:
>>> Hi
>>>
>>> Just a heads up.
>>>
>>> I think e0f7958db
On 02/07/2018 06:37 AM, Nick Østergaard wrote:
> Hi
>
> Just a heads up.
>
> I think e0f7958dbdab89f38bacc6a567e21b38a0926aee broke the build on fedora26
> and fedora 27 which uses glm 0.9.8.4. Caused by fix in
> https://bugs.launchpad.net/kicad/+bug/1746546.
>
>
On 02/23/2018 04:05 PM, Wayne Stambaugh wrote:
> On 02/23/2018 03:43 PM, Andy Peters wrote:
>>
>>
>>> On Feb 23, 2018, at 6:05 AM, Jeff Young wrote:
>>>
>>> This patch addresses code review comments to the Inc/DecAlpha bug fix.
>>>
>>>
s/6
> <https://bugs.launchpad.net/kicad/+bug/1746546/comments/6>
>
> On 02/07/2018 03:53 PM, Steven A. Falco wrote:
> > On 02/07/2018 08:46 AM, Maciej Sumiński wrote:
> >> Thank you Steven, that is a valuable data point. Would you try updating
> >> gc
ke} INSTALL="install -p" DESTDIR=%{buildroot} install
+popd
+
+# 3D models
+pushd %{name}-packages3D-%{version}/
+%{__make} INSTALL="install -p" DESTDIR=%{buildroot} install
+popd
+
+# Templates
+pushd %{name}-templates-%{version}/
+%{__make} INSTALL="install -p" DESTDI
I am using Fedora 28, and have just noticed a strange crash. This happens with
5.0.0 and also with the latest nightly (r13432-e750382e).
I've got to assume I'm doing something wrong, but I am baffled, so I want to
see what folks think.
I've attached a backtrace. The way I cause this crash is
ian. However, I note that this
> is a wxWidgets assertion, which should be disabled for release builds. Since
> you did the packaging for Fedora, do you have a build log? Alternatively, do
> you see this assertion when running a local build?
>
> -S
>
> Am Mo., 30. Juli 201
Juli 2018 um 09:51 Uhr schrieb Steven A. Falco
> mailto:stevenfa...@gmail.com>>:
>
> A little more info. My KiCad build works fine on my laptop, which has
> both an Intel and Nvidia graphics chip on its motherboard. The Nvidia
> framebuffer device is using the nouveau d
keep experimenting, but I'm not sure what to try next. So far, in all
other respects, I don't see a problem with the Nvidia driver.
Steve
On 07/30/2018 10:08 PM, Steven A. Falco wrote:
> Thanks for looking at it. Regarding your first question, I've placed a copy
> of my bui
t; wrote:
>
> Hi Steve, some comments inlined below:
>
> On Wed, Aug 8, 2018 at 4:13 PM, Steven A. Falco <mailto:stevenfa...@gmail.com>> wrote:
>
> I'm packaging KiCad for Fedora. The web page:
> http://kicad-pcb.org/about/licenses/ <http://ki
I've made a build of 5.0.0 for Fedora rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1129084
This will take a little while to push out to the Fedora mirror servers.
Steve
On 07/20/2018 07:53 AM, Wayne Stambaugh wrote:
> Great work Rene and thanks to all of the library
fedora download page if at all needed?
>
> http://kicad-pcb.org/download/fedora/
>
> Nick
> Den fre. 20. jul. 2018 kl. 20.02 skrev Steven A. Falco
> :
>>
>> I've made a build of 5.0.0 for Fedora rawhide:
>>
>> https://koji.fedoraproject.org/koji/buildinfo?bu
make a pull request for it.
>
> Of course, if you don't want / can't do that, let us know and one of
> us can handle it too.
>
> Adam
> On Fri, Jul 20, 2018 at 8:44 PM Steven A. Falco wrote:
>>
>> I looked at that page, and I opened a bug to update the tex
un, Jul 22, 2018 at 9:08 AM Nick Østergaard wrote:
>>
>> Thank you.
>> Den søn. 22. jul. 2018 kl. 15.04 skrev Steven A. Falco
>> :
>>>
>>> I took a look, and no changes to the web site are needed regarding Fedora
>>> packages. Thanks for the poin
t;
> On 30/06/18 23:56, Steven A. Falco wrote:
> > Thank you!
> >
> > There are three repos not yet tagged with rc3 on github - two are
> probably awaiting translation work: kicad-doc and kicad-i18n. Also not
> tagged: kicad-templates. Once everything ca
On 03/06/2018 01:51 PM, Kevin Cozens wrote:
> On 2018-03-06 01:40 PM, Steven A. Falco wrote:
>> I just finished building 49486b83 for Linux (Fedora 27) and immediately upon
>> starting eechema from the main kicad window, I get an assert in
>> src/gtk/scrolwin.cpp at line 2
On 03/12/2018 10:23 AM, Jon Evans wrote:
> I have seen multiple users who run nightlies think they have RC2 because they
> read "5.0.0-rc2" and stop reading after that :-)
> Maybe we should switch the tag back to "5.0-dev" between RC releases?
> I think all of us developers are going to look up
The fix is good. I also noted that on the launchpad bug. Thanks for resolving
this issue.
Steve
On 03/06/2018 04:08 PM, Jeff Young wrote:
> It’s up, Kevin. Thanks for offering to test.
>
> Cheers,
> Jeff.
>
>
>> On 6 Mar 2018, at 20:33, Kevin Cozens wrote:
>>
>>
I just got a build error on Linux, at git commit 218f66a08, which appears to be
the latest commit.
In file included from
/builddir/build/BUILD/kicad-r12311-218f66a0/pcbnew/specctra_import_export/specctra.h:36:0,
from
and I'll report back with my findings.
Steve
On 03/05/2018 01:43 PM, Seth Hillbrand wrote:
> Does the compile error exist after you make clean and re-make?
>
> 2018-03-05 10:20 GMT-08:00 Steven A. Falco <stevenfa...@gmail.com
> <mailto:stevenfa...@gmail.com>>:
>
On 03/05/2018 02:13 PM, Steven A. Falco wrote:
> Yes it does. I'm building on Fedora via the "mock" tool, which always starts
> from an empty directory. Just to be sure, I removed the entire "mock"
> working area, and I even re-downloaded the source repositories. I'l
I'm going to retract this report. It builds correctly on copr, so the problem
must be something in my local setup.
Sorry for the noise.
Steve
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
ace the v4 library repo with the v5 symbol, footprint, and 3d
repos.
Please let me know if there are any problems.
Steve
> 2018-02-26 4:48 GMT+01:00 Steven A. Falco <stevenfa...@gmail.com
> <mailto:stevenfa...@gmail.com>>:
>
> On 02/25/2018 07:3
Now that 5.0.0-rc1 is out, I'd like to ask how this should be packaged.
In particular, I'm using Fedora, and my private builds are built based on the
mechanisms from the "fedora-packaging" repo on github. However, the
"fedora-packaging" repo still pulls in the "kicad-libraries" repo from kicad
gt;
> 2018-03-05 23:22 GMT+01:00 Nick Østergaard <oe.n...@gmail.com
> <mailto:oe.n...@gmail.com>>:
>
> It also seem to build correctly on jenkins.
>
> 2018-03-05 23:16 GMT+01:00 Steven A. Falco <stevenfa...@gmail.com
> <mailto:stevenfa...@
On 03/05/2018 07:52 PM, hauptmech wrote:
> The attached patch may fix the build error seen after the RPATH patch.
I was able to build the latest source on my machine with this patch included.
While one run is hardly conclusive, I think this patch has merit.
I'll do some additional runs, and
I just kicked off the Fedora builds about 1 minute ago. Should be ready in an
hour or so. :-)
Steve
On 10/12/18 8:38 AM, Wayne Stambaugh wrote:
> Does anyone need more time to get packages built for the 5.0.1 release?
> I am hoping to release on Sunday if possible. Please let me know
Leaving directory '/builddir/build/BUILD/kicad-r14377-4ad37bc9'
BUILDSTDERR: make[1]: *** [CMakeFiles/Makefile2:3342:
qa/qa_utils/CMakeFiles/qa_utils.dir/all] Error 2
BUILDSTDERR: make[1]: *** Waiting for unfinished jobs
It seems that the makefiles think STATIC is a library.
Steve
>
>
On 11/5/18 9:49 AM, John Beard wrote:
> Gah! Wrong patch! Try this.
That's better! I got a clean build with your new patch. Please commit it, and
thanks!
Steve
> On Mon, Nov 5, 2018 at 2:43 PM Steven A. Falco wrote:
>>
>> On 11/5/18 5:24 AM, John B
b.com/KiCad/kicad-website
>
> Thanks,
>
> Wayne
>
> On 11/8/2018 12:57 PM, Steven A. Falco wrote:
>> The attached patch adds Fedora 29 to the downloads section of the web site.
>>
>> Please review and apply this, or please give me feedback if the patch is
&g
The attached patch adds Fedora 29 to the downloads section of the web site.
Please review and apply this, or please give me feedback if the patch is
incorrect, unlikely though that may be. :-)
Steve
>From 1722bed70e4fc7714bca697778d669ea6e526f19 Mon Sep 17 00:00:00 2001
From: &quo
I'd like to have a discussion about python shebangs. I noticed several rpmlint
errors when building the official Fedora packages. Specifically, rpmlint is
complaining about using "env" as a method for locating the python interpreter.
Here are the errors:
kicad-doc.noarch: E:
The following discussion is from [KiCad/fedora-packaging] Handle ambiguous
Python shebang (#20). I'm cross-posting to kicad-developers since I'm not sure
who sees the fedora-packaging emails. Please don't hate me. :-)
On 11/4/18 6:05 AM, nickoe wrote:
> The patch was merged upstream, I
As a packager, I'd prefer to have both the 5.0.0 and 5.0.1 tags on the same
commit, if it turns out that nothing has changed in the libs.
The reason is that the Fedora spec file only has one version number, yet it
pulls in 7 separate tar balls. It would definitely be awkward to have multiple
to see what happens with the ngspice library. If it looks like
there will be a substantial delay in having the flag removed, I can always
apply my patch and push that as the next official Fedora build.
Steve
On 1/11/19 2:25 PM, Steven A. Falco wrote:
> On 1/11/19 1:51 PM, Steven A. Falco wr
On 1/15/19 9:21 AM, Wayne Stambaugh wrote:
> Hi Steve,
>
> On 1/15/2019 8:51 AM, Steven A. Falco wrote:
>> I'll look at that. The worst burst of backspaces is about 7 characters
>> long, so I could accumulate 14 chars or so before making a decision. In
>> other w
his is as
> one a done patch for you.
>
> Tom or Orson,
>
> Any objections to this patch. I didn't test it but on the surface it
> appears to resolve the issue.
>
> Cheers,
>
> Wayne
>
> On 1/14/2019 10:30 AM, Steven A. Falco wrote:
>> I wanted t
t = t.Mid(0, position) + t.Mid(position + 1);
}
}
m_simConsole->AppendText( aEvent.GetString() + "\n" );
m_simConsole->SetInsertionPointEnd();
}
On 1/14/19 6:21 PM, Wayne Stambaugh wrote:
> On 1/14/19 1:06 PM, Steven A. Falco wrote
valid returns. I would prefer either iterative removing of the \b and
> its preceding char or a wxString::Printf() into a new string to evaluate the
> escape sequences
>
> -Seth
>
> A more general patch would
> Am 2019-01-14 13:06, schrieb Steven A. Falco:
>> The
I had a corrupted repo - I fixed that and the build is now running. I'll let
you know how it goes...
Steve
On 1/15/19 4:07 PM, Steven A. Falco wrote:
> I opened a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1666505
>
> I've made the necessary changes in "fe
On 1/15/19 5:19 PM, Seth Hillbrand wrote:
> Am 2019-01-15 16:42, schrieb Steven A. Falco:
>> A recent commit, "pcbnew: Prevent GITHUB plugin from being
>> registered", seems to have caused my copr build to fail.
>
> Hi Steve-
>
> Sorry about that. Missed a
I
> have not seen any activity from him.
>
> On Tue, 15 Jan 2019 at 20:58, Steven A. Falco <mailto:stevenfa...@gmail.com>> wrote:
>
> On 1/15/19 9:21 AM, Wayne Stambaugh wrote:
> > Hi Steve,
> >
> > On 1/15/2019 8:51 AM, Steven A. Falco wrote:
A recent commit, "pcbnew: Prevent GITHUB plugin from being registered", seems
to have caused my copr build to fail.
Fedora has "BUILD_GITHUB_PLUGIN=ON". I get this error:
[ 18%] Building CXX object
common/CMakeFiles/pcbcommon.dir/__/pcbnew/io_mgr.cpp.o
cd
My build of kicad-5.0.2-1.fc29 has completed in the Fedora buildsystem, and
I've submitted it for testing. Thus, the build should show up in the
updates-testing repo as soon as a release engineer pushes it along - usually
that takes a day or two.
After that, if it receives enough (positive)
re:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-40a9391ac3
Steve
On 12/4/18 2:03 PM, Rene Pöschl wrote:
> How does a package get karma? Can the community perhaps help out in some way?
>
> On 04/12/18 19:57, Steven A. Falco wrote:
>> My build of kicad-5.0.2-1.fc29 ha
I see that the source code was tagged with 5.0.2, but I get a 404 when I try to
download the tar via:
https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz
Is that the correct link? Has the tar been posted yet?
Thanks,
Steve
On 12/3/18 7:49 AM, Wayne Stambaugh
ld servers updated and the installers uploaded to
> the website. As soon as the library devs get the library repos tagged,
> it shouldn't take more than a week to get most of the installers built.
> My goal is to make the release announcement this weekend.
>
> Cheers,
>
> Wayne
>
tagged but I'm guessing the are packaged separately on most if not
> all linux distros.
>
> Cheers,
>
> Wayne
>
> On 12/3/2018 12:05 PM, Steven A. Falco wrote:
>> The link is based on what I was using for 5.0.0, 5.0.1, etc. I'd guess that
>> as soon as yo
The Fedora build has +2 karma - thanks to Seth and Inie! One more +plus1 vote
and we can move from testing to released. Or we'll just wait 6 days and it
will happen without added karma. :-)
Steve
On 12/6/18 6:07 PM, Adam Wolf wrote:
> Thanks!
>
> On Thu, Dec 6, 2018 at 5:03 PM Nick
On 12/9/18 10:47 AM, Seth Hillbrand wrote:
> Am 2018-12-09 10:24, schrieb Steven A. Falco:
>> I had been able to build KiCad successfully for Fedora 29, but
>> something has apparently changed very recently, because I am now
>> getting a build failure.
>>
>&
I had been able to build KiCad successfully for Fedora 29, but something has
apparently changed very recently, because I am now getting a build failure.
Below is part of my build log. The error relates to an include file called
KHR/khrplatform.h:
[ 23%] Building CXX object
On 12/9/18 11:53 AM, Steven A. Falco wrote:
> On 12/9/18 10:47 AM, Seth Hillbrand wrote:
>> Am 2018-12-09 10:24, schrieb Steven A. Falco:
>>> I had been able to build KiCad successfully for Fedora 29, but
>>> something has apparently changed very recently, because I
On 11/26/18 4:57 PM, Steven A. Falco wrote:
> On 11/26/18 3:30 PM, Simon Richter wrote:
>> Hi,
>>
>> On 26.11.18 17:52, Steven A. Falco wrote:
>>
>>> Since I am one of the packagers for KiCad for Fedora, I get "abort" reports
>>> that Fed
Since I am one of the packagers for KiCad for Fedora, I get "abort" reports
that Fedora has collected from users.
I'm forwarding one of the reports to see if there is any interest in this data
by any KiCad developers. Please let me know if it is helpful, or if I should
just disregard these
On 11/26/18 3:30 PM, Simon Richter wrote:
> Hi,
>
> On 26.11.18 17:52, Steven A. Falco wrote:
>
>> Since I am one of the packagers for KiCad for Fedora, I get "abort" reports
>> that Fedora has collected from users.
>
>> I'm forwarding one of
t; lead ngspice developers, who helps KiCad users use the simulator.
>
> Cheers,
> Orson
>
> 1. https://forum.kicad.info
>
> On 1/11/19 5:24 PM, Steven A. Falco wrote:
>> Now that Fedora has the requisite libraries, I'm trying to get ngspice
>> working. I
Now that Fedora has the requisite libraries, I'm trying to get ngspice working.
It compiled fine, but when I try to run the first example from
http://ngspice.sourceforge.net/ngspice-eeschema.html, I get the following:
push: stackp: 0 -> 1
Circuit: KiCad schematic
pop: stackp: 1 -> 0
calling
I tried another ngspice experiment. I ran a simulation, and it worked, albeit
with the data size warning I asked about earlier. So far so good.
However, the ngspice window showed some really strange text, as if the font was
missing many characters. Here is a link to a screenshot:
On 1/11/19 1:51 PM, Steven A. Falco wrote:
> On 1/11/19 1:21 PM, Seth Hillbrand wrote:
>> Am 2019-01-11 12:18, schrieb Steven A. Falco:
>>> I tried another ngspice experiment. I ran a simulation, and it
>>> worked, albeit with the data size warning I asked about e
On 1/11/19 1:21 PM, Seth Hillbrand wrote:
> Am 2019-01-11 12:18, schrieb Steven A. Falco:
>> I tried another ngspice experiment. I ran a simulation, and it
>> worked, albeit with the data size warning I asked about earlier. So
>> far so good.
>
> That warning
; -Jon
>
> On Sun, Mar 31, 2019 at 9:28 AM Steven A. Falco <mailto:stevenfa...@gmail.com>> wrote:
>
> I was alerted to the following bug report:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1694288
>
> The user hit a key - doesn't know which key - and s
I was alerted to the following bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1694288
The user hit a key - doesn't know which key - and somehow triggered a crash in
GetNextItem. I don't know if this bug report is helpful, but it does have a
backtrace, and we know which version of
On 3/14/19 10:26 AM, Wayne Stambaugh wrote:
> How are we doing on the 5.1.0 packaging? I've only heard from
> Jean-Samuel thus far. Are the windows and macos packages ready to go
> yet? I have a few minor tweaks to make to the release announcement and
> it's ready to go. Please let me know so
On 2/7/19 1:38 PM, Vesa Solonen wrote:
> Steven A. Falco kirjoitti 7.2.2019 klo 18.04:
>
>> However, because of the eeschema line-width issues that I mentioned
>> yesterday, I'm not convinced that users will be happy with gtk3.
>>
>> In the attached screenshot, c
gt;
>> Make sure to use the correct wxWidgets_CONFIG_EXECUTABLE, I don't
>> remember what they are called on fedora, but I think there are two
>> wx-config binaries on fedora if you have wxgtk with both gtk2 and gtk3.
>>
>> Nick
>>
>> On Wed, 6 Feb 2019 at 22
On 2/7/19 2:11 PM, Wayne Stambaugh wrote:
> On 2/7/2019 1:38 PM, Vesa Solonen wrote:
>> Steven A. Falco kirjoitti 7.2.2019 klo 18.04:
>>
>>> However, because of the eeschema line-width issues that I mentioned
>>> yesterday, I'm not convinced t
On 2/6/19 2:38 PM, Carsten Schoenert wrote:
> Am 06.02.19 um 20:00 schrieb Wayne Stambaugh:
>> Any idea the number of unique downloads? I'm guessing not many users
>> install from experimental.
>
> Yes, people need to know that they want to use a version from
> experimental, so the base is
I'm doing some testing of my Copr build - here are the build parameters:
Application: kicad
Version: 5.1.0-rc1-unknown-r14933-7789ec4b, debug build
Libraries:
wxWidgets 3.0.4
libcurl/7.61.1 OpenSSL/1.1.1a zlib/1.2.11 brotli/1.0.5 libidn2/2.0.5
libpsl/0.20.2 (+libidn2/2.0.5)
On 2/8/19 2:36 PM, Seth Hillbrand wrote:
> Am 2019-02-08 11:48, schrieb Steven A. Falco:
>> I'm doing some testing of my Copr build - here are the build parameters:
>>
>> Application: kicad
>> Version: 5.1.0-rc1-unknown-r14933-7789ec4b, debug build
>>
Will the libraries, translations, and documentation be tagged for the rc1, rc2,
etc?
I'd like to use tagged material for the package builds, rather than just
picking a random SHA. Currently, only the source is tagged with rc1.
Steve
On 2/16/19 8:21 AM, Wayne Stambaugh wrote:
> Tom,
>
Sorry for the hijack.
Will the libraries, translations, and documentation be tagged for the rc1, rc2,
etc?
I'd like to use tagged material for the package builds, rather than just
picking a random SHA. Currently, only the source is tagged with rc1.
Steve
On 2/11/19 11:39 AM, Seth Hillbrand wrote:
> Am 2019-02-11 11:31, schrieb Steven A. Falco:
>> With KiCad 5.0.2 I am able to hold down ctrl+shift to move text to any
>> location, ignoring the snap-grid.
>>
>> With the r14933-7789ec4b build that I made, that doesn't work
I posted a bug regarding adding a component in eeschema.
Should I notify the list as I find these, or is simply creating the bug
sufficient? I would rate this bug as fairly important, because one winds up
with duplicated lines in the add-components tool.
ets_CONFIG_EXECUTABLE, I don't remember
> what they are called on fedora, but I think there are two wx-config binaries
> on fedora if you have wxgtk with both gtk2 and gtk3.
>
> Nick
>
> On Wed, 6 Feb 2019 at 22:59, Steven A. Falco <mailto:stevenfa...@gmail.com>> wrote:
1 - 100 of 289 matches
Mail list logo