Author Topic: Building KiCAD for Windows  (Read 31315 times)

0 Members and 1 Guest are viewing this topic.

Offline HackedFridgeMagnet

  • Super Contributor
  • ***
  • Posts: 1931
  • Country: au
Re: Building KiCAD for Windows
« Reply #50 on: April 11, 2014, 08:42:22 am »
When I build this it feels like I am bitcoin mining.
Will I find one?  :)
 

Offline carloscuev

  • Regular Contributor
  • *
  • Posts: 122
  • Country: mx
    • Spanish Freescale Developers Forum
Re: Building KiCAD for Windows
« Reply #51 on: April 11, 2014, 08:44:13 am »
When I build this it feels like I am bitcoin mining.
Will I find one?  :)

 :-DD
 

Offline HackedFridgeMagnet

  • Super Contributor
  • ***
  • Posts: 1931
  • Country: au
Re: Building KiCAD for Windows
« Reply #52 on: April 11, 2014, 10:41:43 am »
Built ok, but where do I get these Kiface files?
Any info on what they are do?
I can see something in the commit log. But it doesn't make much sense to me.

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4757
Quote
    Committer: Dick Hollenbeck
    Date: 2014-03-20 06:47:30 UTC
    mfrom: (4658.1.2 kiway-merge)
    Revision ID: dick@softplc.com-20140320064730-vj8xkej8lgn29et0

*   KIWAY Milestone A): Make major modules into DLL/DSOs.

!   The initial testing of this commit should be done using a Debug build so that
    all the wxASSERT()s are enabled.  Also, be sure and keep enabled the
    USE_KIWAY_DLLs option.  The tree won't likely build without it.  Turning it
    off is senseless anyways.  If you want stable code, go back to a prior version,
    the one tagged with "stable".

*   Relocate all functionality out of the wxApp derivative into more finely
    targeted purposes:
    a) DLL/DSO specific
    b) PROJECT specific
    c) EXE or process specific
    d) configuration file specific data
    e) configuration file manipulations functions.

    All of this functionality was blended into an extremely large wxApp derivative
    and that was incompatible with the desire to support multiple concurrently
    loaded DLL/DSO's ("KIFACE")s and multiple concurrently open projects.
    An amazing amount of organization come from simply sorting each bit of
    functionality into the proper box.

*   Switch to wxConfigBase from wxConfig everywhere except instantiation.
*   Add classes KIWAY, KIFACE, KIFACE_I, SEARCH_STACK, PGM_BASE, PGM_KICAD,
    PGM_SINGLE_TOP,
*   Remove "Return" prefix on many function names.
*   Remove obvious comments from CMakeLists.txt files, and from else() and endif()s.
*   Fix building boost for use in a DSO on linux.
*   Remove some of the assumptions in the CMakeLists.txt files that windows had
    to be the host platform when building windows binaries.
*   Reduce the number of wxStrings being constructed at program load time via
    static construction.
*   Pass wxConfigBase* to all SaveSettings() and LoadSettings() functions so that
    these functions are useful even when the wxConfigBase comes from another
    source, as is the case in the KICAD_MANAGER_FRAME.
*   Move the setting of the KIPRJMOD environment variable into class PROJECT,
    so that it can be moved into a project variable soon, and out of FP_LIB_TABLE.
*   Add the KIWAY_PLAYER which is associated with a particular PROJECT, and all
    its child wxFrames and wxDialogs now have a Kiway() member function which
    returns a KIWAY& that that window tree branch is in support of.  This is like
    wxWindows DNA in that child windows get this member with proper value at time
    of construction.
*   Anticipate some of the needs for milestones B) and C) and make code
    adjustments now in an effort to reduce work in those milestones.
*   No testing has been done for python scripting, since milestone C) has that
    being largely reworked and re-thought-out.
 

Offline carloscuev

  • Regular Contributor
  • *
  • Posts: 122
  • Country: mx
    • Spanish Freescale Developers Forum
Re: Building KiCAD for Windows
« Reply #53 on: April 11, 2014, 11:09:36 am »
You can find them here:
"kicad-winbuilder-3.3\build\Release\cvpcb\_cvpcb.kiface"
"kicad-winbuilder-3.3\build\Release\eeschema\_eeschema.kiface"
"kicad-winbuilder-3.3\build\Release\gerbview\_gerbview.kiface"
"kicad-winbuilder-3.3\build\Release\pcb_calculator\_pcb_calculator.kiface"
"kicad-winbuilder-3.3\build\Release\pcbnew\_pcbnew.kiface"
"kicad-winbuilder-3.3\build\Release\pagelayout_editor\_pl_editor.kiface"

Reading that revision description you posted I'll enable USE_KIWAY_DLLS option and rebuild, wish me luck!

No concrete idea about what they are for :(
« Last Edit: April 11, 2014, 11:12:30 am by carloscuev »
 

Offline HackedFridgeMagnet

  • Super Contributor
  • ***
  • Posts: 1931
  • Country: au
Re: Building KiCAD for Windows
« Reply #54 on: April 11, 2014, 11:48:15 am »
After I manually copied the .kiface files eeschema and pcbnew both ran, I could place components. So looking good.

Although Kicad.exe crashed so still bugs on this build.

from About:

Application: kicad
Version: (2014-04-10 BZR 4796)-product Release build
wxWidgets: Version 3.0.0 (debug,wchar_t,compiler with C++ ABI 1002,GCC 4.8.1,wx containers,compatible with 2.8)
Platform: Windows NT 6.2 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Boost version: 1.54.0
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON


 

Offline firewalker

  • Super Contributor
  • ***
  • Posts: 2321
  • Country: gr
Re: Building KiCAD for Windows
« Reply #55 on: April 11, 2014, 04:28:14 pm »
Carlos, how do you packet you binary? E.g. in bin.4740 I don't see any bat files for settings paths etc.

Alexander.
Become a realist, stay a dreamer.

 

Offline firewalker

  • Super Contributor
  • ***
  • Posts: 2321
  • Country: gr
Re: Building KiCAD for Windows
« Reply #56 on: April 11, 2014, 04:31:29 pm »
I also will try a statically linked binary (scripting disabled).

Alexander.
Become a realist, stay a dreamer.

 

Offline firewalker

  • Super Contributor
  • ***
  • Posts: 2321
  • Country: gr
Re: Building KiCAD for Windows
« Reply #57 on: April 11, 2014, 09:16:33 pm »
Nope, built from scratch and the problem persists

You should copy all the dlls found on "mingw32\bin" folder to you bin directory. I tried you build and had the same error. After copying the dlls, everything seems fine.

Alexander.
Become a realist, stay a dreamer.

 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf