kicad-developers team mailing list archive

[Michael Narigon <mnarigon@xxxxxxxxx>]

Gents,
It probably landed in your spam filter (half the e-mails from the developers list do to me) but I sent a message that I am pretty far along on what you are discussing. See the tar file at https://code.launchpad.net/~mnarigon.

I used the good work you guys had and cleaned it up. I used the kicad-build.sh concept of the build steps (and KiCadOSXBuilder) and separated out the KiCad build process into a number of steps that can be selectively executed. For those platforms where the dependencies exist I take advantage of them.

The steps are roughly check the environment, check for pre-requisites, build tools, build dependent libraries, pull source from the repository, build, install, and package.

The scripts are alpha but the steps I have completed are pretty robust. I am still working on the install and packaging steps, debug builds do not work, and I have not yet worked on windows other than to check the cygwin dependencies although I intend these script to fully support Windows.

Currently, I can build KiCad on OS X and Linux. I am currently focussed on getting a drag and drop install working on OS X.

In the tar there is the top-level build script called build.sh. Read this to understand what is going on, and try it out by running it.

I intend this to work on OS X, Linux (debian and Redhat) and Windows.

Michael

On Aug 20, 2014, at 11:53 AM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:

> On 08/20/2014 11:45 AM, Wayne Stambaugh wrote:
>> On 8/19/2014 5:17 PM, Dick Hollenbeck wrote:
>>> On 08/19/2014 03:37 PM, Wayne Stambaugh wrote:
>>>> On 8/19/2014 4:17 PM, Dick Hollenbeck wrote:
>>>>> On 08/18/2014 06:47 PM, Wayne Stambaugh wrote:
>>>>>> On 8/18/2014 6:45 PM, Brian Sidebotham wrote:
>>>>>>> On 16 August 2014 17:44, Wayne Stambaugh <stambaughw@xxxxxxxxxxx> wrote:
>>>>>>>> One of the tasks that I have committed to working on in the KiCad road
>>>>>>>> map is to clean up the current mess we have created by allowing
>>>>>>>> dependency libraries to be built as part of the KiCad source build.  The
>>>>>>>> only exception I see for the time being is Boost.  Although I am have my
>>>>>>>> reservations on that as well.  Why you ask?  I've spent several days
>>>>>>>> trying to get KiCad to build on Windows using MSYS2 as my build
>>>>>>>> environment and mingw64 as my target environment.  Every single library
>>>>>>>> dependency with the exception of our custom Boost and avhttp (which
>>>>>>>> could easily be build and installed using CMake) are already packaged
>>>>>>>> for me.  However, the current KiCad build insists on downloading and
>>>>>>>> building some libraries from source that are already installed.  This is
>>>>>>>> silly.  I can resolve the issues by passing all of the
>>>>>>>> PACKAGE_ROOT_PATHs when I run CMake but that is silly as well since my
>>>>>>>> build environment already points the correct path.
>>>>>>>>