Opened 10 years ago
Closed 10 years ago
#44042 closed submission (fixed)
oce @0.15 - new port
Reported by: | mbrethen | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.0 |
Keywords: | Cc: | ||
Port: | oce |
Description
Currently, the easiest way to build OpenCASCADE on OS X is from the community edition (oce). I'm attaching a proposed Portfile for oce=0.15. OCE has the same license as OCCT; since OCCT 6.7.0, you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License version 2.1.
Here are default flags on OS X
OCE_BUILD_SHARED_LIB ON
OCE_BUILD_TYPE Release
OCE_DATAEXCHANGE ON
OCE_DRAW OFF
OCE_INSTALL_PREFIX /opt/local
OCE_MODEL ON
OCE_MULTITHREAD_LIBRARY NONE
OCE_OCAF ON
OCE_VISUALISATION ON
OCE_WITH_FREEIMAGE OFF
OCE_WITH_GL2PS OFF
In order to build DRAWEXE, one can add the 'draw' variant: 'sudo port install +draw'
OCE can be compiled with TBB in order to support parallel meshing. Enable it with: 'sudo port install +tbb'
There are additional variants, see Portfile for a full list.
The Draw Test Harness provides a flexible and easy-to-use means of testing and demonstrating the CAS.CADE modeling libraries. See $PREFIX/share/oce-0.15/src/DrawResources/DRAW.doc.
Attachments (1)
Change History (9)
comment:1 Changed 10 years ago by mbrethen
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Only thing that immediately jumps out at me in the portfile is that you don't need to use destroot.keepdirs
for any directory into which you're going to install anything.
comment:3 follow-up: 5 Changed 10 years ago by mbrethen
Isn't ${destroot}${frameworks_dir} removed after completing the destroot phase, or is post-destroot considered part of the destroot phase? Unless I completly misunderstood the documentation:
"Any empty directories in ${destroot} upon completion of the destroot phase are removed unless a directory name is placed in the value field of the optional destroot.keepdirs keyword."
comment:4 follow-up: 6 Changed 10 years ago by mbrethen
If I understand what your meaning, it works like the 'mv' command?
mv uses cp(1) and rm(1) to accomplish the move. The effect is equivalent to: rm -f destination_path && \ cp -pRP source_file destination && \ rm -rf source_file
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to mark.brethen@…:
Isn't ${destroot}${frameworks_dir} removed after completing the destroot phase, or is post-destroot considered part of the destroot phase? Unless I completly misunderstood the documentation:
"Any empty directories in ${destroot} upon completion of the destroot phase are removed unless a directory name is placed in the value field of the optional destroot.keepdirs keyword."
The post-X procs are considered part of the X phase.
comment:6 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to mark.brethen@…:
'file rename' must work similar to the 'mv' command:
Yes, and in MacPorts, you may as well use our alias move
instead of the more verbose file rename
.
comment:7 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Status: | new → assigned |
comment:8 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Committed in r122275 with some changes (mostly just whitespace/formatting changes).
This was on a mbp running mavericks (10.9.3).