Eeschema warning after opening my schema file(latest Win nightly build)

[Andy]

Application: kicad
Version: (2016-09-17 revision 679eef1)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.46.0 OpenSSL/1.0.2d zlib/1.2.8 libidn/1.32 libssh2/1.6.0 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.57.0
Curl: 7.46.0
KiCad - Compiler: GCC 5.2.0 with C++ ABI 1009
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=ON
                  KICAD_USE_OCE=ON

Steps to reproduce:

1. Launch KiCAD
2. Try to open usbasp.sch

Result: see screenshot http://s019.radikal.ru/i612/1609/41/fe9c23f532ce.png

[Nick Østergaard (nickoe)]

This is not a bug, this is just from the fact that the special lib has been removed/split up to other libs. The symbols should be available in the *-cache.lib file. If it is not present you can probably find the old special.lib somewere and use that if you care.

[Andy (sparco025)]

* -cache.lib File is in a folder, but still warning.
When I open my other schemes Eeshema stops responding. Need help

[Nick Østergaard (nickoe)]

What folder? It should be next to your sch file. How do you open the other schematocs, are they part of the same project?

[Andy (sparco025)]

All files are in the project folder with the file * .pro.
I usually open the projects as follows:
1) Open KiCad
2) File -> Open Project(select folder -> open *.pro file)
3) Then I see the files in the project tree -> double click to open my *.sch

Every *.sch file is part of the same project.

Project usbasp(not my project, but folder contains * -cache.lib), which I sent scheme at the opening gives a warning(you saw screenshot), and other projects generally hang eeschema.

[Wayne Stambaugh (stambaughw)]

@Nick, I noticed in this bug report that the nightly builds are being
configured with -DKICAD_USE_SCH_IO_MANAGER=ON. Is this still the case?
If so, please disable it. I really didn't intend for users to be
testing this yet, only developers for round trip file testing. It is
highly likely there are library management issues with this code. I'll
default this option to on when it's ready for general user testing.

Thanks,

Wayne

On 9/28/2016 4:51 AM, Nick Østergaard wrote:
> What folder? It should be next to your sch file. How do you open the
> other schematocs, are they part of the same project?
>

[Nick Østergaard (nickoe)]

@Andy, I still don't really know what your issue is. If you are talking about the special lib that is simply because it has been removed from the library and your project file is expecting it. The one with the xilinx.dcm libs is a library issue which should be addressed at https://github.com/KiCad/kicad-library/blob/master/library/xilinx.dcm

@Wayne, KICAD_USE_SCH_IO_MANAGER is off in the latest nightly now. I enabled it initially because they are nightlies and you asked for testing after all.

[Andy (sparco025)]

@Nick, When I open a little more complicated scheme, the following error pops up http://s017.radikal.ru/i425/1609/51/b7b74bd6c221.png

[Wayne Stambaugh (stambaughw)]

@Nick, that's definitely the new plugin choking on a parsing error. It
looks like it's one of our libraries so I don't need Andy's library to
debug it unless he has modified this library.

@Andy, Nick enabled the new schematic I/O plugin in nightly builds which
isn't quite ready for general testing. He has since disabled this so
please use one of the latest nightly builds which should resolve your issue.

On 9/29/2016 6:37 AM, Andy wrote:
> @Nick, When I open a little more complicated scheme, the following error
> pops up http://s017.radikal.ru/i425/1609/51/b7b74bd6c221.png
>

[Wayne Stambaugh (stambaughw)]

Found yet another anomaly in the component library text definition that I had not run across yet so I'll fix it when I get a chance.

[KiCad Janitor (kicad-janitor)]

Fixed in revision 9d258ba921c1341718015575bb83645a866c6065
https://git.launchpad.net/kicad/patch/?id=9d258ba921c1341718015575bb83645a866c6065

[Wayne Stambaugh (stambaughw)]

Fix committed in product master branch commit 9d258ba9.

[Andy (sparco025)]

Сommit 9d258ba9 fixed my problem. Thanx