[77990] trunk/dports/graphics/openjpeg

[Ryan Schmidt]

On Apr 18, 2011, at 22:09, Ryan Schmidt wrote:

> On Apr 18, 2011, at 22:07, mcalhoun at macports.org wrote:
> 
>> Revision: 77990
>>         http://trac.macports.org/changeset/77990
>> Author:   mcalhoun at macports.org
>> Date:     2011-04-18 20:07:31 -0700 (Mon, 18 Apr 2011)
>> Log Message:
>> -----------
>> openjpeg: Fix inability to copy .dSYM directory with library; Fixes #29193.
>> No revision increases needed since the library builds correctly or not at all.
> 
> 
>> + all-local:
>> + 	@$(INSTALL) -d ../bin
>> +-	@cp -P .libs/libopenjpeg.* ../bin/
>> ++	@cp -PR .libs/libopenjpeg.* ../bin/
>> + 	@rm -f ../bin/libopenjpeg.la*
>> + 	@rm -rf .report_lib
>> + 	@$(INSTALL) -d .report_lib
>> +-	@cp -P .libs/libopenjpeg.* .report_lib
>> ++	@cp -PR .libs/libopenjpeg.* .report_lib
>> + 	@rm -f .report_lib/libopenjpeg.lai
>> + 	@echo "" > .report.txt
>> + 	@echo "Installing: ${prefix}/include/${headerdir}/" >> .report.txt
> 
> Is that the correct solution? Do we want .dSYM directories installed? Or should they be ignored when installing?

What I mean is, they are debugging information; we probably don't need to install it. Here's an amusing little write-up that talks about these "DWARF with dSYM" debugging files:

http://lapcatsoftware.com/blog/2009/01/20/dsym-in-your-bundle-or-just-happy-to-see-me/

Perhaps there is an argument we should be using when configuring that tells it not to create this debugging information in the first place. Or, perhaps we should be deleting the debugging information in post-build, so destroot doesn't see it.