But the free Azure service has a limitation of 10GB space for a builder, so
it os not really fesible to build everything properly.
I managed to make a docker image with the MSYS2 build environment, but ran
out of space to make the installer.
tor. 10. okt. 2019 06.41 skrev Mark Roszko :
> More
On Wed, 9 Oct 2019 at 18:36, Wayne Stambaugh wrote:
>
> The lead development team has been discussing migrating the KiCad
> project to GitLab[1]. Given the issues with Launchpad, I think this is
> a good move. I've applied for an open source GitLab license. Assuming
> we get accepted, I would
It is quite some time since I tried to run anything of kicad in the
build dir. Does it even work for other pats of kicad?
I switched my workflow to make install and run it from there.
On Thu, 3 Oct 2019 at 19:29, Ian McInerney wrote:
>
> It appears that the DSO searching code couldn't find the
Recently I think people have been using google docs for colloborative
design document style things.
lør. 28. sep. 2019 14.00 skrev Simon Richter :
> Hi,
>
> not sure if I've asked this already: is there some place where I could
> post design documents for review and archival?
>
> Launchpad has
I think it is recent enough, but I have not heard about anyone needing the
Xorg fixes as they are related to the legacy canvas. Not sure about the ATI
one.
Mayne the section "Legacy Canvas and wxGTK" can be shortened as we have GAL
available everywhere by now.
We can probably remove the stuff
Does the sha listed in the version info from the runtime app not match?
On Thu, 5 Sep 2019 at 12:49, Jonatan Liljedahl wrote:
>
> Oh, I see. So then how can I check if a commit is included or not in a
> specific nightly 5.1 download?
>
> Cheers
>
> On Thu, Sep 5, 2019 at 10:47 AM Ian McInerney
Cool, then we can have nightly tonight afterall :)
On Wed, 4 Sep 2019 at 23:34, Seth Hillbrand wrote:
>
> Whoops. Thanks JP. Fix incoming.
>
> -S
> On 2019-09-04 12:35, jp charras wrote:
> > common.h does not compile with msys2/gcc 9.1.0
> >
> > Here is the error message:
> >
> > In file
I see the same error in the builder that builds for the official builds.
On Wed, 4 Sep 2019 at 19:20, Ian McInerney wrote:
>
> wxASSERT shouldn't be used inside constexpr functions because some of their
> code paths for it implement trap functions that use inline assembly. This is
> not
Att. Wayne and Adam
According to Jonatans testing in
https://bugs.launchpad.net/kicad/+bug/1841752/comments/9
It looks like ngspice-30 do work for him on the latest nightlies...
Next step, checking if the 5.1 branch testing builds are ok with ngspice-30.
If that works it may be because of some
What was the command that could be added the the schematic to make
ngspice print the version info about itself in the output text shown
in the bottom of the simulator window?
On Fri, 30 Aug 2019 at 12:45, Jonatan Liljedahl wrote:
>
> Thanks. I've updated with a comment on my launchpad report:
>
On a side note: ppc64le was also enabled recently on fedora for the copr
builds and possibly also their official packages of kicad.
tor. 29. aug. 2019 14.22 skrev Gianluca Renzi :
> Ok, thanks!
>
> On Thu, Aug 29, 2019 at 1:40 PM Jean-Samuel Reynaud
> wrote:
>
>> Hi,
>>
>> Best way it step 0
The windows build box for the stable and nightly builds use boost 1.68.
On Wed, 28 Aug 2019 at 21:18, Blair Bonnett wrote:
>
>
> On Wed, 28 Aug 2019 at 21:04, Ian McInerney wrote:
> >
> > Going up to 1.67 won't be possible, since 18.04 is estimated to be
> > supported by KiCad until 2023
> >
I think it sounds good.
Especially the crash on deleting locked footprint bug, which has been
reported by "many" users is a good one to get rid of.
Nick
On Tue, 27 Aug 2019 at 21:57, Seth Hillbrand wrote:
>
> Hi All-
>
> I know 5.1.4 is still in its infancy but I am hoping that we can plan
>
In his second email that is.
man. 19. aug. 2019 15.19 skrev Nick Østergaard :
> I can see the attachment in my email client (gmail android app).
>
> man. 19. aug. 2019 15.03 skrev Wayne Stambaugh :
>
>> Sylwester,
>>
>> Either your patch was removed by the laun
I can see the attachment in my email client (gmail android app).
man. 19. aug. 2019 15.03 skrev Wayne Stambaugh :
> Sylwester,
>
> Either your patch was removed by the launchpad moderation system or you
> forgot to attach it.
>
> Cheers,
>
> Wayne
>
> On 8/18/19 4:11 PM, Sylwester Kocjan wrote:
>
> On Fri, Aug 9, 2019 at 3:02 PM Nick Østergaard wrote:
>
>> Please sanity test the windows build and make pr for the website, I won't
>> make commits until sunday. I am travelling.
>>
>> fre. 9. aug. 2019 23.50 skrev Adam Wolf :
>>
>
;> Cheers,
>>
>> Wayne
>>
>> On 8/9/19 3:50 PM, Stefan Brüns wrote:
>> > On Freitag, 9. August 2019 16:45:37 CEST Nick Østergaard wrote:
>> >> kicad-doc 5.1.4 has been tagged
>> >
>> > Hi,
>> >
>> > the packages for open
kicad-doc 5.1.4 has been tagged
Windows builds should be up in an hour or two.
On Wed, 7 Aug 2019 at 18:23, Nick Østergaard wrote:
>
> Yes. There is an issue on the 5.1.3 of kicad-doc that and we need to include
> the fix for that in 5.1.4 and test it.
>
> ons. 7. aug. 2019 17
Yes. There is an issue on the 5.1.3 of kicad-doc that and we need to
include the fix for that in 5.1.4 and test it.
ons. 7. aug. 2019 17.44 skrev Wayne Stambaugh :
>
>
> On 8/7/19 9:33 AM, Steven A. Falco wrote:
> > On 8/5/19 9:35 AM, Steven A. Falco wrote:
> >> On 8/4/19 6:02 PM, Rene Pöschl
Maybe I am off here, butnis there any reason why you can just enable the
MAINTAIN_PNGS option to make it convert the svg to cpp?
tir. 6. aug. 2019 06.01 skrev Johannes Sprigode :
> If I may chip in.
>
> The new symbols (16x16) I created for the horizontal text are done in
> inkscape and exported
Ok, thanks. Just a note, there are two packages for msys2
mingw-packages that provided.
I see you based your pkgbuild on the 3.0 one...
On Thu, 1 Aug 2019 at 17:01, Tomasz Wlostowski
wrote:
>
> On 30/07/2019 20:03, Nick Østergaard wrote:
> > I get the same error. :(
> >
>
I get the same error. :(
On Tue, 30 Jul 2019 at 16:32, Tomasz Wlostowski
wrote:
>
> On 30/07/2019 15:33, Nick Østergaard wrote:
> > It was built like this:
> > https://github.com/msys2/MINGW-packages/blob/c6dfad711f4d956a02e93026a0eb9a74ad6bfd65/mingw-w64-wxWidgets3.1/PK
It was built like this:
https://github.com/msys2/MINGW-packages/blob/c6dfad711f4d956a02e93026a0eb9a74ad6bfd65/mingw-w64-wxWidgets3.1/PKGBUILD
On Tue, 30 Jul 2019 at 14:59, Tomasz Wlostowski
wrote:
>
> On 30/07/2019 14:54, Nick Østergaard wrote:
> > Exacept when I try to build it agai
with
the menu entry to test the crash reporter.
I still need to test it on windows.
On Tue, 16 Jul 2019 at 13:01, Nick Østergaard wrote:
>
> It looks like some of the errors are related to the lexer stuff. Can
> you try to rebase your branch to latest master?
>
> On Tue, 16 Jul 2019
The builds are now up and running again
fre. 26. jul. 2019 13.10 skrev Nick Østergaard :
> It looks like there are some issues with installing wx 3.1, although it
> should still use 3.0.
>
> fre. 26. jul. 2019 08.04 skrev Holger Vogt :
>
>> There are no upgrades of the build
It looks like there are some issues with installing wx 3.1, although it
should still use 3.0.
fre. 26. jul. 2019 08.04 skrev Holger Vogt :
> There are no upgrades of the builds at
> https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/testing/5.1/
> since July 14.
>
> Could please
Just to keep to clear, I am on vacation until the week is over, and I would
like check prpgress and see if there are some details missing before
tagging doc and i18n.
ons. 24. jul. 2019 11.45 skrev Jean-Samuel Reynaud :
> PPA is in progress:
>
> kicad him self is ready (binary package)
>
>
I am on vacation, but I expect to just tag master of kicad-doc and 5.1 of
kicad-i18n vithout checking much.
man. 22. jul. 2019 20.31 skrev Wayne Stambaugh :
> Is there anything left preventing me from tagging the 5.1 branch for the
> 5.1.3 release? If I don't hear anything, I'm going to tag the
It looks like some of the errors are related to the lexer stuff. Can
you try to rebase your branch to latest master?
On Tue, 16 Jul 2019 at 13:00, Nick Østergaard wrote:
>
> @Tomasz Wlostowski I am trying to build against wx3.1, but I get
> build errors, please review the build log:
@Tomasz Wlostowski I am trying to build against wx3.1, but I get
build errors, please review the build log:
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-patch/465/console
On Tue, 16 Jul 2019 at 12:37, Nick Østergaard wrote:
>
> Hmm, ok, I guess you mean the -may27 one.. i
Hmm, ok, I guess you mean the -may27 one.. it seem to have never commits.
https://github.com/twlostow/kicad-dev/tree/tom-crash-reporter-may27
On Tue, 16 Jul 2019 at 11:08, Tomasz Wlostowski
wrote:
>
> On 15/07/2019 14:43, Nick Østergaard wrote:
> > Remind me, is this feature still i
Hello Devs,
Currently I see this error on master:
/var/lib/jenkins/workspace/linux-kicad-head/src/eeschema/tools/sch_editor_control.cpp:
In lambda function:
/var/lib/jenkins/workspace/linux-kicad-head/src/eeschema/tools/sch_editor_control.cpp:496:92:
error: lvalue required as unary '&' operand
Without speculating too much about the subject, I would expect it to
be case sensitive. Having stuff case insensitive other than in a
search box seem like trouble to me.
On Tue, 16 Jul 2019 at 11:43, Tomasz Wlostowski
wrote:
>
> Hi,
>
> I have design with a multi-row connector with pins labeled
Remind me, is this feature still in a seperate branch to master, or
how is it enabled?
On Thu, 11 Jul 2019 at 21:08, Nick Østergaard wrote:
>
> @Tomasz Wlostowski I just found that it looks like someone has
> uploaded a wxwidgets 3.1 pkgbuild for the mingw-packages for msys2, I
&g
s weekend but
> this seems like a quiet transition so far. :)
>
> -Seth
>
> On 2019-07-12 05:00, Nick Østergaard wrote:
> > Just for the record, I did build test it on msys2/mingw on windows, I
> > added these args to cmake.
> >
> > -DCMAKE_CXX
Just for the record, I did build test it on msys2/mingw on windows, I
added these args to cmake.
-DCMAKE_CXX_STANDARD=14 \
-DCMAKE_CXX_STANDARD_REQUIRED=ON \
-DCMAKE_CXX_EXTENSIONS=OFF \
-DCMAKE_CXX_FLAGS=-U__STRICT_ANSI__ \
The __STRICT_ANSI__ is required because of using wx 3.0 as far as I
@Tomasz Wlostowski I just found that it looks like someone has
uploaded a wxwidgets 3.1 pkgbuild for the mingw-packages for msys2, I
could try to build and and rebuild your branch for windows.
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-wxWidgets3.1/PKGBUILD
On Tue, 9 Jul 2019
It looks like people are happy with the patches, can we get them
merged so they don't get lost and we don't need to rebase them locally
all the time?
On Fri, 5 Jul 2019 at 19:01, Simon Richter wrote:
>
> Hi,
>
> On Fri, Jul 05, 2019 at 06:24:45PM +0200, Tomasz Wlostowski wrote:
>
> > > I can't
d: keep it as is
e: prepend the branch to what we currently have
On Wed, 10 Jul 2019 at 17:55, Wayne Stambaugh wrote:
>
> On 7/9/19 4:49 PM, Carsten Schoenert wrote:
> > Hello Nick,
> >
> > Am 09.07.19 um 21:57 schrieb Nick Østergaard:
> >> I have a hard time
An option could be to prepend the branch name via something like:
git symbolic-ref -q --short HEAD
To the git describe --long we already have.
On Tue, 9 Jul 2019 at 21:57, Nick Østergaard wrote:
>
> I have a hard time to understand how 5.99 is better to describe a
> development vers
19 klo 23.47 Nick Østergaard (oe.n...@gmail.com) kirjoitti:
>>
>> How is a number like 99 being any better than the latest release tag?
>>
>
> Did you read the original post, about the current problem? What is the
> "latest release tag"? 5.1.0 or 5.1.2? Number lik
How is a number like 99 being any better than the latest release tag?
On Mon, 8 Jul 2019 at 22:43, Eeli Kaikkonen wrote:
>
>
>
> ma 8. heinäk. 2019 klo 21.23 Wayne Stambaugh (stambau...@gmail.com) kirjoitti:
>>
>> Honestly, I don't have a strong preference
>> one way or another. If someone can
@Wayne I think the current one is fine.
@Kevin, And the version is not just the tag and number of commits, but
also the sha1.
On Mon, 8 Jul 2019 at 20:23, Wayne Stambaugh wrote:
>
> It used to be 6.0.0-dev but apparently this caused package version
> issues so it was dropped in favor of the
Please see
https://bugs.launchpad.net/kicad/+bug/1835408/comments/3
I think this is the same issue. Do a clean build.
On Mon, 8 Jul 2019 at 14:01, Dino Ghilardi wrote:
>
> commit 4852c91b423abf1e3e745f9d17ad56c92d5445b8
>
> does not compile for me on Linux, even re-generating config files with
Cool, thank you for verifying.
ons. 3. jul. 2019 14.54 skrev Seth Hillbrand :
> On 2019-07-03 02:12, Nick Østergaard wrote:
> > On Wed, 3 Jul 2019 at 06:39, Seth Hillbrand wrote:
> >> Hi Nick-
> >>
> >> Tested with latest nightly and it works nicely on 1
On Wed, 3 Jul 2019 at 06:39, Seth Hillbrand wrote:
>
> On 2019-07-01 16:38, Nick Østergaard wrote:
> > Good news, it seems like we managed to make the kicad-mac-packaging
> > scripts happy.
> >
> > After upgrading to ngspice 30 we had to update the include pa
e ngspice. I have filed an issue if someone has a
> > quick one to add.
> >
> > https://github.com/KiCad/kicad-mac-builder/issues/90
> >
> > Adam
> >
> > On Mon, Jul 1, 2019, 9:43 PM Nick Østergaard wrote:
> >>
> >> Good news, it seems like w
Hello Tomasz
Do you have any comments on the wxwidgets version?
It looks like 3.0.4 of wxwidgets is the latest version packaged in
msys2 as of today.
On Wed, 12 Jun 2019 at 23:58, Nick Østergaard wrote:
>
> It looks like you mis-cited me there. That was Wayne that wrote that,
> I do
heers.
On Fri, 21 Jun 2019 at 11:16, Nick Østergaard wrote:
>
> I see no reason to make ngspice 30 a strict minimum requirement.
>
> Lets just help packagers update to the latest ngspice and we are good.
>
> tor. 13. jun. 2019 18.33 skrev Wayne Stambaugh :
>>
>
Ok, thank you for the fix. It looks like it works. :)
On Wed, 26 Jun 2019 at 19:29, jp charras wrote:
>
> Le 26/06/2019 à 18:26, Nick Østergaard a écrit :
> > Hello JP et. al,
> >
> > It looks like I have issues building pcb_parser.cpp after
> > eb1faebf1f
Hello JP et. al,
It looks like I have issues building pcb_parser.cpp after
eb1faebf1f72bd5350f0dbffa0eb6aa22a15918e
See the attached file for the build error I get
I can reproduce this easily with make -j40
In the log snippet I did even do make -j1 after it failed once.
I don't think this
You probably started the msys2 environment shell. You need to start
the mingw shell environment.
On Wed, 26 Jun 2019 at 14:37, Pradeepa Senanayake
wrote:
>
> Hello All,
>
> I tried to build the KiCad source in Windows 10 MSYS2 environment using the
> steps available in the
>
Ok, I guess that is the safest option and if one requires a track there one
could just draw it manually.
lør. 22. jun. 2019 18.52 skrev Jeff Young :
> Yes.
>
> On 22 Jun 2019, at 17:39, Nick Østergaard wrote:
>
> Ah, ok, it os the chamfers. I didn't realise that. What are
e doesn’t go between the two pads because their thermal relief
> value doesn’t allow enough room.
>
> Cheers,
> Jeff.
>
>
> On 22 Jun 2019, at 17:04, Nick Østergaard wrote:
>
> Mmm, I am not sure I under stamd that screenshot. Why are the zone not
> touchimg the thermal
Mmm, I am not sure I under stamd that screenshot. Why are the zone not
touchimg the thermal track between the pads while it looks like there is a
part of zone area on the middle of the thermal track?
lør. 22. jun. 2019 17.58 skrev Jeff Young :
> Our current algorithm will produce thermal
rket for 5.1 python3 enabled win64 installer.
>
> Regards, Mitja
>
>
> On Saturday, 23 March 2019, 12:47:50 CET, Nick Østergaard
> wrote:
>
>
> Ok, I can try that, but I am on vacation thus week, so I am not sure I will
> get arpund to it very soon.
>
> lør. 23.
I see no reason to make ngspice 30 a strict minimum requirement.
Lets just help packagers update to the latest ngspice and we are good.
tor. 13. jun. 2019 18.33 skrev Wayne Stambaugh :
> On 6/10/19 4:01 PM, Carsten Schoenert wrote:
> > Hello Wayne,
> >
> > Am 10.06.19 um 20:15 schrieb Wayne
Would it make sense to have them in the demos folder under some folder
where it is evident that they are for testing and not showcasing?
tor. 20. jun. 2019 18.51 skrev Wayne Stambaugh :
> Marco,
>
> For one shot warning messages like the new zone fill algorithm, wouldn't
> a simple project with
Awesome, thanks!
On Tue, 18 Jun 2019 at 00:03, Seth Hillbrand wrote:
>
> On 2019-06-17 17:02, Nick Østergaard wrote:
> > Hello Seth,
> >
> > It looks like a recent change you made broke one of the unittest.
> >
> > See https://jenkins.simonrichter.eu/job/li
lable Vector Graphics'
handles extension: svg
test_graphics_import_mgr.cpp(106): error: in
"GraphicsImportMgr/SelectByExt": check !!plugin has failed
test_graphics_import_mgr.cpp(106): error: in
"GraphicsImportMgr/SelectByExt": check !!plugin has failed
Regards
Nick Østergaard
_
+1
tor. 13. jun. 2019 22.38 skrev Seth Hillbrand :
> Hi All-
>
> Right now, our minimum cmake version is 2.8.12. I'd like to bump this
> up to 3.0.2. This will assist in cleaning up a number of workarounds in
> our build system. 3.0.2 or greater appears to be available for all
> platforms
, Tomasz Wlostowski
wrote:
>
> On 11/06/2019 22:29, Nick Østergaard wrote:
> > Too bad the gcc windows
> > build crash report doesn't have a stack trace. Maybe MSVC builds would
> > have more debug info.
>
> Hi Nick,
>
> My build (wx 3.1.1) under MSYS has stack trac
Yes, that was the same commit I tested as mentioned earlier. Although
somehow added a "not" in the original message :)
On Tue, 11 Jun 2019 at 00:52, Wayne Stambaugh wrote:
>
> Did you test the latest commit 2745a95b6b02c3864d6594503cc21619691cdd94?
>
> On 6/10/19 6:02 PM,
It didn't seem to work for the use case I described on windows last week.
On Mon, 10 Jun 2019 at 23:51, Wayne Stambaugh wrote:
>
> Hey Tom,
>
> On 6/4/2019 12:31 PM, Tomasz Wlostowski wrote:
> > On 04/06/2019 17:11, Tomasz Wlostowski wrote:
> >
> >> Hi Wayne,
> >>
> >> It looks like I screwed up
I made it a dash 2 pkgrel for windows, I suggest doing the same for the
macos package.
man. 10. jun. 2019 10.51 skrev Carsten Schoenert :
> Hi,
>
> Am 10.06.19 um 01:46 schrieb Ian McInerney:
> > Is there a reason that pushing a change like this can't wait until the
> > 5.1.3 release?
>
> that's
Hello, I have some comments as well:
I was under the impression that is was only split to multiple options
because it was easier to help isolate issue, i.e. only intended for
developers/packagers to enable/disable some of the options.
The action menu one should probably just be removed and
I see the same.
tor. 6. jun. 2019 00.04 skrev Steven A. Falco :
> On 6/5/19 5:50 PM, Steven A. Falco wrote:
> > I just started getting the following error on Linux. Is anyone else
> seeing this?
>
> Looks like it is coming from commit
> 6fab7cc02512ddc47d42403d4d1ea3f88f832d14. If I remove
Also reporter at https://bugs.launchpad.net/kicad/+bug/1831705
On Wed, 5 Jun 2019 at 14:36, Eeli Kaikkonen wrote:
>
> It was just found out
> (https://forum.kicad.info/t/bug-align-to-right-left-does-the-same-thing-on-bottom-side/17149/9)
> that commit 6bcf1839b7a6 added max_error which causes
You can testrun it on windows from:
https://kicad-downloads.s3.cern.ch/windows/testing/patched/kicad-patched-371-5.1.0-770-g8bf750311-x86_64.exe
On Wed, 5 Jun 2019 at 08:17, Eeli Kaikkonen wrote:
>
> I'm trying to compile the reporter branch on Kubuntu. The official master
> branch compiles
I just tried to trigger a crash via the help menu and I see a fine
dialog, but that one I don't see for a real crash.
On Wed, 5 Jun 2019 at 00:12, Nick Østergaard wrote:
>
> I mean: I am really on 2745a95b6
>
> On Wed, 5 Jun 2019 at 00:11, Nick Østergaard wrote:
> >
> &
I mean: I am really on 2745a95b6
On Wed, 5 Jun 2019 at 00:11, Nick Østergaard wrote:
>
> Hello
>
> I just checkout out the crash reporter from Tom's branch. I am not on:
> 2745a95b6 (HEAD, tom/tom-crash-reporter-may27) crash_reporter:
> correctly install Windows exception h
Hello
I just checkout out the crash reporter from Tom's branch. I am not on:
2745a95b6 (HEAD, tom/tom-crash-reporter-may27) crash_reporter:
correctly install Windows exception handler under Kicad shell
I found a place in eeschema where it crashes. Specifically:
1. Open KiCad
2. Load the
Are you sure you did pull his latest changes?
It worked fine when I built it yesterday.
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-patch/369/
I just triggered a new build from his branch on github.
A sidenote: Could we delete the branch from the official github on
launchpad? And
we should
probably also give some very quick guide to provide backtraces, or is
this not needed with the new stuff from Tom?
So please indicate on the way forward. Should we add it to the dev
docs or the website?
Regards
Nick Østergaard
___
Mailing
It should work on the next build.
On Sun, 19 May 2019 at 17:35, Nick Østergaard wrote:
>
> Yes, I know, but judging the time stamps, it is only one day ;P
>
> I was trying tonenable the chinese translations of the unstaller, but somehow
> it still not happy.
>
> søn. 19.
Yes, I know, but judging the time stamps, it is only one day ;P
I was trying tonenable the chinese translations of the unstaller, but
somehow it still not happy.
søn. 19. maj 2019 17.25 skrev Seth Hillbrand :
> Hi Folks-
>
> Windows nightlies seem to be down for the past couple days. Looking
I have never seen anything like that.
Please do tell us exactly what your configuration is.
tor. 16. maj 2019 12.29 skrev :
> I've seen the following problem for some time when wxpython is enabled:
>
>
>
> [xcb]
Fixed.
On Wed, 15 May 2019 at 16:56, Nick Østergaard wrote:
>
> Hi Andrew
>
> I can confirm that the png's are not available.
>
> The doxygen stuff is built in
> https://github.com/KiCad/kicad-doc-website/blob/master/.docker/Dockerfile.kicad-doc-doxygen
>
> It is
hon/classpcbnew_1_1BOARD__ITEM.html
> This has been broken for a while.
>
> On Fri, May 10, 2019 at 7:59 AM Nick Østergaard wrote:
>>
>> Disclamier: I disabled the auto update for now as the change is not merged
>> pending review. I will fix it after the weekend.
>&g
> in master is 5685174808f5ca973e916a10f9f93660ee4dc4f2.
>
> Wayne
>
> On 5/14/19 3:47 AM, Nick Østergaard wrote:
> > @Wayne Stambaugh any impediments to getting this merged?
> >
> > On Fri, 10 May 2019 at 21:37, Steven A. Falco wrote:
> >>
> >> Here
@Wayne Stambaugh any impediments to getting this merged?
On Fri, 10 May 2019 at 21:37, Steven A. Falco wrote:
>
> Here is the result. Everything passed. The tests run surprisingly quickly.
>
> sh-5.0# make test
> Running tests...
> /usr/bin/ctest --force-new-ctest-process
> Test project
Hi
Why do we need a detailed graphical representation of the Skidl inner
workings? Isn't all we need its inputs and outputs a hier sheet or as any
other parts, some form of symbold for the interfaces (i/o)?
tor. 9. maj 2019 21.10 skrev Piotr Esden-Tempski :
> Hi,
>
> Just a thought. This
Disclamier: I disabled the auto update for now as the change is not merged
pending review. I will fix it after the weekend.
fre. 10. maj 2019 16.54 skrev Jon Evans :
> Thanks, Nick!
>
> On Thu, May 9, 2019 at 4:38 PM Nick Østergaard wrote:
>
>> It should work now, and it may
It should work now, and it may also be a bit more responsive.
On Thu, 9 May 2019 at 16:16, Nick Østergaard wrote:
>
> I know. I will report back when it works.
>
> tor. 9. maj 2019 16.15 skrev Jon Evans :
>>
>> Still down
>>
>> On Wed, May 8, 2019 at 3:27 PM W
I know. I will report back when it works.
tor. 9. maj 2019 16.15 skrev Jon Evans :
> Still down
>
> On Wed, May 8, 2019 at 3:27 PM Wayne Stambaugh
> wrote:
>
>> Still no luck :(
>>
>> On 5/8/19 10:12 AM, Nick Østergaard wrote:
>> > Ok, thank you for
Nothing attached
tor. 9. maj 2019 09.45 skrev :
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help :
Ok, thank you for the notification.
It looks like the publish job jot stuck in a retry loop, I have
restarted it and it should be back within half an hour I hope.
On Wed, 8 May 2019 at 15:15, Ben Hest wrote:
>
> It's down for me.
>
> On Wed, May 8, 2019 at 6:20 AM Wayne Stambaugh wrote:
>>
>>
https://bugs.launchpad.net/kicad/+bug/1816286
ons. 8. maj 2019 15.40 skrev Nick Østergaard :
> Is the swig version 4.0.0?
>
> ons. 8. maj 2019 15.39 skrev Steven A. Falco :
>
>> I've started getting a build error on 5.1.2 in Fedora rawhide. Here is
>> part of the log:
Is the swig version 4.0.0?
ons. 8. maj 2019 15.39 skrev Steven A. Falco :
> I've started getting a build error on 5.1.2 in Fedora rawhide. Here is
> part of the log:
>
> [ 68%] Generating pcbnew_wrap.cxx, pcbnew.py
> cd /builddir/build/BUILD/kicad-5.1.2/pcbnew && /usr/bin/cmake -E
>
I guess this is sort of related to the observation and response I got here:
https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg27587.html
Or maybe I misunderstand what exactly you mean.
On Mon, 6 May 2019 at 12:38, Jeff Young wrote:
>
> Eelik reported that our cross-probing
Hello Jeff,
I ran my "evaluate" script on your branch and there are a couple of
commits that are not buildable, see
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-evaluate/107/artifact/build-report.txt
As usual the builds logs are available on the jenkins job if you need
them. (You may
Congratulations Wayne. That sounds like good news for everyone. But
remember not to burn yourself out, just the opportunity to take a
break from kicad in your "spare" time then :)
On Sat, 27 Apr 2019 at 20:05, Wayne Stambaugh wrote:
>
> For those you who haven't heard yet, I made the
It looks like there is an issue with the patch builds, the kicad
binaries are not included in the installer, only some dependencies...
So don't use that build.
On Fri, 3 May 2019 at 16:00, Nick Østergaard wrote:
>
> I have uploaded a build of the eemodern branch on
&
I have uploaded a build of the eemodern branch on
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-patch/lastSuccessfulBuild/artifact/out/pack-x86_64/kicad-patched-330-5.1.0-437-gc807783d7-x86_64.exe
On Fri, 3 May 2019 at 14:06, Brian Piccioni wrote:
>
> Hello Devs
>
>
>
> This is well
Maybe it will be fixed in the next release of cmake
https://gitlab.kitware.com/cmake/cmake/merge_requests/2747
Found via https://gitlab.kitware.com/cmake/cmake/issues/18865
On Wed, 1 May 2019 at 22:34, Nick Østergaard wrote:
>
> @Wayne, please note that I think there is a workaround.
@Wayne, please note that I think there is a workaround. I have not
tested it myself, but I guess you can configure kicad with
Boost_NO_BOOST_CMAKE=ON as mention in the github issue.
On Wed, 1 May 2019 at 20:33, Wayne Stambaugh wrote:
>
> Jeff,
>
> I think that was a different issue. My issue
I don't think so, at least when I look at the PKGBUILD it is still
using bootstrap.sh and b2 to build. See:
https://github.com/msys2/MINGW-packages/blob/fd550b8d48e6bc831b1e36202eaf495cba5062f8/mingw-w64-boost/PKGBUILD
I don't see anything immediately alarming. Maybe the builds scripts in
boost
It worked fine in the past, but at some point the emails never reached the
mailing list. I am not sure if it was some email config on jenkins that
needed to be updated or what it was, but I never really tried to enable it
after the move because of the issues with the logs not really being public
Hi John
The one on ci.kicad-pcb.org does not exist after the move to some CERN
infra. I don't really like the setup as is. The intention is to have the
builds public, but they can not be like that at the moment because of the
infrastructure design. This is one of the reasons that we have not
Look in the dev console, it is the mimetype that is sometimes wrong.
It seems like it is not a good idea to host it directly is s3 like this. I
will make it more reliable at a later time.
tir. 23. apr. 2019 20.21 skrev Brian Piccioni :
> Foobared on Chrome Windows for me the past few days I've
201 - 300 of 1794 matches
Mail list logo
