-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails on Sierra #33
Comments
Hi Jim, thanks for reporting this issue. I haven't tried to build on Sierra yet but I will to see if I can reproduce the issue. There is an open nglib build issue #26, where I was not able to build on El Capitan and it is possible that it is the same issue perhaps manifested slightly differently which may give insight into the root cause. In the mean time, you can grab builds from our FreeCAD releases on GitHub |
@jimhigson, here's another quick follow-up; My test failed out of the gate on macOS Sierra because QT is not supported on macOS > 10.11. How did you get around that issue?
|
To my knowledge I didn't do anything to get around that. Maybe it found an old install from before I upgraded to Sierra? Let me know if I can provide any information that would help here. Thanks for the links to the snapshot builds - I didn't know those existed. |
Further to gift's forum post, you can install qt4 using cartr's qt4 port. I have reproduced this issue on Sierra and it is the same nglib issue #26 that occurs on El Capitan. |
Is there any workaround for building on Sierra? |
Hi Jim, I believe @ianrrees has already fixed the nglib issue that prevented builds on Sierra but neither of us has had a chance to back-port the changes to the OCCT7 nglib formula. Unfortunately I am traveling in Indonesia through January 7th with very limited access... If you are up for it, you can clone this repo and back-port ian's changes to the nglib formula - I believe it will work. Details are here https://github.com/Homebrew/homebrew-science/issues/3624 and here #26. Also, the continuous integration builds available under the FreeCAD GitHub releases page will run on Sierra. |
Hi @jimhigson, sorry I've been super busy with work stuff lately as Bruce mentioned. I believe the nglib in the Homebrew main line will build for you, but I don't actually have a Sierra machine to work on. If you could test it and report back, that would be great! As has been discussed on another thread, I think the ideal solution is to get the changes we need in to the main Homebrew recipe (or we could get rid of that one - I added it initially to support FreeCAD on Mac) so that we're not trying to maintain two copies of essentially the same thing. |
This is what I get now: I've previously done
|
Hi Jim, Could you try instead to "brew install homebrew/science/nglib" and see what happens? I'm not sure whether the current FreeCAD Homebrew recipe will be happy with that nglib recipe, but am interested in whether that nglib can be built on Sierra. Sorry, I misspoke earlier - the nglib isn't in the homebrew main line as such, but is in homebrew-science. You'll probably have already "tapped" homebrew-science, but if not you'll get an error above, and can then "brew tap homebrew/science". |
@ianrrees - unfortunately very similar:
|
Hmm, that's a bummer. I'm heading to the hills for a few days, but will try to get back on this in the next week or two. Thanks for testing! |
@ianrrees, @bblacey, I recently upgraded to Sierra. Your fix in homebrew/science does resolve the above error . The reason @jimhigson is still getting it is because the freecad recipe still specifies the nglib recipe from homebrew-freecad. However, am I missing something? The opencascade include path is not correct for homebrew occt 7 (it was looking for headers in opencascade/inc) and after I corrected that it fails because Handle_BRepAlgo_AsDes.hxx does not exist. |
Ah, after reading a litter more of these issues am I correct in thinking that the recipe in science doesn't support occt7, only the one in this repo? I applied @ianrrees patch to hombrew-freecad/nglib and it built fine. |
Hi @peterl94, I was in Indonesia for the past 3 weeks during much of which I didn't have Internet access and am just catching up. I noticed the occ paths were incorrect in #26 (comment). Neither Ian nor I have had a chance to update the nglib formula here with Ian's latest patch. You are also a contributor on this repo so feel free to provide an update if you have time - hint, hint ;) |
I now get a different failure. Not sure if this is the same issue as #26
|
Jim, I haven't really run out the build from head yet so could you try the following:
The advantage of first installing the dependencies and then building within your own repo is that ccache will be installed so future re-compiles will be faster. On the other hand, the formula will always download a new set of source from GitHub into a clean directory and recompile everything. Once you have the dependencies installed and your own FreeCAD repo clone, you can use Looking forward to hearing your results. |
@bblacey - thanks for the script. Am building now - let's see where this gets. |
Guessing you didn't mean
I guess that means that the dependencies didn't install properly. At this point I'm not sure I want to continue - my decision to use brew to install software was mostly so that I can just install things - I'm not very experienced with building C programs and at this point I think it makes more sense to put up with an old version of Freecad than to keep trying to build it. |
Hi Jim, you do want to cd to build and then append .. to the cmake command. Sorry for the error in the cmake command. Let me how how it works out. If it doesn't work, try another git clone of FreeCAD because I am not sure what running cmake in the root might have done to your instance. |
Ok, I did |
Hmmm, did you run Also, please provide the output of |
Jim, also, if you want to run the latest and greatest builds, they are available at https://github.com/FreeCAD/FreeCAD/releases/tag/0.17_pre. The macOS build is automatically built, tested and uploaded each time a PR is merged into master. You can refer to the SHA on the file name or in the about box to understand the changes since the last build you downloaded. |
With a fully updated brew on Sierra I get this:
The text was updated successfully, but these errors were encountered: