Hello,

I created a ppa with a oce-0.6.0 package . Now I'm going to start
building a pythonocc package using this ppa. So - in order to build a
current pythonocc package based on oce-0.6.0: which tag should I use?
Is pythonocc-0.5 still the best choice?
Should I just use latest master?
Which other dependencies are there? Still any need for SMESH and GEOM?

Thank you,

Henning

2011/9/29 Thomas Paviot <tpav...@gmail.com>:
> Dear all,
>
> Below the message sent by Denis Barbier on the oce-dev mailing list. Sorry
> for cross-posting if you already registered oce-dev, but this is a
> significant announce for the pythonocc project. This OCE release includes
> changes that are required by pythonocc to work as expected.
>
> I was waiting for this new version to be released before going on with
> pythonocc related developments. A few changes were recently commited. If
> you're interested in testing the current pythonocc status:
> git clone git://github.com/tpaviot/pythonocc.git
>
> Best Regards,
>
> Thomas
>
> ======================
> Hello,
>
> OCE 0.6.0 has been released.  This release is source and binary
> compatible with OCE 0.5.0.
> You can download sources from
>  https://github.com/tpaviot/oce/zipball/OCE-0.6.0  (.zip)
>  https://github.com/tpaviot/oce/tarball/OCE-0.6.0  (.tar.gz)
>
> Here are changes since OCE 0.5.0:
>
>  * Cmake 2.8 is explicitly required to build OCE.
>
>  * Removed many X11 dependencies. Now it is possible to build a large part
> of
>   OCE (with the exception of visualisation) without depending on X11 (using
>   OCE_DISABLE_X11 option).
>
>  * Cmake support : Cmake users will be able to correctly find OCE using
>   FIND_PACKAGE(OCE). Several examples are added to show how to use it in
>   end-user programs. It is now possible to detect/request single toolkits.
>
>  * Packaging : change installation paths; we do no more install files at the
>   same location as OpenCascade, but adopted more standard paths.
>
>  * Tests : integrated gtest 1.6.0 and added other unit tests, which helped
> in
>   fixing some bugs. Added MSVC support to the testsuite.
>
>  * Win32/MSVC improvements:
>   + Enabled configuration files in Win32 platforms
>   + Plugins and TKOpenGL are correctly found in debug builds
>   + TKOpenGL works when building static libraries
>
>  * Modify tcl scripts to not require $env(CASROOT).
>
>  * Many small changes, bug fixes and warning removals.
>   + Improvements to OSD_Process::SystemDate()
>   + TKernel : add dependency against -ldl.
>   + Bugfix : Work around a cmake bug that prevented building
> Win64+MSVC+static libs
>   + Bugfix : add missing include in BRepBlend_BlendTool.lxx.
>   + Bugfix : fix mismatch new/delete in Standard_Failure.cxx
>   + Fixed compiler warnings in OpenGl_TextureBox.cxx
>   + Whitespace cleanup
>   + In module TKOpenGL, fixed the two remaining GCC warnings of the form :
>     "comparison between ‘enum texStatus’ and ‘enum texDataStatus’"
>   + Added missing include in BRepBlend_BlendTool.lxx
>   + Fix capitalization of include file
>   + pass NULL for timezone pointer to gettimeofday()
>   + eliminate bad cast by copying to local variable
>   + use localtime_r if available
>   + Do not redefine memmove as an alias for memcpy
>   + Workaround GCC (< 4.3) bugs in gp_Mat, gp_XYZ, gp_Mat2d and gp_XY.
>   + Fix HashCode, it could segault when MMGT_OPT is not set to 1.
>
> Users who contributed to this release:
>     Denis Barbier, Thomas Paviot, Hugues Delorme, QbProg,
>     Matthew Dempsky, Massimo Del Fedele
>
> Enjoy,
> Denis
>
> _______________________________________________
> Pythonocc-users mailing list
> Pythonocc-users@gna.org
> https://mail.gna.org/listinfo/pythonocc-users
>
>

_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users

Reply via email to