#38919: Add port for h3dutil --------------------------------+-------------------------------- Reporter: daniel.evestedt@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: h3dutil | --------------------------------+-------------------------------- Comment (by daniel.evestedt@…): Replying to [comment:12 daniel.evestedt@…]:
Replying to [comment:11 ryandesign@…]:
Confirmed issue also exists on Mavericks, and issue does not exist on Mountain Lion.
However, on Mountain Lion, I saw a different error: The following file was recorded as part of the port's contents:
{{{
/Volumes/Data/macports/mountainlion/var/macports/build/_Volumes_Data_macports_dports_graphics_h3dutil/h3dutil/work/h3dutil-1.3.0/include/H3DUtil/H3DUtil.h
}}}
(where /Volumes/Data/macports/mountainlion is my MacPorts prefix and /Volumes/Data/macports/dports is my ports tree).
It's the same file that also got installed to the proper location:
{{{ /Volumes/Data/macports/mountainlion/include/H3DUtil/H3DUtil.h }}}
I'm not sure how this problem occurred or how best to correct it. Unfortunately this project uses cmake, which is very difficult for me to understand.
H3DUtil.h is automatically generated by CMake when H3DUtil is built. I think the location was changed between 1.2.0 and 1.3.0 and it is then put into place on install. How are you using 1.3.0 though? 1.2.0 seems to be the one in the current MacPorts version for me at least.
I tried in Mavericks and get the same issue. I tried to track it down and found out a few things. The dcmtk that is used for Mavericks is a snapshot version of the dcmtk code and not an official release. It seems to not be in a fully stable state yet. There are two ways to build dcmtk, CMake or configure. If using CMake dcmtk build will fail with the same errors as H3DUtil when linking applications or shared libraries. configure seems to work though. I would recommend to have the default build of dcmtk to be without libiconv and add support for it as a variant. Otherwise all libraries that previously used MacPorts dcmtk will fail on Mavericks. The best solution would be to provide shared libraries as well which would avoid this linking problem. However since the CMake build for shared libraries fails and configure does not seem to have this option there is no simple way to do that. -- Ticket URL: <https://trac.macports.org/ticket/38919#comment:13> MacPorts <http://www.macports.org/> Ports system for OS X