Global symbol library table copied from msys64 directory (not KiCad install directory) on Windows nightly

[Michael Kavanagh]

Application: kicad
Version: (2018-01-19 revision 673f03e59)-makepkg, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

[Wayne Stambaugh (stambaughw)]

The windows installer needs to be built with the -DDEFAULT_INSTALL_PATH set to c:\Program Files\kicad for 64 bit builds and c:\Program Files (x86)\kicad for 32 bit builds so at least the default install path is correct. This still does not solve the issue for users who change the default install path on windows. The only solution we currently have for that is to have the installer set the environment variables to the correct install path. Would our windows installer dev please set the -DDEFAULT_INSTALL_PATH build config variable correctly to eliminate this issue?

[Jeff Young (jeyjey)]

Will this also fix: https://bugs.launchpad.net/kicad/+bug/1744415 ?

[Jeff Young (jeyjey)]

Did this get fixed in the installer?

[Wayne Stambaugh (stambaughw)]

I'm sure this was fixed during 5.1 development when I added the new initial global library table configuration dialog.