Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple warnings when configuring OpenJPEG on MacOS with CMake 3.x (trunk) #443

Closed
gcode-importer opened this issue Nov 25, 2014 · 4 comments

Comments

@gcode-importer
Copy link

Originally reported on Google Code with ID 443

Building Shared library (default) adds one warning.
Using -DOPJ_USE_DSYMUTIL:BOOL=TRUE adds even more warnings

Reported by mayeut on 2014-11-25 21:50:16

@gcode-importer
Copy link
Author

This issue was updated by revision r2947.


Warnings related to OPJ_USE_DSYMUTIL are fixed

Reported by mayeut on 2014-11-25 21:52:34

@gcode-importer
Copy link
Author

For the last warning, a decision has to be made :
http://www.kitware.com/blog/home/post/510

/Applications/CMake-3.1.0-rc-2.app/Contents/bin/cmake --help-policy CMP0042
CMP0042
-------

``MACOSX_RPATH`` is enabled by default.

CMake 2.8.12 and newer has support for using ``@rpath`` in a target's install
name.  This was enabled by setting the target property
``MACOSX_RPATH``.  The ``@rpath`` in an install name is a more
flexible and powerful mechanism than ``@executable_path`` or ``@loader_path``
for locating shared libraries.

CMake 3.0 and later prefer this property to be ON by default.  Projects
wanting ``@rpath`` in a target's install name may remove any setting of
the ``INSTALL_NAME_DIR`` and ``CMAKE_INSTALL_NAME_DIR``
variables.

This policy was introduced in CMake version 3.0.  CMake version
3.1.0-rc2 warns when the policy is not set and uses OLD behavior.  Use
the cmake_policy command to set it to OLD or NEW explicitly.

Reported by mayeut on 2014-11-25 22:33:04

@gcode-importer
Copy link
Author

Since INSTALL_NAME_DIR is defined for APPLE in OpenJPEG, not much to decide.
Validate the new policy to remove warning

Reported by mayeut on 2014-11-25 23:55:13

@gcode-importer
Copy link
Author

This issue was closed by revision r2948.

Reported by mayeut on 2014-11-25 23:57:41

  • Status changed: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants