#39213 closed enhancement (fixed)
HexFiend @2.1.2: Install HexFiend.framework into ${frameworks_dir}
| Reported by: | cooljeanius (Eric Gallager) | Owned by: | neverpanic (Clemens Lang) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.3 |
| Keywords: | Cc: | dweber@…, neverpanic (Clemens Lang), nonstop.server@… | |
| Port: | HexFiend |
Description
HexFiend.framework is supposed to be a shared library that other applications can use. Installing it to ${frameworks_dir} would make it easier to link against.
Change History (4)
comment:1 Changed 11 years ago by nonstop.server@…
| Cc: | nonstop.server@… added |
|---|
comment:2 Changed 11 years ago by neverpanic (Clemens Lang)
| Owner: | changed from macports-tickets@… to cal@… |
|---|---|
| Status: | new → assigned |
comment:3 follow-up: 4 Changed 11 years ago by neverpanic (Clemens Lang)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I wanted to avoid fixing all binaries of HexFiend.app using install_name_tool, but at the same time provide a re-usable HexFiend component, so I created a subport in r108291 providing the framework to simplify re-using it.
comment:4 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to cal@…:
I wanted to avoid fixing all binaries of HexFiend.app using
install_name_tool, but at the same time provide a re-usable HexFiend component, so I created a subport in r108291 providing the framework to simplify re-using it.
That seems like a good enough solution, thanks for the update!
Note: See
TracTickets for help on using
tickets.
Cc Me!