← Back to team overview

kicad-developers team mailing list archive

Re: Simulator towards 5.0

 

I still think this is strange reasoning, so the version 5 will be built differently on every system? I thought v5 should include the spice simulator?

Are you saying there is no recommended way to deliver kicad? So when I send a file to my friend on windows, he might not be able to do the same things as I can on ubuntu, or on arch or whatever?

I understand that there are optional dependencies, but basically having the option to turn them off still seems better than having the option to turn them on. At least when turning them off I will understand why they are not in kicad. And a new developer might find this easier as well.

Can we at least have an update to the build docs that reflects what is deemed non-experimental or a line stating that everything should be turned on?

- Kristoffer

On 2017-12-07 16:53, Wayne Stambaugh wrote:
I hope users are no longer building kicad from source.  We tried that
already and it was a disaster.  The build options should reflect the
dependencies available on the platform it's being built on.  Whether or
not an optional feature is ready for release is not relevant.  For
example if ngspice was not built with the --with-libngspice option
(which apparently on arch linux it is not), setting KICAD_SPICE=ON will
fail during build config.  It is up to the system package developer to
determine if kicad should be built with spice support.

On 12/6/2017 9:04 AM, Kristoffer Ödmark wrote:
Are we not in feature freeze, the features that I enabled by default is
from my understanding the ones that will be built into the official
ones. And yes, the people that are compiling a non-standard install
shuld be savvy enough to be change the compilation settings. That is why
i think the default build should reflect the ones being run by the less
savvy users.

  -Kristoffer

On 12/06/2017 11:31 AM, Simon Richter wrote:
Hi,

On 06.12.2017 11:12, Kristoffer Ödmark wrote:

I do not see why anyone is even objecting to this? Where is the logic at
having a default build that does not correspond to any of the official
packages?!
That usually happens because the nightly builds enable all the
experimental features to allow people to test them, but the default is
still "disabled" because they introduce extra dependencies and make life
difficult for people compiling from source.

The default for new options needs to be decided before the release, I
think, and "release" packages should go with that.

     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
_______________________________________________
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



Follow ups

References