Closed adam-urbanczyk closed 3 years ago
Looks like #41 triggers this
Any ideas what went wrong? Does occt from cadquery builds with freeimage enabled?
No clue I'm afraid - I only uploaded your build no 5 version to keep my ci pipeline going.
Can you try the more recent build h2fc2405_2 of freeimage?
The version listed above does not set the version properly https://anaconda.org/conda-forge/freeimage/3.18.0/download/osx-64/freeimage-3.18.0-h4a8c4bd_0.tar.bz2
$ otool -L Downloads/freeimage-3.18.0-h4a8c4bd_0/lib/libfreeimage.3.dylib
Downloads/freeimage-3.18.0-h4a8c4bd_0/lib/libfreeimage.3.dylib:
libfreeimage-3.18.0.dylib-x86_64 (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.4)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.200.5)
Edit: And the correct output of the new version
$ otool -L Downloads/freeimage-3.18.0-h2fc2405_2/lib/libfreeimage.dylib
Downloads/freeimage-3.18.0-h2fc2405_2/lib/libfreeimage.dylib:
@rpath/libfreeimage.3.dylib (compatibility version 3.0.0, current version 3.18.0)
@rpath/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
@rpath/libjpeg.9.dylib (compatibility version 13.0.0, current version 13.0.0)
@rpath/libtiff.5.dylib (compatibility version 11.0.0, current version 11.0.0)
@rpath/libpng16.16.dylib (compatibility version 54.0.0, current version 54.0.0)
@rpath/libopenjp2.7.dylib (compatibility version 7.0.0, current version 2.3.1)
@rpath/libwebpmux.3.dylib (compatibility version 4.0.0, current version 4.4.0)
@rpath/libwebp.7.dylib (compatibility version 8.0.0, current version 8.4.0)
@rpath/libjxrglue.0.dylib (compatibility version 0.0.0, current version 1.1.0)
@rpath/libraw.19.dylib (compatibility version 20.0.0, current version 20.2.0)
@rpath/libIlmImf.24.dylib (compatibility version 24.0.0, current version 24.0.0)
@rpath/libIex.24.dylib (compatibility version 24.0.0, current version 24.0.0)
@rpath/libHalf.24.dylib (compatibility version 24.0.0, current version 24.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
@rpath/libc++.1.dylib (compatibility version 1.0.0, current version 1.0.0)
@frmdstryr should we set the failing freeimage package to broken? https://github.com/conda-forge/cf-mark-broken
@frmdstryr I can confirm that using newer freeimage is solving the issue. @looooo that sounds like a logical conclusion.
@frmdstryr btw.: freeimage seems to be gpl2/gpl3 licensed. I don't think we are allowed to distribute occt (lgpl) this way. Other occt versions on anaconda use freeimage plus So best to package freeimage-plus for conda-forge. And I guess we have to set the new occt-version to broken until we have changed to freeimage-plus.
regarding https://dev.opencascade.org/doc/occt-6.9.1/overview/html/index.html freeimage can be used with occt on condition of the FIPL license:
FreeImage is an Open Source library supporting popular graphics image formats, such as PNG, BMP, JPEG, TIFF, and others used by multimedia applications. This library is developed by Hervé Drolon and Floris van den Berg. FreeImage is easy to use, fast, multithreading safe, compatible with all 32-bit or 64-bit versions of Windows, and cross-platform (works both with Linux and Mac OS X). FreeImage is optionally used by OCCT to work with images, on conditions of the FreeImage Public License (FIPL) (http://freeimage.sourceforge.net/freeimage-license.txt).
I guess we can close this issue @adam-urbanczyk
LGTM
Issue: after importing a compiled python module linking to occt I get this:
Environment (
conda list
):Details about
conda
and system (conda info
):