Skip to content
This repository has been archived by the owner on Nov 30, 2019. It is now read-only.

cannot build #31

Open
Hardcore-fs opened this issue Feb 15, 2014 · 11 comments
Open

cannot build #31

Hardcore-fs opened this issue Feb 15, 2014 · 11 comments

Comments

@Hardcore-fs
Copy link

https://gist.github.com/Hardcore-fs/9027625

@gtdj
Copy link

gtdj commented Feb 16, 2014

I got error at the same line.

@ghost
Copy link

ghost commented Feb 17, 2014

I fixed this by commenting out the three lines in src\kicad\pcbnew\CMakeLists.txt that contain "osx_fix_bundles." This doesn't seems to cause any problems further on in the build process, but I do encounter a different issue.

@berkakinci
Copy link

This seems to be a combination of CMakeList oversight and build script oversight. I worked around it by making the following patch to the build script. I later had another problem (platform not supported from boost). May be one of you can get farther with the patch:

--- orig/build.sh   2014-02-17 16:53:00.000000000 -0500
+++ ./build.sh  2014-02-20 06:10:24.000000000 -0500
@@ -55,6 +55,10 @@
    echo ""
    echo "-C / --cern-branch : Selects the CERN branch, that includes push&shove router, GAL and new TOOL framework"
    echo ""
+   echo "-K / --stable-branch : Selects the kicad/stable branch for those who prefer to work WITH KiCad rather than ON it."
+   echo ""
+   echo "-m / --mrproper : Clean build products."
+   echo ""

    if [ "$1" != "" ]; then
        exit 1
@@ -104,6 +108,12 @@
        KICAD_DIRECTORY=cern-kicad
        ;;

+       # CERN Branch
+       -K | --stable-branch)
+       KICAD_BRANCH="lp:kicad/stable"
+       KICAD_DIRECTORY=kicad-stable
+       ;;
+
        # Print the help text
        -h | --help )
        print_usage
@@ -389,9 +399,33 @@
    done
    CMAKE_ARCHITECTURE_STRING=${CMAKE_ARCHITECTURE_STRING%;}

+   # See ./src/kicad/Documentation/compiling/mac-osx.txt
+   STEP_NAME="BUILD KICAD - swig"
+   STEP_NUMBER="5.1"
+   print_step_starting_message
+
+   cmake $SOURCE_DIRECTORY/$KICAD_DIRECTORY -DKICAD_BUILD_DYNAMIC=ON                                          \
+                                            -DCMAKE_CXX_FLAGS=-D__ASSERTMACROS__                              \
+                                                 -DCMAKE_ASM_FLAGS="${CMAKE_ASM_FLAGS}"                            \
+                                            -DCMAKE_INSTALL_PREFIX=$PREFIX_DIRECTORY                          \
+                                            -DCMAKE_FIND_FRAMEWORK=LAST                                       \
+                                            -DwxWidgets_CONFIG_EXECUTABLE=$PREFIX_DIRECTORY/bin/wx-config     \
+                                            -DPYTHON_EXECUTABLE=`which python`                                \
+                                            -DPYTHON_SITE_PACKAGE_PATH=$PREFIX_DIRECTORY/python/site-packages \
+                                            -DPYTHON_PACKAGES_PATH=$PREFIX_DIRECTORY/python/site-packages     \
+                                            -DCMAKE_OSX_ARCHITECTURES="${CMAKE_ARCHITECTURE_STRING}"          \
+                                            -DCMAKE_BUILD_TYPE=$BUILD_TYPE
+   make $MAKE_THREAD_COUNT swig || exit_on_build_error
+
+   # Original build with KICAD_BUILD_DYNAMIC=ON against the missing osx_fix_bundles target.
+   STEP_NAME="BUILD KICAD - KiCad"
+   STEP_NUMBER="5.2"
+   print_step_starting_message
+
    cmake $SOURCE_DIRECTORY/$KICAD_DIRECTORY -DKICAD_SCRIPTING=ON                                              \
                                             -DKICAD_SCRIPTING_MODULES=ON                                      \
                                             -DKICAD_SCRIPTING_WXPYTHON=ON                                     \
+                                            -DKICAD_BUILD_DYNAMIC=ON                                          \
                                             -DCMAKE_CXX_FLAGS=-D__ASSERTMACROS__                              \
                                                  -DCMAKE_ASM_FLAGS="${CMAKE_ASM_FLAGS}"                            \
                                             -DCMAKE_INSTALL_PREFIX=$PREFIX_DIRECTORY                          \

@aspdigital
Copy link

This bug still exists. I'm not sure why it can't be fixed. I'd do it myself but I'm not enough of a programmer.

@berkakinci
Copy link

I think the underlying CMake problem appears fixed:
http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741
I haven't tried it yet; I'm not likely to try this any more. I'm still trying to get my pre-built binary from mdx4.org running so that I can get to work!

@adamwolf
Copy link

Hi folks,

I've got builds going nightly, and am working with Miguel to get them
pushed to the Kicad webpage. I also have a new build script. The Kicad
devs changed how Mac builds are created--that's why this doesn't even get
close to working anymore. I don't get to do much Kicad work during the
workweek, however. For now, feel free to try the package located at

https://www.dropbox.com/s/1t1vwiwvqb6wh1h/kicad-r4730.20140303-155100.dmg.
It's about 215 megabytes.
Adam Wolf
Wayne and Layne, LLC

On Tue, Mar 11, 2014 at 4:03 AM, berkakinci [email protected]:

I think the underlying CMake problem appears fixed:

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741
I haven't tried it yet; I'm not likely to try this any more. I'm still
trying to get my pre-built binary from mdx4.org running so that I can get
to work!

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-37274934
.

@guymadison
Copy link

KiCad needs a staging branch or developers need to be more careful with their checkins. The build breaks so often on OS X its silly.

Guy

On Mar 11, 2014, at 9:08 AM, Adam Wolf [email protected] wrote:

Hi folks,

I've got builds going nightly, and am working with Miguel to get them
pushed to the Kicad webpage. I also have a new build script. The Kicad
devs changed how Mac builds are created--that's why this doesn't even get
close to working anymore. I don't get to do much Kicad work during the
workweek, however. For now, feel free to try the package located at

https://www.dropbox.com/s/1t1vwiwvqb6wh1h/kicad-r4730.20140303-155100.dmg.
It's about 215 megabytes.
Adam Wolf
Wayne and Layne, LLC

On Tue, Mar 11, 2014 at 4:03 AM, berkakinci [email protected]:

I think the underlying CMake problem appears fixed:

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741
I haven't tried it yet; I'm not likely to try this any more. I'm still
trying to get my pre-built binary from mdx4.org running so that I can get
to work!

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-37274934
.


Reply to this email directly or view it on GitHub.

@adamwolf
Copy link

I'm not a developer. I just package Kicad. There was a recent change where
they tried to create a branch that is sort of stable, but previously, the
"stable" branch was only updated every 18+ months or so.

This meant that packagers could either package stable, which was 18 months
out of date, or master, which breaks on various platforms all the time.

Miguel and I both have jenkins systems setup, and we're both trying to get
automated testing done.

Adam Wolf

On Tue, Mar 11, 2014 at 11:12 AM, guymadison [email protected]:

KiCad needs a staging branch or developers need to be more careful with
their checkins. The build breaks so often on OS X its silly.

Guy

On Mar 11, 2014, at 9:08 AM, Adam Wolf [email protected] wrote:

Hi folks,

I've got builds going nightly, and am working with Miguel to get them
pushed to the Kicad webpage. I also have a new build script. The Kicad
devs changed how Mac builds are created--that's why this doesn't even
get
close to working anymore. I don't get to do much Kicad work during the
workweek, however. For now, feel free to try the package located at

https://www.dropbox.com/s/1t1vwiwvqb6wh1h/kicad-r4730.20140303-155100.dmg.

It's about 215 megabytes.
Adam Wolf
Wayne and Layne, LLC

On Tue, Mar 11, 2014 at 4:03 AM, berkakinci [email protected]:

I think the underlying CMake problem appears fixed:

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741
I haven't tried it yet; I'm not likely to try this any more. I'm still
trying to get my pre-built binary from mdx4.org running so that I can
get
to work!

Reply to this email directly or view it on GitHub<
https://github.com/KiCad/KicadOSXBuilder/issues/31#issuecomment-37274934>
.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-37314338
.

@adamwolf
Copy link

Similarly, it's hard to be a packager for Kicad. Some of the issues on
this project are just full of vitriol!

When people attack a volunteer for working hard to give the world something
for free, most volunteers decide to leave.

On Tue, Mar 11, 2014 at 11:16 AM, Adam Wolf
[email protected]:

I'm not a developer. I just package Kicad. There was a recent change
where they tried to create a branch that is sort of stable, but previously,
the "stable" branch was only updated every 18+ months or so.

This meant that packagers could either package stable, which was 18 months
out of date, or master, which breaks on various platforms all the time.

Miguel and I both have jenkins systems setup, and we're both trying to get
automated testing done.

Adam Wolf

On Tue, Mar 11, 2014 at 11:12 AM, guymadison [email protected]:

KiCad needs a staging branch or developers need to be more careful with
their checkins. The build breaks so often on OS X its silly.

Guy

On Mar 11, 2014, at 9:08 AM, Adam Wolf [email protected] wrote:

Hi folks,

I've got builds going nightly, and am working with Miguel to get them
pushed to the Kicad webpage. I also have a new build script. The Kicad
devs changed how Mac builds are created--that's why this doesn't even
get
close to working anymore. I don't get to do much Kicad work during the
workweek, however. For now, feel free to try the package located at

https://www.dropbox.com/s/1t1vwiwvqb6wh1h/kicad-r4730.20140303-155100.dmg.

It's about 215 megabytes.
Adam Wolf
Wayne and Layne, LLC

On Tue, Mar 11, 2014 at 4:03 AM, berkakinci [email protected]:

I think the underlying CMake problem appears fixed:

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741
I haven't tried it yet; I'm not likely to try this any more. I'm
still
trying to get my pre-built binary from mdx4.org running so that I
can get
to work!

Reply to this email directly or view it on GitHub<
https://github.com/KiCad/KicadOSXBuilder/issues/31#issuecomment-37274934>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-37314338
.

@guymadison
Copy link

Oh I understand... but I also understand what its like to have a team of 70 developers flame you because you broke the build and they didn't want to work late to get their work checked in.

In general I hate too much process, I know I am careful about check-ins but I have found out that others aren't so careful. So if you have influence in the process I would recommend some process changes.

This all came about the other day, after a month I noticed the build had been fixed so I downloaded the build and it failed to build again... so I threw my hands up.

I worked at Apple for 10 years... The real way to package dependent libraries is in the .app frameworks directory and link them directly with the build rather than depending on external libraries to exist. If you need external libraries the installer should put them in place, then not rely on mac ports which has its own set of issues.

Just my two cents.

Guy

On Mar 11, 2014, at 9:17 AM, Adam Wolf [email protected] wrote:

Similarly, it's hard to be a packager for Kicad. Some of the issues on
this project are just full of vitriol!

When people attack a volunteer for working hard to give the world something
for free, most volunteers decide to leave.

On Tue, Mar 11, 2014 at 11:16 AM, Adam Wolf
[email protected]:

I'm not a developer. I just package Kicad. There was a recent change
where they tried to create a branch that is sort of stable, but previously,
the "stable" branch was only updated every 18+ months or so.

This meant that packagers could either package stable, which was 18 months
out of date, or master, which breaks on various platforms all the time.

Miguel and I both have jenkins systems setup, and we're both trying to get
automated testing done.

Adam Wolf

On Tue, Mar 11, 2014 at 11:12 AM, guymadison [email protected]:

KiCad needs a staging branch or developers need to be more careful with
their checkins. The build breaks so often on OS X its silly.

Guy

On Mar 11, 2014, at 9:08 AM, Adam Wolf [email protected] wrote:

Hi folks,

I've got builds going nightly, and am working with Miguel to get them
pushed to the Kicad webpage. I also have a new build script. The Kicad
devs changed how Mac builds are created--that's why this doesn't even
get
close to working anymore. I don't get to do much Kicad work during the
workweek, however. For now, feel free to try the package located at

https://www.dropbox.com/s/1t1vwiwvqb6wh1h/kicad-r4730.20140303-155100.dmg.

It's about 215 megabytes.
Adam Wolf
Wayne and Layne, LLC

On Tue, Mar 11, 2014 at 4:03 AM, berkakinci [email protected]:

I think the underlying CMake problem appears fixed:

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741
I haven't tried it yet; I'm not likely to try this any more. I'm
still
trying to get my pre-built binary from mdx4.org running so that I
can get
to work!

Reply to this email directly or view it on GitHub<
https://github.com/KiCad/KicadOSXBuilder/issues/31#issuecomment-37274934>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-37314338
.


Reply to this email directly or view it on GitHub.

@adamwolf
Copy link

Please take a look at that .dmg I uploaded. Each .app is independent of
each other, and each is independent of build dependencies.

On Tue, Mar 11, 2014 at 11:26 AM, guymadison [email protected]:

Oh I understand... but I also understand what its like to have a team of
70 developers flame you because you broke the build and they didn't want to
work late to get their work checked in.

In general I hate too much process, I know I am careful about check-ins
but I have found out that others aren't so careful. So if you have
influence in the process I would recommend some process changes.

This all came about the other day, after a month I noticed the build had
been fixed so I downloaded the build and it failed to build again... so I
threw my hands up.

I worked at Apple for 10 years... The real way to package dependent
libraries is in the .app frameworks directory and link them directly with
the build rather than depending on external libraries to exist. If you need
external libraries the installer should put them in place, then not rely on
mac ports which has its own set of issues.

Just my two cents.

Guy

On Mar 11, 2014, at 9:17 AM, Adam Wolf [email protected] wrote:

Similarly, it's hard to be a packager for Kicad. Some of the issues on
this project are just full of vitriol!

When people attack a volunteer for working hard to give the world
something
for free, most volunteers decide to leave.

On Tue, Mar 11, 2014 at 11:16 AM, Adam Wolf
[email protected]:

I'm not a developer. I just package Kicad. There was a recent change
where they tried to create a branch that is sort of stable, but
previously,
the "stable" branch was only updated every 18+ months or so.

This meant that packagers could either package stable, which was 18
months
out of date, or master, which breaks on various platforms all the
time.

Miguel and I both have jenkins systems setup, and we're both trying to
get
automated testing done.

Adam Wolf

On Tue, Mar 11, 2014 at 11:12 AM, guymadison [email protected]:

KiCad needs a staging branch or developers need to be more careful
with
their checkins. The build breaks so often on OS X its silly.

Guy

On Mar 11, 2014, at 9:08 AM, Adam Wolf [email protected]
wrote:

Hi folks,

I've got builds going nightly, and am working with Miguel to get
them
pushed to the Kicad webpage. I also have a new build script. The
Kicad
devs changed how Mac builds are created--that's why this doesn't
even
get
close to working anymore. I don't get to do much Kicad work during
the
workweek, however. For now, feel free to try the package located at

https://www.dropbox.com/s/1t1vwiwvqb6wh1h/kicad-r4730.20140303-155100.dmg.

It's about 215 megabytes.
Adam Wolf
Wayne and Layne, LLC

On Tue, Mar 11, 2014 at 4:03 AM, berkakinci <
[email protected]>wrote:

I think the underlying CMake problem appears fixed:

http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/revision/4741

I haven't tried it yet; I'm not likely to try this any more. I'm
still
trying to get my pre-built binary from mdx4.org running so that
I
can get
to work!

Reply to this email directly or view it on GitHub<

https://github.com/KiCad/KicadOSXBuilder/issues/31#issuecomment-37274934>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub<
https://github.com/KiCad/KicadOSXBuilder/issues/31#issuecomment-37314338>
.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-37316178
.

@notthetup
Copy link

@adamwolf Do you still pack OSX builds? Is there anywhere I can find newer builds than the one you linked above?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants