René Bertin

On Monday August 12 2024 03:32:08 Sergey Fedorov wrote: >Given that current MacPorts setup has known problems with some Qt4 plugins, I certainly do not mean we should follow that...

On Saturday December 28 2024 23:23:25 Sergey Fedorov wrote: >Or is there any reason to have two ports? Maybe replace `qt4-mac` with the devel version, and then it is simple....

OK, that's a situation that I address in part in my Qt5 ports, by installing symlinks that expose "my" component directories via the paths where "their" install schema would put...

On Sunday December 29 2024 06:59:02 Sergey Fedorov wrote: >`qt4pas got installed with `qt4-mac-devel` like this: > /opt/local/libexec/qt4/lib/Qt4Pas.framework/ Does that port hardcode an install location? Still not at my Mac...

On Sunday December 29 2024 06:59:02 Sergey Fedorov wrote: >So that is not found. The only other port I know of that installs a framework into $qt_dir/lib is port:qt-assistant, but...

On Sunday December 29 2024 14:30:15 Karl-Michael Schindler wrote: >> Does that port hardcode an install location? Still not at my Mac but it looks like the wrong path for...

On Sunday December 29 2024 17:11:11 Karl-Michael Schindler wrote: >It is not in the original sources, but then shows up in the Makefile, which I assume is created by qmake.:...

On Monday December 30 2024 05:31:57 Sergey Fedorov wrote: >Relevant to `qt4pas` is this: >``` ># searchpath for qt4pas framework >#IFDEF Darwin >-Ff/opt/local/libexec/qt4/lib >#ENDIF >``` > If the build is...

> ld: framework not found Qt4Pas Doh moment: is that how the framework directory name is spelled and are you using a case-sensitive filesystem?

No, the linker error is specific enough that it's unlikely to be a Cocoa vs. Carbon issue. But you'd have to get the build to produce more verbose output so...