Cool. Great work Mark :)
On Thu, 31 Mar 2022, 04.53 Mark Roszko, wrote:
> Three symbol stores are now available at https://symbols.kicad.org for
> Windows developers/users to troubleshoot crashes.
>
> These stores are automatically updated on nightly builds and stable
> releases.
> The nightly a
You need to use the package target when buildign the doc tar
On Fri, 11 Feb 2022, 16.15 Jon Evans, wrote:
> @seth - I think the docs need to be re-packed in the manner Christoph
> says, IIRC that is a requirement for the Mac packaging.
>
> On Fri, Feb 11, 2022 at 10:09 AM Christoph Moench-Tegede
Hi Franck,
This should be superceeded by:
https://dev-docs.kicad.org/en/file-formats/
Nick
On Wed, 19 Jan 2022 at 19:41, Franck Bourdonnec wrote:
>
>
> About doc, this one seems good but bazaar, no revision, no datestamp ?
>
> Is it maintained ?
>
>
> bazaar.launchpad.net/~stambaughw/kicad/doc
Hi Levente,
Is this the file you are looking for?
https://gitlab.com/kicad/libraries/kicad-library-utils/-/blob/master/.v5_schlib/schlib.py
Nick
On Mon, 17 Jan 2022 at 00:51, Levente wrote:
>
> Hello devs,
>
>
>
> I miss the sch.py from kicad-library-utils for v6, and I thought I write
> it my
Having the unused parameters is no harm, it will only generate a
warning at configure time.
The KICAD_PCM flag already defaults to ON, but I guess it should just
be removed as an option? Are there any reason to keep it as a toggle
for v6+?
I am not aware of anything new flags for features in v7.
The list received it at least ..
On Thu, 4 Nov 2021, 20.26 Steven A. Falco, wrote:
> This is a test email - please ignore.
>
> For some reason, the last email I received from launchpad was on
> 2021-10-08 at the time the "Launchpad bug tracker closure" email went out.
>
> Thus, I missed the emai
What about versioning these folders? Or is that handled by the packager on
a given platform with a build arg?
On Mon, 18 Oct 2021 at 01:32, Seth Hillbrand wrote:
> Hi Folks-
>
> There's a small change brewing to where the default symbol/footprint
> libraries are installed.
>
> Previously, KiCad
Wouldn't be appropriate to add the post as this to the blog on kicad.org as
well?
On Tue, 19 Oct 2021 at 22:30, Seth Hillbrand wrote:
> Hi Folks-
>
> As you know, the original KiCad domain name (kicad-pcb.org) was recently
> sold. This happened without notification to the KiCad Project or membe
Hi Bastian,
You should probably report it as an issue on
https://gitlab.com/kicad/code/kicad/-/issues
There you can also add a screenshot to help explain what you are
seeing. Remember to add the version information.
Nick
On Fri, 8 Oct 2021 at 22:08, Bastian wrote:
>
> Hi
>
> Placing a new IC c
This is the same we saw on the windows build earlier. FWIW.
On Tue, 14 Sept 2021 at 17:18, Steven A. Falco wrote:
>
> Thanks, Wayne - that is a clear improvement.
>
> Steve
>
> On 9/14/21 11:13, Wayne Stambaugh wrote:
> > On 9/14/21 10:05 AM, Steven A. Falco wrote:
> >> Thanks, Jeff. It
Maybe you should post that to the github issue?
On Wed, 4 Aug 2021 at 17:41, Steven A. Falco wrote:
>
> This has now been corrected in Fedora rawhide as described in [1], which let
> me close the associated KiCAD FTBFS in [2].
>
> I don't know if this issue is unique to Fedora or if others will
What commit are you on?
On Fri, 16 Jul 2021 at 10:39, Alex Vidrasan wrote:
>
> Hi,
>
> I tried to submit a bug report the usual way but gitlab killed my account and
> won't let me register a new one for some reason.
>
> The issue is I can't compile the latest kicad from a freshly cloned
> repos
@Amir, Currently, any help at getting this list sorted out is progress.
https://gitlab.com/kicad/code/kicad/-/issues?scope=all&utf8=%E2%9C%93&state=opened&milestone_title=6.0.0-rc1
But that list contains both big and small items, but items that do require
some real work.
On Tue, 29 Jun 2021 at
;-lwx_mswu_propgrid-3.0;-lwx_baseu_xml-3.0;-lwx_mswu_stc-3.0)
>
> Because it found 3.0.5 (even though 3.1.5 was installed) so I ran
>
> pacman -R mingw-w64-x86_64-wxWidgets
>
> and it went through.
>
>
> Thanks everybody!
>
>
>
> On 2021-06-28 11:00 a.m., Nick Ø
Brian, think that is because you started the msys shell instead of one of
the mingw64 one.
On Mon, 28 Jun 2021 at 16:46, jp charras wrote:
>
> Le 28/06/2021 à 16:14, Brian Piccioni a écrit :
> > JP
> >
> > Thanks for the quick reply
> >
> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/releas
You don't need to specify the type, but cmake will accept it as well and
that is how it is written by cmake in the CMakeCache.txt.
On Wed, 16 Jun 2021 at 20:51, Kevin Cozens wrote:
> On 2021-06-15 6:32 a.m., Marco Ciampa wrote:
> > On Tue, Jun 15, 2021 at 12:22:42AM +0300, Eeli Kaikkonen wrote:
;
> https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/2215757/
>
> Steve
>
> On 6/3/21 4:32 PM, Nick Østergaard wrote:
> > Ah,ok, I misread the pipeline logs..
> >
> > Error: Login invalid/expired. Please visit
> https://copr.fedorainfracloud.org/
Hopefully it should be running ok in
https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/jobs/1316881996
On Thu, 3 Jun 2021 at 22:32, Nick Østergaard wrote:
> Ah,ok, I misread the pipeline logs..
>
> Error: Login invalid/expired. Please visit
> https://copr.fedorainfracloud.or
Steve
>
> On 6/3/21 3:26 PM, Nick Østergaard wrote:
> > @Steven A. Falco <mailto:stevenfa...@gmail.com>
> >
> > Did you have a look at building the docs for fedora with the other
> package?
> >
> > It appears to still BuildRequires: asciidoc when I look
@Steven A. Falco
Did you have a look at building the docs for fedora with the other package?
It appears to still BuildRequires: asciidoc when I look in the spec file in
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/
On Sun, 30 May 2021 at 22:51, Jon Evans wrote:
> If you
Mm, normally you should use the mingw env in msys2, from your prompt it
appears you use the msys env.
Normally I would expect all psths it uses for binsries to be unic like,
that is /c instead of c:/
ons. 19. maj 2021 02.55 skrev Clifford Neal Simon :
> Hi devs,
>
> I'm doing my first build from
It did not work last time I tried it.
On Tue, 18 May 2021 at 14:43, Wayne Stambaugh wrote:
> I just looked and the 5.1.10 windows build is using OCE. I thought we
> switched over to OCC for msys2 builds but apparently not. I have
> switched to OCC on my windows msys2 builds. I think we should
IMHO we should be fine with defaulting to OCC by now. Previously there were
issues with the occ build in msys2 where kicad would not link to it
properly, but we have since started to support msvc instead and we are
using occ for those builds for master.
Also, I think we are using occ on macos now,
> Cu
> David
>
> Am 28. Apr. 2021, 17:47 +0200 schrieb Nick Østergaard :
>
> Mm, you didn't state what OS you have on that pi, but I assume something
> debian based, you probably need a "-dev" og some of the libcurl stuff.
> Something like libcurl4-gnutls-dev
&g
Ok, thank you. I will follow-up with archlinux packager for ngspice.
On Wed, 28 Apr 2021 at 10:02, Holger Vogt wrote:
> config.h for ngspice should not be distributed, because it is a local,
> OS dependent autogenerated file, and might interfere with other packages.
>
> So I did remove it in ngs
Hi
What is the solution to this issue. I just hit issues with ngspice-34 in
archlinux. [1]
There is a /usr/include/config.h
Should this be put in /usr/include/ngspice/config.h?
I lost track of this discussion, so I am not really sure what happened and
why. Just slightly surprised that it appear
I would be fine with permanently enabling the ngspice integration. It has
historically not been that complicated to support, I mean build wise, and I
don't think it makes a lot of difference for rebuilds, which is where it
could be nice to disable some things, like scripting sometimes.
Speaking fr
d be able to install the latest version again and have it
> work.
>
> -Jon
>
> On Sat, Mar 13, 2021 at 10:26 AM Nick Østergaard wrote:
>>
>> Please try to see if you can start it directly from the kicad.exe in the
>> install location insread of the shortcuts.
>>
Please try to see if you can start it directly from the kicad.exe in the
install location insread of the shortcuts.
lør. 13. mar. 2021 16.22 skrev David :
> I'm reporting this here as I am unable to provide any version information
> as nothing starts up. This is reported as an incomplete report b
Maybe try the kicad-mac-buidler just to verify your environment works?
It should use the same brew stuff as you manually use.
https://gitlab.com/kicad/packaging/kicad-mac-builder/
On Fri, 5 Mar 2021 at 17:44, Jonatan Liljedahl wrote:
>
> I tried "make install" in case something wasn't in the rig
pp.o)
> opencascade::handle::~handle() in
> libkicad2step_lib.a(oce_utils.cpp.o)
> PCBMODEL::~PCBMODEL() in libkicad2step_lib.a(oce_utils.cpp.o)
> PCBMODEL::AddPadHole(KICADPAD const*) in
> libkicad2step_lib.a(oce_utils.cpp.o)
> std::__1::vector
>
> ::push_ba
You need to make sure you have a clean buid dir and try yo explicitly
disable oce and enable occt on your cmake configure line.
fre. 5. mar. 2021 11.48 skrev Jonatan Liljedahl :
> Ok, I'm now trying to build against OCE instead, as I'm sure that used
> to work before.
> I managed to have CMake fi
debug build on my environment
> either. Thanks.
>
> Regards,
>
> Thomas
>
> On 2/20/21 3:04 AM, Nick Østergaard wrote:
> > It works for me now, at least,
> >
> > https://jenkins.simonrichter.eu/job/windows-kicad-msys2-5.1/237/console
> >
> > On Wed, 1
It works for me now, at least,
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-5.1/237/console
On Wed, 17 Feb 2021 at 14:12, Jon Evans wrote:
>
> Hi Marco,
>
> I am not part of kicad-us...@groups.io but I am part of this list and I can
> fix the issue you mention, sorry about that...
>
Hi Holger,
Whats up with this big diff from 33 to 34?
https://github.com/msys2/MINGW-packages/pull/7867#issuecomment-770786574
Nick
On Sat, 30 Jan 2021 at 17:57, Wayne Stambaugh wrote:
>
> Holger,
>
> Thanks for the fixes. Hopefully our packagers can get this into as many
> of our nightly bui
Mmm, I guess they are also part of the install target in cmake and no real
packaging changes are needed a such, right?
On Wed, 20 Jan 2021 at 18:34, Seth Hillbrand wrote:
> This is a heads up for our Linux packagers that the launcher locations
> have changed in the master branch.
>
> You will no
FYI, there are still generated files in the source which are also checked
in to the source tree:
After a make clean:
deleted:../eeschema/dialogs/dialog_bom_help_md.h
deleted:../pcb_calculator/attenuators/bridget_tee_formula.h
deleted:../pcb_calculator/attenuators/pi_formula.h
deleted:
The list is not dead.
On Thu, 31 Dec 2020 at 05:53, Reece R. Pollack wrote:
>
> I finally have some time to work on adding origin transforms to the
> footprint editor. I have a couple of questions:
>
> 1) Is the Developers mailing list still working? I haven't gotten
> anything since Dec 26th.
>
ions to flow in since that _rc1.
On Wed, 23 Dec 2020 at 13:34, Christoph Moench-Tegeder
wrote:
>
> ## Nick Østergaard (oe.n...@gmail.com):
>
> > By having the release announcement, it is easier to use that as a
> > reference when users are flagging packages in various distro
those
don't are not released via a native package manager.
ons. 23. dec. 2020 11.20 skrev Carsten Schoenert :
> Hell Nick,
>
> Am 23.12.20 um 10:07 schrieb Nick Østergaard:
> > Hi Carsten
> >
> > This is a balancing act. Quite some time ago we decided that we sho
Hi
Yes, of course. I was not aware that there were any string changes,
but I didn't really check it either.
Nick
On Wed, 23 Dec 2020 at 10:34, Константин Барановский
wrote:
>
> Please next time provide the ability for the translators to update the
> translations before tagging.
>
> вт, 22 дек.
e don't expect other distros to have builds ready by the
release announcement.
Nick
On Wed, 23 Dec 2020 at 09:27, Carsten Schoenert wrote:
>
> Hi,
>
> Am 22.12.20 um 23:01 schrieb Nick Østergaard:
> > I don't think we need that long. Everything seems to be tagged. I ha
I don't think we need that long. Everything seems to be tagged. I have
triggered the windows build and it should just be a simple pkgver bump
for macos and ubuntu ppa as well.
On Tue, 22 Dec 2020 at 21:14, Wayne Stambaugh wrote:
>
> 5.1.9 has been tagged for release. Please tag the library, doc,
ws. But if development of the
> KiCad Code is easier on Linux I could move to Linux for this target.
>
>
> best wishes
>
>
> Stefan
>
>
> On 12/18/20 4:28 PM, Nick Østergaard wrote:
>
> What is your goal?
>
> fre. 18. dec. 2020 12.00 skrev Stefan Aurache
What is your goal?
fre. 18. dec. 2020 12.00 skrev Stefan Auracher :
> I started KiCad from within msys like
> /d/proj/msys_mingw/KiCad_git_repo/kicad/build/release/kicad/kicad.exe
>
> And within this build tree in
> D:\proj\msys_mingw\KiCad_git_repo\kicad\build\release
>
> I don't have the direct
more security
> updates).
> It would be crazy for MSYS2 not to eventually drop the packages themselves
> as well.
>
> On Tue, Nov 10, 2020 at 6:13 PM Nick Østergaard wrote:
>
>> On further review of the msys2 news page that states:
>>
>> /quote
>> 2
On further review of the msys2 news page that states:
/quote
2020-05-17 - 32-bit MSYS2 no longer actively supported
32-bit mingw-w64 packages are still supported, this is about the POSIX
emulation layer, i.e. the runtime, Bash, MinTTY...
After this date, we don't plan on building updated msys-i68
For archlinux that is...
On Mon, 9 Nov 2020 at 20:08, Nick Østergaard wrote:
> Mm, I am not sure exactly why, but I have had zlib as a build dependency
> for a looong time.
>
> On Tue, 18 Aug 2020 at 00:56, Seth Hillbrand wrote:
>
>> As promised, the MR is:
>>
>&
Mm, I am not sure exactly why, but I have had zlib as a build dependency
for a looong time.
On Tue, 18 Aug 2020 at 00:56, Seth Hillbrand wrote:
> As promised, the MR is:
>
> https://gitlab.com/kicad/code/kicad/-/merge_requests/359
>
> You can click the "Check out branch" to get the branch to tes
d to be but with the fragmented x11/wayland
>> mess, they removed the api call support to determine top level window.
>> >
>> > And removing the focus calls instead are going to lead a rabbit hole of
>> things not working like hotkeys.
>> >
>> > On Thu, N
Oh, I did verify that, sorry I wasn't clear. It definitely works.
>>
>> On Thu, Oct 1, 2020, 02:00 Nick Østergaard wrote:
>>
>>> I was implicitly hoping you could explicitly verify for me that using
>>> the OSDN url would support range requests. :)
>>&
. See
> https://www.mklab.rhul.ac.uk/~tom/kicad/SlackBuild/. The tom_build.sh
> script calls the main build script kicad-git.SlackBuild.
>
> Thanks
> Tom
>
> On Thu, 5 Nov 2020, Nick Østergaard wrote:
>
> > Are you using a build script? If so please link it.
> >
Are you using a build script? If so please link it.
Also check if you partially installed in multiple locations, sucha as where
ldconfig looks and echo LD_LIBRARY_PATH from your runtime env.
Nicl
tor. 5. nov. 2020 16.26 skrev Tom Crane :
> I have been using recent builds for the past few weeks.
Hi Alexander
Maybe you want to add it to the "made with kicad" page on the website?
https://kicad-pcb.org/made-with-kicad/
Nick
On Thu, 10 Sep 2020 at 19:52, wrote:
> Oh, that's right, I'll do it. Thanks)
>
> 10 сентября 2020 г. 18:42:23 GMT+03:00, "Roberto Fernández Bautista" <
> roberto.fer.
Hi Rachel
I wonder why you wouldn't just propose the changes to the maintainer of
kicad-git in AUR.
I didn't review your scripts, but that is where I woukd start.
fre. 23. okt. 2020 12.32 skrev :
> Hi folks,
>
> I recently got fed up enough of not having a parallel installable
> nightly for Ar
-lite.exe
> seems to work
>
>
> I have not tested all versions between
>
>
> On 2020-10-12 4:20 p.m., Nick Østergaard wrote:
>
> What system are you installing it on?
>
> Does any older nightly builds work?
>
> On Mon, 12 Oct 2020 at 18:42, Brian Piccioni
>
What system are you installing it on?
Does any older nightly builds work?
On Mon, 12 Oct 2020 at 18:42, Brian Piccioni
wrote:
> Hello
>
> I downloaded kicad-r18079.88102bca46-x86_64.exe and
> kicad-r18079.88102bca46-x86_64-lite.exe from
> https://kicad-downloads.s3.cern.ch/index.html?prefix=win
You may be interested in the DRC updates for v6, see
https://forum.kicad.info/t/need-some-guinea-pigs-for-a-rule-based-drc-prototype/22955
man. 12. okt. 2020 07.49 skrev BERTRAND Joël :
> Hello,
>
> Sometimes, on very compact boards, I need isolated vias (from
> planes)
> for exam
Build with the same options as used on arch.
man. 12. okt. 2020 04.20 skrev Tom Crane :
> Thanks for the clarification -- and to all who follow-ed up. That was the
> information I needed. Now using Phoenix 4.1.1a1/gtk3 (wxWidgets 3.1.5)
> from git to build both wxPython4 and wxWidgets (wxGTK3+
You are best off configuringnyour build with gtk3 in a clean build dir.
tor. 8. okt. 2020 18.24 skrev Ian McInerney :
> The build has failed because it appears that your version of
> wxPython/Phoenix is using wxWidgets 3.1.5 and you are trying to use
> wxWidgets 3.1.4 in the main KiCad build. Tho
s one. As it standards, 10.12 is past EOL now.
> 10.13 EOL is in 2 months. Supporting outdated (and as an extension
> insecure) OSes just encourages users to make the bad decision to keep using
> them.
> >
> > On Wed, Sep 30, 2020 at 11:26 AM Nick Østergaard
> wrote:
> &g
ls in the torrent as well, just pass
> --urlList flag multiple times.
>
> On Wed, Sep 30, 2020 at 11:28 PM Nick Østergaard
> wrote:
>
>> Does it also work with the OSDN mirror?
>>
>> tor. 1. okt. 2020 02.42 skrev Andrew Lutsenko :
>>
>>> Hi all,
>&
Does it also work with the OSDN mirror?
tor. 1. okt. 2020 02.42 skrev Andrew Lutsenko :
> Hi all,
>
> I recall we had this discussion before about providing torrent files for
> release downloads to reduce the slowdown related to rush traffic. it didn't
> go far mainly because of resources needed
posting the announcement to the 30th
> >> > > > which
> >> > > > was the original plan.
> >> > > >
> >> > > > Cheers,
> >> > > >
> >> > > > Wayne
> >> > > >
> >> > > >
A solution to this could be go genrate idf models more interactively as
suggested Jon. We already have idfcyl and idfrect as references. I assume
there is no reason to use IDF over STEP as the physical representation.
On Tue, 29 Sep 2020 at 21:01, Mário Luzeiro wrote:
> that would work for me to
Everything has been tagged, the windows build is ready.
I think the macos build may be a bit delayed, but I think we can undraft
the release announcement now anyways.
On Sat, 26 Sep 2020 at 03:33, Christian Schlüter wrote:
> Libraries are
>
> https://github.com/KiCad/kicad-footprints/releases/t
Ni, they are only cached via the archive artifacts of jenkins, which I
can't reach right now.
fre. 25. sep. 2020 22.39 skrev Wayne Stambaugh :
> Is there a repo with with the build configuration so I can see what
> msys2/mingw64 packages are being used in our builds?
>
> On 9/25
I cant reach the build server right now, so I don't know the status, but it
is not autoupdated. Mainly updated once in a while after a release has been
made with "known good env".
fre. 25. sep. 2020 22.02 skrev Wayne Stambaugh :
> I take it we are not getting any nightly build errors for msys2/mi
Hi
Slightly related to this discussion and for inspiration:
https://twitter.com/azonenberg/status/1282188633118699520
Nick
On Wed, 23 Sep 2020 at 09:43, Alexander Shuklin wrote:
> Hi Kliment,
> I think if these things you explained will be implemented, it will make
> high speed design very mu
I think JP fixed this in
https://gitlab.com/kicad/code/kicad/-/commit/ff0a728753adf701a9d723b9f2b6484114e5dff1
On Mon, 14 Sep 2020 at 08:11, Marco Ciampa wrote:
> See the message:
>
> pcbnew/drc/drc_engine.cpp:492: warning: Empty msgid. It is reserved by
> GNU gettext:
>
It is the same for the windows nighlties.
On Tue, 8 Sep 2020 at 15:08, Eeli Kaikkonen wrote:
>
> Compilation fails today:
>
> [4/14] Building CXX object
> qa/drc_proto/CMakeFiles/drc_proto.dir/drc_test_provider_annulus.cpp.o
> FAILED: qa/drc_proto/CMakeFiles/drc_proto.dir/drc_test_provider_annul
Why don't you just install it?
On Wed, 19 Aug 2020 at 13:04, Jonatan Liljedahl wrote:
>
> I see! But isn't gerbview always run standalone? Running pcbnew and
> eeschema from the main kicad project manager works fine from the build
> directory, as long as you don't open a pcb or schematic which ar
Hi Rene
Thank you for the heads up. You have contributed a lot, I am not
really in the loop with all the library maintenance effort, but the
libraries have certainly been kicked high up on the quality and
coverage lists while you have been around.
I don't even dare to mention other honorable libr
Please submit it directly on gitlab as a merge request.
https://gitlab.com/kicad/code/kicad
fre. 21. aug. 2020 14.17 skrev Augusto Fraga Giachero :
> Hi,
>
> I've experienced crashes in pcbnew when creating a cooper fill zone when
> no board edges has been defined. Tuns out that BuildBoardPolygo
I assume rawhide maintainers will get this resolved when the dust settles.
At least the numbered fedoracore builds are building just fine on copr.
ons. 19. aug. 2020 23.25 skrev Steven A. Falco :
> I've been chasing a build failure on the nightlies for Fedora Rawhide
> whereby wxGTK3-devel is cla
Isn't there a new cmakevariable to enable the binaries to be run from the
build dir?
ons. 19. aug. 2020 11.38 skrev Jeff Young :
> It’s a “thing” on OSX. I run the attached script which fixes things up.
> Sadly it has to be run after each build.
>
> I know Jon has the same issue, but I haven’t h
Probably CEST, and 24h clock...
man. 17. aug. 2020 16.33 skrev Kevin Cozens :
> On 2020-08-17 3:58 a.m., Maciej Suminski wrote:
> > I have received a message saying that a virtual machine hosting the
> > downloads storage might be down on 7th September between 9:00 and 12:00.
>
> Is that AM or PM
I think we should just get the updated solution merged that Ian made.
It does not use system lemon and there for not require it as an
external dependency, but addes the source file directly and fixes the
issue with the dirty flag. If someone want to make it be able to
switch to a system lemon if fo
I think it has always been like this. But there is only one user grid
selection, so I am not sure it is a real issue.
On Mon, 3 Aug 2020 at 17:02, Brian Piccioni wrote:
>
> Hello
>
> While working on geographic annotation I note that it is possible to set
> different x and y for the user grid but
Not to throw a finger at anyone, but it has been quasi-optional for a while.
https://gitlab.com/kicad/code/kicad/-/blob/a146cd9e2e22c2b7100cb3c635f1e7733e346daf/common/CMakeLists.txt#L440-445
Although that just means that you won't see anything dirty if you
don't have lemon available on your syst
une version.
>>
>> After failing to build yesterday's master I deleted my build directory,
>> pulled master, same problem. I then updated msys in order to make sure it
>> wasn't a tool issue. Same problem. I deleted the build directory and same
>> result.
>
That looks quite strange. Did you try a clean build directort? Maybe
there is some caching that is broken after a toolchain update? Pure
speculation.
On Tue, 21 Jul 2020 at 16:47, Brian Piccioni
wrote:
>
> It is a non-release tag, but as a developer I sort of need it to compile ...
>
> On 2020-
rcdir}" \
-B "%{__cmake_builddir}" \
__cmake_builddir
%{!?__cmake_in_source_build:%{_vpath_builddir}}%{?__cmake_in_source_build:.}
__cmake_in_source_build1
Looks like __cmake_builddir is defined as "." so the build will happen
in source?
On Mon, 20 Jul 2020 at 23:45
I am not sure I misunderstand the terminology here, but "cmake -S . -B
foo -Dnickersej" looks "in tree" to me.
On Mon, 20 Jul 2020 at 23:37, Seth Hillbrand wrote:
>
> Hi Steve-
>
> This looks like a build setup issue, not in our CMake code. We can
> build out of tree (in fact, we really prefer i
What does this mean if I want to test this locally?
Should I do the following or are there other options enforced in cmake?
git clone ...kicad...
mkdir build_outside_of_kicad
cd build_outside_of_kicad
cmake ...kicad...
On Mon, 20 Jul 2020 at 23:28, Steven A. Falco wrote:
>
> Fedora recently mad
for 32 bit builts for both debug and release.
Nick Østergaard
On Wed, 8 Jul 2020 at 02:08, Wayne Stambaugh wrote:
>
> I wish I could say I was surprised.
>
> On 7/7/20 4:34 PM, Mark Roszko wrote:
> > vcpkg has a python3 build .. in fact, people actually complain vcpkg
> &
Are you talking about the python scripting API, or what is your intention?
tor. 9. jul. 2020 14.20 skrev Conrad Wood :
> Hi,
>
> I have a keen interest on APIs for Kicad6. I wonder if there are any
> documents describing the intented architecture and APIs of Kicad6 yet?
> If so could you give m
one)
>
> -Jon
>
> On Tue, Jul 7, 2020 at 7:31 AM Mark Roszko wrote:
> >
> > Nope, I'm building straight out of vcpkg now.
> > Jon Evans posted the patches to kicad's findwxwidgets back in November fyi.
> >
> > On Tue, Jul 7, 2020 at 5:39 AM Nick
s up.
> Why not make it standard baseline as part of kicad instead of allowing
> versions to be mixed?
>
>
> On Mon, Jul 6, 2020 at 3:04 PM Nick Østergaard wrote:
>>
>> Just a FYI, we have not really solved wxpython phoenix for macos yet,
>> though some progress were made
Just a FYI, we have not really solved wxpython phoenix for macos yet,
though some progress were made recently.
For MSVC there are a number of issues yet to be addressed, this is
with the intention of using vcpkg.
1. Fix cmake scripts for wxwidgets
2. Add opencascade to vcpkg
3. Add swig to vcpk
I like the sound of this idea, it could definitely help the workflow
for a lot of people.
What may be related to this is some properly "plugin" manager such
that it is easier to bundle some script and have some script installed
external, similar to the freecad addon manager.
I don't remember if a
Last time I looked, there was rescue feature in the file menu of pcbnew, I
think. I never used it, I don't really know what it does, but I guess it
just reads the bak file.
tir. 30. jun. 2020 09.32 skrev jp charras :
> Le 30/06/2020 à 00:13, hauptmech a écrit :
> >
> > While I agree that it is no
ith no milestone and the
> wishlist label (it is far easier than Launchpad was).
>
> -Ian
>
> On Fri, Jun 26, 2020 at 10:09 AM Eeli Kaikkonen
> wrote:
>
>>
>>
>> On Fri, Jun 26, 2020 at 8:46 AM Nick Østergaard
>> wrote:
>>
>>> What about f
What about feature requests / wishes from users that are very unlikely to
realise quickly? Should they still be assigned the new milestone?
I just worry they may clutter the overview too much, but I guess when we
will see how it goes. :) My concern may not be a real problem afterall.
Nick
fre.
Thank you.
søn. 14. jun. 2020 14.25 skrev Holger Vogt :
> Uups,
>
> Nick, thanks for the hint.
>
> ngspice-doc-32.tar.gz is uploaded now.
>
> Holger
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.l
Hello Holger
Ok, I sorta tried to update the package a couple of times and was
wondering why the download did not work on a simple pkg bump.
This is because the doc tar is missing. Could you please add that, or
is it not intended to be included anymore?
https://git.archlinux.org/svntogit/communi
Erhm, ooh yeah, I sorta nuked the jenkins instance that performed the
mirroring... so I will need to fix that one of these days..
On Thu, 4 Jun 2020 at 14:59, wrote:
>
> Hello Jeff,
>
> I was using github instead of gitlab, this lags gitlab by a day it seems.
> The problem fixed with ae852e17f987
It is fixed now.
On Tue, 2 Jun 2020 at 12:16, Nick Østergaard wrote:
>
> Well, the jenkins job that prepares the copr package fails to clone the 3d
> models for some reason, maybe the repo grew massively in size recently.
>
> tir. 2. jun. 2020 04.01 skrev Oleg Endo :
>>
Well, the jenkins job that prepares the copr package fails to clone the 3d
models for some reason, maybe the repo grew massively in size recently.
tir. 2. jun. 2020 04.01 skrev Oleg Endo :
> Hi all,
>
> The Fedora nightly builds are already 4 days behind.
> Did something get stuck there?
>
> Chee
Plain speculation, but maybe you did run the cmake command initially
without libglm-dev being installed, then installed it and re-reun the
config? If that is the erase, you should probably delta your build
(containing the CMakeCache.txt) and try again.
On Mon, 1 Jun 2020 at 18:41, Brian Henning
1 - 100 of 1904 matches
Mail list logo
