Hello, Augusto!
Your ideas regarding multiplexed I/Os are good, but might only be sufficient
for small to medium-complex CPUs/FPGAs/modules/circuits. If you follow the
latest developments, you will notice that there are even bigger things coming
up and it will get more and more difficult to vis
This is dependent on the size of the change. If it's small change,
patches are fine. If it's a very large change, then I prefer that you
create a public repo on launchpad so I can clone it locally to review
and test it. You have to use your best judgment on this.
It's important to get input fro
There is no specified policy about this as far as I see it.
Generally we only use the bug tracker for bugs and stuff where people just
don't have time to start coding. So in conclusion, you should be good if
you just send patches to the dev list.
If you want to create some bugs to relate to 6.0 f
You can remove the boost patches. They are only of historical
concern, and they'll live in Git for any future archaeologist who
cares.
Adam
On Tue, Jan 30, 2018 at 3:20 PM, Jeff Young wrote:
> Yeah, I didn’t patch my boost either. (I can’t remember if I MacPorts’d it
> or Homebrew’d it, but I
If we implement a feature or an improvement to a feature, does it need an
issue, or do we just send patches to the dev-list?
(Obviously this is for 6.0, so I’m just trying to understand the process.)
Thanks,
Jeff.
___
Mailing list: https://launchpad.ne
Yeah, I didn’t patch my boost either. (I can’t remember if I MacPorts’d it or
Homebrew’d it, but I didn’t do anything beyond that.)
> On 30 Jan 2018, at 21:13, Bernhard Stegmaier wrote:
>
> Wayne,
>
> I don’t think so.
>
> I use a stock MacPorts boost since long before you removed boost fro
Wayne,
I don’t think so.
I use a stock MacPorts boost since long before you removed boost from KiCad
build.
This might not be representative, but I didn’t see any problems.
I had a quick look into Adams build scripts and I didn’t see that he is
building his own boost (with the patches) somewhe
Bernhard,
What about the macos boost and context patches? Do we still need to
keep them?
Thanks,
Wayne
On 1/29/2018 1:23 PM, Bernhard Stegmaier wrote:
> Wayne,
>
> yes, from my side you can delete them.
> Even if deleted they are in git anyway, so we can restore them if really
> needed.
> I’l
Nick-
Thanks for the test. I'm attaching revised patch that allows multiple
OpenCASCADE installations on a single machine.
I've tested with a few different OpenCASCADE versions down to 6.8 with no
issues installed alongside OCE 0.17. You can choose which you want to link
by using either "-DKICA
Seth,
I finally got around to testing this patch and I'm getting a cache
library load error when I add a symbol from a library nickname with a
space. I manually edited my sym-lib-table file and modified a library
nickname with space then added a symbol to a schematic. I saved the
schematic, clos
I get the same issue with OCCT 7.2.0.
2018-01-29 23:30 GMT+01:00 Nick Østergaard :
> Hi Seth,
>
> I just took the patch for a testrun and will state some comments below.
>
> This looks a bit strange:
>
> -- Boost version: 1.66.0
> -- -- OpenCASCADE Community Edition has been found.
> -- -- Found
Augusto,
Most of this is going to be addressed during the next development cycle
when the new symbol library and schematic file format are implemented.
At the moment, there is no plan at this time to allow for resizing
symbols in schematics. Since symbols will be embedded in the schematic,
resizi
Hi,
I've been designing schematics with some stm32 parts using the standard
Kicad libraries, and a lot of these microcontrollers has 10+ functions
multiplexed in each I/O pin. In the standard library the symbols
displays all possible configurations available to each pin, I understand
the moti
OCCT is usually quite a few commits ahead of OCE; in fact OCE is
usually based on the earlier release of OCCT. In addition to that,
since we build in MSYS on MSWin, a patch (which is an ugly hack) is
required to support non-ASCII characters in file names.
- Cirilo
On Mon, Jan 29, 2018 at 8:08 PM,
14 matches
Mail list logo
