Re: [oce-dev] OCE compiling on MacOS

48 views
Skip to first unread message

jelle feringa

unread,
Apr 29, 2013, 5:28:05 PM4/29/13
to oce...@googlegroups.com
Hi Greg,

I'm pretty sure Thomas did not write this tutorial, and I fully agree with you, messing with the symbolic links is a very poor idea at best.
Also, given macports recent move to distributing binaries puts it ahead of the pack.
Yes, having a macports binary would be _very__ welcome, since distributing those on linux and windows is well accommodated.
Would you be willing to investigate / lead that effort?
It would be a wonderful step ahead indeed!

Cheers,

-jelle




On Mon, Apr 29, 2013 at 8:02 PM, Greg Allen <gal...@arlut.utexas.edu> wrote:
I'm building the head [https://github.com/tpaviot/oce.git] on an up-to-date Mac system [10.8.3].

The directions in the wiki [https://github.com/tpaviot/oce/wiki/Build-%28Mac-OSX%29] tell you to modify your system by adding a symlink from X11 into /usr/local. I respectfully suggest that's a bad idea, and that OCE should work without modifying the system.

All that's missing for CMake to find the X11 includes is:

INCLUDE_DIRECTORIES(${X11_INCLUDE_DIR})

It could go in a number of places, all the way up to the top CMakeLists.txt (after FIND_PACKAGE X11)

The patch below is where I decided to put it. Please add it where you deem appropriate. (I'll test on my X11-symlink-free McSystem.)

I'd like to see pythonocc be included in MacPorts. This is an early step toward that goal.

Thanks,
-Greg

diff --git a/adm/cmake/BuildToolkit.cmake b/adm/cmake/BuildToolkit.cmake
index 3327d08..ecacd1f 100644
--- a/adm/cmake/BuildToolkit.cmake
+++ b/adm/cmake/BuildToolkit.cmake
@@ -161,6 +161,8 @@ FOREACH(MODULE ${TOOLKIT_MODULES})
        IF (WIN32)
                # For compilers under Windows a define must be set per file to c
                ADD_DEFINITIONS("-D__${MODULE}_DLL")
+       ELSE(WIN32)
+               INCLUDE_DIRECTORIES(${X11_INCLUDE_DIR})
        ENDIF(WIN32)
 
        SOURCE_GROUP (${MODULE} FILES ${source_files})

--
You received this message because you are subscribed to the Google Groups "oce-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to oce-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Thomas Paviot

unread,
Apr 30, 2013, 2:53:31 AM4/30/13
to oce...@googlegroups.com
2013/4/29 Greg Allen <gal...@arlut.utexas.edu>
I'm building the head [https://github.com/tpaviot/oce.git] on an up-to-date Mac system [10.8.3].

The directions in the wiki [https://github.com/tpaviot/oce/wiki/Build-%28Mac-OSX%29] tell you to modify your system by adding a symlink from X11 into /usr/local. I respectfully suggest that's a bad idea, and that OCE should work without modifying the system.

All that's missing for CMake to find the X11 includes is:

INCLUDE_DIRECTORIES(${X11_INCLUDE_DIR})

It could go in a number of places, all the way up to the top CMakeLists.txt (after FIND_PACKAGE X11)

The patch below is where I decided to put it. Please add it where you deem appropriate. (I'll test on my X11-symlink-free McSystem.)

I'd like to see pythonocc be included in MacPorts. This is an early step toward that goal.

Thanks,
-Greg

diff --git a/adm/cmake/BuildToolkit.cmake b/adm/cmake/BuildToolkit.cmake
index 3327d08..ecacd1f 100644
--- a/adm/cmake/BuildToolkit.cmake
+++ b/adm/cmake/BuildToolkit.cmake
@@ -161,6 +161,8 @@ FOREACH(MODULE ${TOOLKIT_MODULES})
        IF (WIN32)
                # For compilers under Windows a define must be set per file to c
                ADD_DEFINITIONS("-D__${MODULE}_DLL")
+       ELSE(WIN32)
+               INCLUDE_DIRECTORIES(${X11_INCLUDE_DIR})
        ENDIF(WIN32)
 
        SOURCE_GROUP (${MODULE} FILES ${source_files})


Hi Greg,

The OSX wiki page is outdated. There's no need for any symbolic links to build/use OCE.

Thank you for your report and your patch, however you should check the branch review/OCCT660 which is under review and will soon be merged into master.

Regars,

Thomas 

jelle feringa

unread,
Apr 30, 2013, 4:15:12 AM4/30/13
to Greg Allen, oce...@googlegroups.com
Hi Greg,

I'm fairly familiar with MacPorts, and think I could contribute "ports" such that someone could type...

That would be absolutely *amazing*
 
$ sudo port install py27-pythonocc

Could you consider making OCE a dependency of py27-pythonocc?
This way the macports efforts also of interest to non-pythonista's.
 
... to compile and install pythonocc and its dependencies.

( I guess we agree )
 
I've never used the binaries feature, but suspect that's not much effort once MacPorts can compile the packages. [I didn't think binaries were new.]

I think the novelty is that installing binaries become normative only recently.
 
I'm willing to continue to investigate MacPorts-ifying OCE/pyocc in my "free time". :)

That effort would be much anticipated Greg, thanks _so_ much looking into that!

-jelle
Reply all
Reply to author
Forward
0 new messages