Anyone out there willing to do some alpha testing? There are only two requirements: be able to build your own Kicad from a GIT branch, and be willing to provide feedback (email to dev list, launchpad bugs, replies here, whatever – I’m not picky).
@hermit, no the features in the other thread are in master (and therefore in the nightlies). The eemodern branch is still too incomplete (and buggy) for the nightlies.
(I’m using CLion and you can click on the folder and say “Exclude from Build”. However, IIRC I might have had to edit one of the CMakeFiles. I’m no expert at that so I’m tagging some more devs for help…)
For others, there is a functional docker image with build dependencies pre-installed (based on Ubuntu 16.04) that I posted, this will allow you to build the software in a virtual environment via a docker container. If other base images are needed, simply post a request.
So what’s different in the eemodern branch? Mostly the eeschema toolset. It’s now based on a selection model. There are some new “features” that fall out of this such as stingy vs greedy selections (like in PCBNew), clipboard-based cut/copy/paste (so you can paste between documents or even between KiCad and a text editor).
eeschema runs and there is a modern mode setting under preferences . Cannot take screenshot of this as eeschema capture keyboard input so hard that print screen does not get propogated to the. Version Info Below
Application: eeschema
Version: 5.1.0-unknown, release build
Libraries:
wxWidgets 3.0.2
libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-142-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
Boost: 1.58.0
OpenCASCADE Community Edition: 6.8.0
Curl: 7.47.0
Compiler: GCC 5.4.0 with C++ ABI 1009
Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_PYTHON3=OFF
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON
It’s compiler specific , since this behavior is actually a c extension in c++ and not actually c++ and thus up to implementation on the lifetime duration of the specified variable. GCC was picky about only one of them,but perhaps the others will show up as crashes. On some, stricter, c++ compilers without extensions it is liable to fail alltogether