kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

On 6 December 2011 06:33, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
> On 12/05/2011 05:08 PM, Brian Sidebotham wrote:
>> Hi Dick,
>>
>> I'm getting the following build error with rev 3270:
>>
>> kicad\pcbnew\kicad_plugin.cpp: In member function 'void
>> KICAD_PLUGIN::loadAllSections(bool)':
>> kicad\pcbnew\kicad_plugin.cpp:309:5: error: call of overloaded
>> 'IO_ERROR(const char [74], const char*, const char [20])' is ambiguous
>> kicad\include/richio.h:99:5: note: candidates are:
>> IO_ERROR::IO_ERROR(const char*, const char*, const std::string&)
>> kicad\include/richio.h:92:5: note:
>> IO_ERROR::IO_ERROR(const char*, const char*, const wxString&)
>
> The 2nd of the two hunks in the attached, already *committed* patch seem to fix this for
> wxWidgets 2.9.x.  And it still works for 2.8.
>
> (The first hunk was just a way to unify the __LOC__ strategy for _MSC_VER and gcc.)
>
> Should fly now, but you will still get warnings from kicad_plugin.cpp, which pertain to
> variables which I am refusing to stuff into globals.  I want to put those globals into the
> BOARD first.
>
> I am mostly tied up today with other stuff.
>
>
> *) kicad_plugin.cpp is not being called yet, so if you still have grief with it, comment
> it out in pcbnew/CMakeLists.txt.  I just wanted to start linking it in so that we could
> smoke out issues like this before we start calling it.
>
> There are just a few minor problems with calling it remaining.  This is why we have the
> parallel load path during testing.  We will be able to load an old board file with the new
> loader, and save it with the old saver.  The result should be identical to a save/load
> cycle using the old loader, and old saver, no?
>
> We'll see.
>
> Dick

Thank you very much for the quick response Dick. I will test ASAP.
Sorry, I didn't let you know what version of wxWidgets I was using or
anything! D'oh!

Best Regards,

Brian.