#36841 closed enhancement (fixed)
opencv: compile with headerpad_max_install_names flag
Reported by: | luc.jean@… | Owned by: | stromnov (Andrey Stromnov) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | ||
Port: | opencv |
Description
Hello,
I have an issue when making an app bundle for a opencv/python app with py2app.
The py2app maintainer said:
Shared libraries on OSX contain an absolute path to their location, and likewise all used libraries are also mentioned using an absolute path. Py2app uses macholib to rewrite those mentions to relative paths starting with '@executable_path'. For libraries that are located in /opt/local the new path requires more space than the old one, hence the error message. One way to ensure that there is enough space is the linker flag "headerpad_max_install_names". I don't know how to tell darwinports to add this flag when building opencv.
I don't know either. Does anybody can help me to fix this issue?
Best
Change History (6)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | opencv added |
---|---|
Priority: | High → Normal |
Summary: | How to compile opencv with headerpad_max_install_names flag? → opencv: compile with headerpad_max_install_names flag |
Type: | request → enhancement |
comment:2 Changed 12 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to stromnov@… |
---|
comment:4 Changed 12 years ago by stromnov (Andrey Stromnov)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Committed at r99684.
comment:5 Changed 12 years ago by luc.jean@…
Unfortunately, I still have the same issue when trying to use py2app and opencv. Any idea?
There shouldn't be any problem with just making opencv always build with headerpad_max_install_names so we should just do that, if we can figure out how/where to insert that directive.