Opened 13 years ago
Closed 12 years ago
#32052 closed defect (wontfix)
dcmtk: enable dynamic linking
| Reported by: | angleto@… | Owned by: | eborisch (Eric A. Borisch) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | ||
| Port: | dcmtk |
Description
dcmtk are statically linked by default, working with static linked dcmtk may cause problems because of static data declared in the library. The dynamic linking should be the default option for dcmtk.
Attachments (1)
Change History (8)
comment:1 Changed 13 years ago by mf2k (Frank Schima)
| Owner: | changed from macports-tickets@… to eborisch@… |
|---|---|
| Port: | dcmtk added |
comment:2 follow-up: 3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | enabling dynamic linking for dcmtk → dcmtk: enable dynamic linking |
|---|
comment:3 Changed 13 years ago by angleto@…
Replying to ryandesign@…:
I'm not sure I understand exactly. How would we make this change?
detailed steps for dynaminc linking of dcmtk are described here: http://forum.dcmtk.org/viewtopic.php?t=19 In my opinion, dynamic linking of dcmtk should be the default choice, meanwhile static linking should be enabled using port variants.
comment:4 Changed 13 years ago by eborisch (Eric A. Borisch)
Is there a discussion we can link to for the record where the developers say that their default (static) build is broken (or at least in what cases it is)?
comment:5 follow-up: 6 Changed 13 years ago by eborisch (Eric A. Borisch)
Implementing the changes from the link above results in a build failure. Do you have a patch for this?
comment:6 Changed 13 years ago by angleto@…
Replying to eborisch@…:
Implementing the changes from the link above results in a build failure. Do you have a patch for this?
I'm sorry I have not any patch. I have no experience of problems compiling shared version of dcmtk, could you post the errors?
Changed 13 years ago by eborisch (Eric A. Borisch)
comment:7 Changed 12 years ago by eborisch (Eric A. Borisch)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
This will be implemented once it is supported in an upstream release.
I'm not sure I understand exactly. How would we make this change?