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 path for
some unknown reason. But it seems like it should work now. The first
build has been pushed to the
> On Jul 1, 2019, at 1:38 PM, 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 path for
> some unknown reason. But it seems like it should work now. The first
> build
Hi Adam
I did add a testing instruction to your issue.
I am a bit curious about what the build error is that you see for mac
10.11 and ngspice 30. The other build you do are called 11.14. I
assume 11.14 does not work on 11.12.
It looks like the nightlies from the old nightlies build are better,
On 7/2/19 4:02 PM, Seth Hillbrand wrote:
> Looks good on Debian also. Tried to break it with varying parallelisms and
> file mods. No issues.
>
> Nice work, Simon!
I did a clean "make -j12" build on Fedora, and it worked fine.
Steve
___
Looks good on Debian also. Tried to break it with varying parallelisms
and file mods. No issues.
Nice work, Simon!
On 2019-07-02 15:35, Wayne Stambaugh wrote:
I gave this a quick test on msys2 builds and it seems to work fine for
me.
On 7/2/2019 11:31 AM, Simon Richter wrote:
Hi,
On
ti 2. heinäk. 2019 klo 22.42 Jeff Young (j...@rokeby.ie) kirjoitti:
> Reusable sheets are undeniably cool. But how often are they used? Are
> they worth the headache/bugs/limitations/etc.?
>
>
What are "reusable sheets"? I have tried a couple of things. Copying a
whole file to another project;
I gave this a quick test on msys2 builds and it seems to work fine for me.
On 7/2/2019 11:31 AM, Simon Richter wrote:
> Hi,
>
> On Mon, Jul 01, 2019 at 12:33:43PM -0400, Seth Hillbrand wrote:
>
>> [ 38%] Building CXX object
>>
I'm with Jeff here. It may be easier to implement a "schematic block"
library function like [1] to handle the reusable aspect for UX and then
tie the actual sheets to the root schematic.
-S
[1] https://bugs.launchpad.net/kicad/+bug/1797683
On 2019-07-02 14:48, Jeff Young wrote:
Reusable
Reusable sheets are undeniably cool. But how often are they used? Are they
worth the headache/bugs/limitations/etc.?
> On 2 Jul 2019, at 19:34, Wayne Stambaugh wrote:
>
> Hierarchical sheets, the gift that keeps on giving. There are many
> subtle and not so subtle issues in play here so be
Hierarchical sheets, the gift that keeps on giving. There are many
subtle and not so subtle issues in play here so be very, very careful.
The probably of breaking hierarchical schematics in spectacular ways is
high. I still haven't determined the ideal solution for the new file
format, that's
Seth,
On 7/2/2019 12:36 PM, Seth Hillbrand wrote:
> On 2019-07-02 12:21, Simon Richter wrote:
>> Hi,
>>
>> On Tue, Jul 02, 2019 at 11:42:30AM -0400, Seth Hillbrand wrote:
>>
>>> Instead of banging on this dependency, I could push option #2 from
>>> my previous e-mail. This was creating a
This is not a project priority and is not going to happen. If you want
a more detailed explanation, please search the dev mailing list archives.
Cheers,
Wayne
On 7/2/2019 12:20 PM, Dino Ghilardi wrote:
> Just a thought (may be a little off-topic):
>
> Since old pcbnew versions will not be
On 2019-07-02 12:21, Simon Richter wrote:
Hi,
On Tue, Jul 02, 2019 at 11:42:30AM -0400, Seth Hillbrand wrote:
Instead of banging on this dependency, I could push option #2 from
my previous e-mail. This was creating a separate target to rebuild
the generated files and checking them into the
On 2019-07-02 11:31, Simon Richter wrote:
Hi,
On Mon, Jul 01, 2019 at 12:33:43PM -0400, Seth Hillbrand wrote:
[ 38%] Building CXX object
eeschema/CMakeFiles/eeschema_kiface_objects.dir/widgets/symbol_tree_pane.cpp.o
Hi,
On Tue, Jul 02, 2019 at 11:42:30AM -0400, Seth Hillbrand wrote:
> Instead of banging on this dependency, I could push option #2 from
> my previous e-mail. This was creating a separate target to rebuild
> the generated files and checking them into the source tree. Then we
> don't try to
Just a thought (may be a little off-topic):
Since old pcbnew versions will not be able to open files in new format,
there should be a way to export a pcb in the "old/stable" format, so
that when testing latest development version of pcbnew on an old board
(and saving it) can be undone
On 7/2/2019 11:11 AM, jp charras wrote:
> Le 02/07/2019 à 16:55, Jeff Young a écrit :
>> I was testing 5.1 and noticed that it can no longer open 6.0 files. Was
>> this accidental, or have we now diverged?
>>
>> (I ask only because I have a bunch of fixes waiting for file format changes
>>
Hi,
On Mon, Jul 01, 2019 at 12:33:43PM -0400, Seth Hillbrand wrote:
> [ 38%] Building CXX object
> eeschema/CMakeFiles/eeschema_kiface_objects.dir/widgets/symbol_tree_pane.cpp.o
> /home/seth/code/kicad/kicad_bare/eeschema/dialogs/panel_sym_lib_table.cpp:29:10:
> fatal error: lib_table_lexer.h:
Thanks!
I'll give it a try.
-Original Message-
From: Simon Richter
Sent: July 2, 2019 10:22 AM
To: Brian Piccioni
Cc: 'KiCad Developers'
Subject: Re: [Kicad-developers] [PATCH 0/9] MSVC build support
Hi,
On Tue, Jul 02, 2019 at 09:18:23AM -0400, Brian Piccioni wrote:
> When I
I have not yet been able to get 10.11 to build with ngspice 30. I
will only look for a little bit. Our policy would have us upgrade to
10.12 as a minimum requirement anyway, since 10.11 no longer gets
security updates.
Adam
On Mon, Jul 1, 2019 at 10:03 PM Adam Wolf wrote:
>
> I do not
Le 02/07/2019 à 16:55, Jeff Young a écrit :
> I was testing 5.1 and noticed that it can no longer open 6.0 files. Was this
> accidental, or have we now diverged?
>
> (I ask only because I have a bunch of fixes waiting for file format changes
> which I could go ahead and make if we have
I was testing 5.1 and noticed that it can no longer open 6.0 files. Was this
accidental, or have we now diverged?
(I ask only because I have a bunch of fixes waiting for file format changes
which I could go ahead and make if we have officially diverged.)
Cheers,
Jeff.
Doesn’t get around the problem. If I do a Find/Replace All, I want changes
across all sheets.
Same problem with Symbol Fields Editor, Global Edit Text and Graphics
Properties, etc.
And it also doesn’t fit the user’s model when they have multi-unit components
split across sheets. I think
Hi,
On Tue, Jul 02, 2019 at 09:18:23AM -0400, Brian Piccioni wrote:
> When I click this linkhttps://git.launchpad.net/~sjr/kicad/msvc-new . I
> get Invalid request
> I assume there is an MSVC KiCad repos out there and I’m sure like to try it.
Hmm, apparently the URL format for Launchpad
This is the direct link to the repo tree for viewing on the web:
https://git.launchpad.net/~sjr/kicad/tree/?h=msvc-new. I believe the link
that Simon sent out before is the URL needed to do a git clone of the repo.
-Ian
On Tue, Jul 2, 2019 at 2:18 PM Brian Piccioni
wrote:
> Since I have been
Hi Jeff-
Got it, thanks.
When we switch to the new schematic format, could we just make sure that
we don't share components around the schematic? Each has their own
SCH_COMPONENT and embedded symbol?
-Seth
On 2019-07-02 06:25, Jeff Young wrote:
Hi Seth,
Let’s say that you change the
Hi Seth,
Let’s say that you change the datasheet of a component that exists in two
sheets. The undo information needs to go in each sheet. Now you go to the
other sheet and perform another action. The datasheet change is now the second
item on the stack in that sheet. Now you go back to
On 2019-07-02 02:51, Jeff Young wrote:
I think I’ve figured out a neat (and easy) way to solve multi-sheet
undo:
1) move the undo stacks to the SCH_EDIT_FRAME
2) stack sheet navigations as undoable operations
This way the conceptual sheet-specific stacks can’t get out of
alignment as you have
Since I have been using MSVC for RenumKiCadPCB development for several months
now I am keen to try the MSVC build so I can work on integrating the function.
When I click this linkhttps://git.launchpad.net/~sjr/kicad/msvc-new . I get
Invalid request
I assume there is an MSVC KiCad
I wouldn't use anything before 2015 since that was before C++11 support was
"finished".
Simon, did you ever try 2019 since it's been out for awhile now?
On Tue, Jul 2, 2019 at 6:54 AM Simon Richter
wrote:
> Hi,
>
> > What is the minimum version of MSVC required for building this?
>
> I use
Hi,
> What is the minimum version of MSVC required for building this?
I use 2017 Build Tools. It should probably work with 2012 and 2015 as well.
Simon
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
I think I’ve figured out a neat (and easy) way to solve multi-sheet undo:
1) move the undo stacks to the SCH_EDIT_FRAME
2) stack sheet navigations as undoable operations
This way the conceptual sheet-specific stacks can’t get out of alignment as you
have to go through the sheet navigation
32 matches
Mail list logo
