qwt does not build with new qt4-mac port

[BSeppke (Benjamin Seppke)]

Since the qt4-mac port has recently/eventually received a major update. All of my dependent ports are building nicely except qwt-*. I tried qwt, qwt60 and qwt-devel and am always getting the follwing error at the staging phase:

--->  Staging qwt-devel into destroot
Error: org.macports.destroot for port qwt-devel returned: symlink: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_qwt/qwt-devel/work/destroot/opt/local/libexec/qt4/include/qwt -> /opt/local/libexec/qt4/Library/Frameworks/qwt.framework/Headers: no such file or directory

Since this exactly describes the error, I will not post the entire log here.

A possible solution (for me at least) was to remove the post-destroot stage inside the port file - although I'm quite unsure if that is okay or needed somewhere else.

[mf2k (Frank Schima)]

In the future, please use WikiFormatting, fill in the Port field and Cc the port maintainers (port info --maintainers qwt-devel), if any.

[dershow]

Cc Me!

[michaelld (Michael Dickens)]

I've been meaning to fix qwt for a while. I'll get at it now!

[patrick.sizun@…]

Cc Me!

[BSeppke (Benjamin Seppke)]

Hello all,

if you want to (really) use qwt, the above patch may not be appropriate, since it removes all the convenient links of the headers and the qwt-libs into the corresponding framework folders. To fix this issue, I suggest to add two lines after

    if {[file exists ${destroot}${qt_frameworks_dir}/qwt.framework/qwt]} {

        file mkdir ${destroot}${qt_includes_dir}
        file mkdir ${destroot}${qt_libs_dir}

This fixes the issue and makes the patchfile, which I attached previously, obsolete.

I attached the new working patch to this discussion, this solved the problem.

[BSeppke (Benjamin Seppke)]

working patch, solves the linking issues at staging phase

[BSeppke (Benjamin Seppke)]

Sorry, the last patch file was done using swapped original and working Portfile. The new one does this the right way round... BTW, I think that it's now time to apply the fix and close this issue?!

Best wishes Benjamin

[BSeppke (Benjamin Seppke)]

Correct (not inverted) patch file

[ralf.schulze@…]

Cc Me!