kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

On 4 August 2011 10:02, Brian Sidebotham <brian.sidebotham@xxxxxxxxx> wrote:
> On 3 August 2011 20:01, Kerusey Karyu <keruseykaryu@xxxxx> wrote:
>> Dnia 2011-08-01, pon o godzinie 21:53 +0100, Brian Sidebotham pisze:
>>> On 1 August 2011 09:52, Brian Sidebotham <brian.sidebotham@xxxxxxxxx> wrote:
>>> > On 31 July 2011 09:05, Kerusey Karyu <keruseykaryu@xxxxx> wrote:
>>> >> Brian, take a look at the shell screenshot and logs. Something is wrong
>>> >> with wxWidgets section.
>>>
>>> Hi Kerusey,
>>>
>>> I have just fixed the wxWidgets build problem, and also the
>>> out-of-date MinGW installer URL. Hopefully the MinGW installer will
>>> become stable soon.
>>>
>> Well. The script is now working. :) MinGW was installed, wxWidgets are
>> build, Kicad binaries also. But...
>>
>> After a 2 hours of script progress:
>> 1) Kicad binaries are hudge. eeschema.exe is an ~10MB file for example.
>
> Then they have debug symbols in. I will look into it. Maybe cmake
> install strips the binaries of debug symbols.
>
>> 2) Kicad binaries searching for libstdc++-6.dll and libgcc_s_dw2-1.dll
>> I have found it on SF, but I think something (wx or Kicad) need a patch
>> for easy Windows build.
>
> Yuk, but okay. I will look into this too. You should find both in the
> mingw/bin directory under the kicad-winbuilder directory. I expect
> bumping the mingw installer bumped the version of gcc they default
> too.
>
> You will also find libgcc_s_dw2-1.dll under the KiCad bin directory. I
> will do a vanilla test again. I obviously have these dll's in my path
> somewhere.

The easiest thing for me to do might be to copy all binaries and
supporting dll's from the mingw installation to an output directory
where the new version will run without dependency problems.

Brian.