Package Details: brlcad 7.36.0-1

Git Clone URL: https://aur.archlinux.org/brlcad.git (read-only, click to copy)
Package Base: brlcad
Description: Extensive 3D solid modeling system
Upstream URL: https://brlcad.org
Keywords: 3d c c++ CAD python tcl
Licenses: BSD-3-Clause, LGPL-2.1-only, LicenseRef-BDL
Submitter: louipc
Maintainer: None
Last Packager: adamperkowski
Votes: 68
Popularity: 0.60
First Submitted: 2007-02-04 02:47 (UTC)
Last Updated: 2024-12-29 21:26 (UTC)

Pinned Comments

envolution commented on 2024-11-18 06:43 (UTC)

I'm not having much luck getting the latest version compiled as per the issue github issue I posted earlier. Hopefully someone more capable can figure this out - if not I'll try again when I have more time

I'll keep brlcad-bin up to date in the meantime - if anyone wants to pick up where I left off you can find the WIP at https://github.com/envolution/aur/tree/main/nomaintain/nobuild/brlcad

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

ejno commented on 2016-06-02 00:27 (UTC)

@gjw: Thanks, should be fixed now.

gjw commented on 2016-05-27 16:58 (UTC)

It does not build any more. It stops at 44 percentage. It seems to me that some functions in the boost libraries have been removed and put into g++ instead.

lenzj commented on 2015-12-13 14:11 (UTC)

@ejno: It compiles and works well now. Thanks again.

ejno commented on 2015-12-13 05:44 (UTC)

@lenzj: Thanks, should be fixed now.

lenzj commented on 2015-12-12 12:40 (UTC)

I'm getting the following error during compile: /tmp/pacaurtmp-/brlcad/src/brlcad-7.24.2/src/other/boost/boost/xpressive/detail/static/transmogrify.hpp:42:46: error: no type named ‘string_type’ in ‘struct boost::xpressive::cpp_regex_traits<char>’ typedef typename Traits::string_type string_type;

ejno commented on 2015-03-12 12:59 (UTC)

@lenzj: Great, thanks for confirming!

lenzj commented on 2015-03-12 12:28 (UTC)

@finale: I've confirmed that it's compiling successfully for me now. Thank you!

ejno commented on 2015-03-12 06:32 (UTC)

@lenzj: Should be fixed now.

ejno commented on 2015-03-08 03:47 (UTC)

@lenzj: Thanks for reporting, I will investigate the issue.