[4847] KiFACE Files Not Copied Into bin Directory

Bug #1315945 reported by Ian Woloschin
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kicad-winbuilder
Fix Released
Medium
Brian Sidebotham

Bug Description

I just built 4847 and I'm trying to run KiCAD via the RunKiCad.bat script. The Project Manager (KiCad.exe) loads fine, but trying to launch any other program (eeschema, PCBNew, etc) fails. Here's the failure from eeschema:

17:14:52: Failed to load shared library 'C:\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface' (error 0: the operation completed successfully.)
17:14:54: IO_ERROR: Fatal Installation Bug
missing file:
'C:\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface'

argv[0]:
'C:\kicad-winbuilder-3.3\kicad\bin\kicad.exe'
from C:\kicad-winbuilder-3.3\src\kicad\common\kiway.cpp : KiFACE() : line 208

Sure enough, that _eeschma.kiface file isn't there. Fortunately, a little bit of digging and I found it in another directory:

C:\kicad-winbuilder-3.3\build\Release\eeschema\_eeschma.kiface

If I copy that into 'C:\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface' then eeschema loads no problem. I'm not sure where the appropriate place to fix this issue is, if it's Windows specific or not, but I wanted to post my findings here so others don't get stuck on the same problem.

Related branches

Revision history for this message
Kerusey Karyu (keruseykaryu-deactivatedaccount) wrote :
Revision history for this message
Brian Sidebotham (brian-sidebotham) wrote :

I will fix this ASAP. Use the modifications in the comment linked to by Kerusey for now, the fix will be present in KiCad-Winbuilder 3.4

Changed in kicad-winbuilder:
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → Brian Sidebotham (brian-sidebotham)
Revision history for this message
m (easyw) wrote :

Hi Brian,
maybe it could be nice also to add kicad.pro file in template dir needed by eeschema to access to libraries from defined search path.
https://bugs.launchpad.net/kicad/+bug/1315868

thank you
Maurice

Changed in kicad-winbuilder:
status: Confirmed → Fix Committed
Revision history for this message
Abdullah Kahraman (cebrax) wrote :

Hello Brian,

I have downloaded and compiled kicad-winbuilder 4886 yesterday and I get the same error. The Project Manager runs fine but others does not, same as the OP. However, copying "_eschema.kiface" and "_pcbnew.kiface" files from "build/Release/eeschema" or "build/Release/pcbnew" does not help except for eeschema. I still get the same error for pcbnew and cvpcb.

Here is the error I get when I try to open eeschema:

10:03:43: Failed to load shared library 'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface' (error 0: the operation completed successfully.)
10:03:43: IO_ERROR: Fatal Installation Bug
missing file:
'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface'

argv[0]:
'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\eeschema.exe'
from C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\src\kicad\common\kiway.cpp : KiFACE() : line 212

Here is what I get when I try to open pcbnew:

10:08:16: Failed to load shared library 'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\_pcbnew.kiface' (error 0: the operation completed successfully.)
10:08:16: IO_ERROR: Fatal Installation Bug
missing file:
'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\_pcbnew.kiface'

argv[0]:
'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\pcbnew.exe'
from C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\src\kicad\common\kiway.cpp : KiFACE() : line 212

I get similar error for cvpcb:

10:14:39: Failed to load shared library 'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\_cvpcb.kiface' (error 0: the operation completed successfully.)
10:14:39: IO_ERROR: Fatal Installation Bug
missing file:
'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\_cvpcb.kiface'

argv[0]:
'C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\kicad\bin\cvpcb.exe'
from C:\kicad-winbuilder-3.3\kicad-winbuilder-3.3\src\kicad\common\kiway.cpp : KiFACE() : line 212

Revision history for this message
Evan Salazar (esalazar1981) wrote :

I updated to the latest winbuilder which does copy the _kiface files to the kicad bin. EESchema opens just fine however pcbnew and cvpcb give me no kiface errors even though I verified they are in the .bin folder. The lastest build I compiled is 4891

Revision history for this message
Brian Sidebotham (brian-sidebotham) wrote : Re: [Bug 1315945] Re: [4847] KiFACE Files Not Copied Into bin Directory

Hi Guys,

The kiface code changes are very intrusive and are a long way from
being finished as far as I can see. Before I roll a new release I need
to wait for the kiface changes to stabilise a bit. It's quite possible
the pcbnew and cvpcb kiface implementation is currently broken in the
KiCad code base.

If you want to try the latest trunk version of KiCad-Winbuilder, you
can download and replace the KiCad-Winbuilder.cmake file from here:

http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/download/brian.sidebotham%40gmail.com-20140507122315-ieonxxa03m32ly48/kicadmingw.cmake-20110418223824-3yr8y0u4nylkjh4c-1/KiCadWinbuilder.cmake

That at least includes the fix for copying the kiface files to the
kicad/bin folder.

Best Regards, Brian.

On 27 May 2014 21:16, Evan Salazar <email address hidden> wrote:
> I updated to the latest winbuilder which does copy the _kiface files to
> the kicad bin. EESchema opens just fine however pcbnew and cvpcb give me
> no kiface errors even though I verified they are in the .bin folder. The
> lastest build I compiled is 4891
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: winbuilder-bugs
> https://bugs.launchpad.net/bugs/1315945
>
> Title:
> [4847] KiFACE Files Not Copied Into bin Directory
>
> Status in KiCad Windows Builder:
> Fix Committed
>
> Bug description:
> I just built 4847 and I'm trying to run KiCAD via the RunKiCad.bat
> script. The Project Manager (KiCad.exe) loads fine, but trying to
> launch any other program (eeschema, PCBNew, etc) fails. Here's the
> failure from eeschema:
>
> 17:14:52: Failed to load shared library 'C:\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface' (error 0: the operation completed successfully.)
> 17:14:54: IO_ERROR: Fatal Installation Bug
> missing file:
> 'C:\kicad-winbuilder-3.3\kicad\bin\_eeschema.kiface'
>
> argv[0]:
> 'C:\kicad-winbuilder-3.3\kicad\bin\kicad.exe'
> from C:\kicad-winbuilder-3.3\src\kicad\common\kiway.cpp : KiFACE() : line 208
>
>
> Sure enough, that _eeschma.kiface file isn't there. Fortunately, a little bit of digging and I found it in another directory:
>
> C:\kicad-winbuilder-3.3\build\Release\eeschema\_eeschma.kiface
>
> If I copy that into 'C:\kicad-
> winbuilder-3.3\kicad\bin\_eeschema.kiface' then eeschema loads no
> problem. I'm not sure where the appropriate place to fix this issue
> is, if it's Windows specific or not, but I wanted to post my findings
> here so others don't get stuck on the same problem.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad-winbuilder/+bug/1315945/+subscriptions

Changed in kicad-winbuilder:
status: Fix Committed → Fix Released
Revision history for this message
Daniel Matthews (xdmattz) wrote :

Hi,

I built 4933 on a windows 7 64 bit machine, and 4938 on a windows XP 32 bit machine. Both seem to work OK on the machines that they were built on. (after getting the kiface files in the proper directory on 4938). But when I try to run a copy of the binaries on the other machine, not the machine that it was compiled on CvPCB and PCBnew both give the "kiface error" as described above. EEschema, GerbView BitMap etc all seem to work fine, just CvPCB and PCBnew.

The reason this is a problem for me is I'm trying to convince work to let me use KiCAD for prototype boards and I cannot compile the code there.

Hope this helps to find the real bug!

Thanks

Dan M.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.