kicad-developers team mailing list archive

[Ian McInerney <Ian.S.McInerney@xxxxxxxx>]

Just to be clear, I was only going to focus on cleaning up the static
linkage in the current build process. While items in common could be moved
into a new DLL, I don't have enough experience with that to try to attempt
it right now.

-Ian

On Wed, Aug 28, 2019 at 4:31 PM Thomas Pointhuber <thomas.pointhuber@xxxxxx>
wrote:

> Please go for it. The separate DLLs make it hard to design a python api
> where eeschema and pcbnew can share resources.
>
> Regards, Thomas
>
> Am 28.08.19 um 16:03 schrieb Simon Richter:
> > Hi,
> >
> > On Wed, Aug 28, 2019 at 10:47:52AM +0200, Ian McInerney wrote:
> >
> >> I think that the only way to really fix this is to split common up into
> >> some smaller units,
> >
> > I had the same idea already. This works for some parts (for example I was
> > able to split off dlist as an experiment), but the base_units stuff
> cannot
> > be turned into a library right now.
> >
> > What might work would be defining the conversion factor in the Kiface
> > instantiation code and pass it down through the *_FRAME hierarchy, but
> that
> > would make all conversions require the frame as context (so it would
> break
> > my plan for a gradual replacement). Once the unit code is merged, there
> > isn't even a need to build separate DLLs anymore, we can just link
> > everything together.
> >
> >    Simon
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>