lprof 20090119, new port

[lassi.tuura@…]

I have attached a port file for graphics/lprof, an open source tool for icc colour profile management. There's no recent source package so code is taken from the CVS repository, the version is simply the date I took the code.

[nerdling (Jeremy Lavergne)]

I tried building lprof and received a problem with qmake being not found. It is, I believe, called qmake-mac on my box (from a fresh cmake install).

CMake Error at /opt/local/share/cmake-2.6/Modules/FindQt4.cmake:1664 (MESSAGE):

Qt qmake not found!

Call Stack (most recent call first):

CMakeLists.txt:78 (FIND_PACKAGE)

[nerdling (Jeremy Lavergne)]

styling/whitespace updates

[nerdling (Jeremy Lavergne)]

/Applications/MacPorts -> $applications_dir

[nerdling (Jeremy Lavergne)]

Can you check out line 36 of the Portfile? I believe there's a backslash where there ought not be one, but you know your configure flags better than me :-)

[lassi.tuura@…]

Can you check out line 36 of the Portfile? I believe there's a backslash where there ought not be one, but you know your configure flags better than me :-)

Thanks for reviewing the port file and your changes.

Which backslash(es) are you referring to? For CMAKE_SYSTEM_PREFIX_PATH I believe it actually means to have the quotes and the semicolon in the variable value. But no, I don't know these configure flags any better than you I am afraid :-/ I know next to nothing about cmake, I effectively just copied flags from existing portfiles using both cmake and qt until it built.

If you want I can bisect through the options to reduce them to the minimal set.

Was the issue with cmake not finding qmake solved?

[lassi.tuura@…]

Replying to snc@…:

I tried building lprof and received a problem with qmake being not found. It is, I believe, called qmake-mac on my box (from a fresh cmake install).

CMake Error at /opt/local/share/cmake-2.6/Modules/FindQt4.cmake:1664 (MESSAGE):

Qt qmake not found!

Call Stack (most recent call first):

CMakeLists.txt:78 (FIND_PACKAGE)

For the record here, as I replied in e-mail but the message never made it to the tracking system:

Thanks for the review! I have:

$ port provides =qmake /opt/local/bin/qmake is provided by: qt4-mac

$ port contents qt4-mac | grep /bin/qmake

/opt/local/bin/qmake /opt/local/libexec/qt4-mac/bin/qmake

LPROF built for me straight from that portfile on two different 10.4.11 systems. Neither system had any version of qt pre-installed anywhere on the system. Any ideas why this doesn't work for you?

[nerdling (Jeremy Lavergne)]

Your qt4-mac provides qmake, but mine provides qmake-mac. Can you please supply me with the output of port installed qt4-mac?

[nerdling (Jeremy Lavergne)]

Replying to lassi.tuura@…:

Which backslash(es) are you referring to? For CMAKE_SYSTEM_PREFIX_PATH I believe it actually means to have the quotes and the semicolon in the variable value. But no, I don't know these configure flags any better than you I am afraid :-/ I know next to nothing about cmake, I effectively just copied flags from existing portfiles using both cmake and qt until it built.

Well, I looked through them again and I don't see what I saw before!

[nerdling (Jeremy Lavergne)]

Replying to lassi.tuura@…:

Which backslash(es) are you referring to? For CMAKE_SYSTEM_PREFIX_PATH I believe it actually means to have the quotes and the semicolon in the variable value. But no, I don't know these configure flags any better than you I am afraid :-/ I know next to nothing about cmake, I effectively just copied flags from existing portfiles using both cmake and qt until it built.

I take that back. Line 36 has the quotes escaped but the rest of the commands do not. This seems suspicious to me. Once I've figured out why my qmake is named differently, this will be next on my list to check, however you said it built just fine for you. It could just be a non-issue.

[lassi.tuura@…]

$ port installed qt4-mac The following ports are currently installed:

qt4-mac @4.4.3_0+dbus+docs+mysql5+sqlite+ssl (active)

Hm, earlier I said it installed from a system without qt. I think I did actually try that first, and it installed fine, but then later decided I wanted qt with more options and did "sudo port install qt4-mac +ssl +sqlite +mysql5". I don't think the above variants affect qmake, but I could of course be wrong.

[lassi.tuura@…]

Concerning CMAKE_SYSTEM_PREFIX_PATH, you can try "grep -r CMAKE_SYSTEM_PREFIX_PATH /opt/local/var/macports/sources". For me it returns 17 matches all of the same form. I really don't know more than that, but if you think there's a real problem, I can try to dig further into it. Just let me know.

[nerdling (Jeremy Lavergne)]

Replying to lassi.tuura@…:

$ port installed qt4-mac The following ports are currently installed:

qt4-mac @4.4.3_0+dbus+docs+mysql5+sqlite+ssl (active)

Hm, earlier I said it installed from a system without qt. I think I did actually try that first, and it installed fine, but then later decided I wanted qt with more options and did "sudo port install qt4-mac +ssl +sqlite +mysql5". I don't think the above variants affect qmake, but I could of course be wrong.

The qt4-mac on my system is using a newer portfile than yours — 4.4.3_1. The newer does not have the variants that you're using. It only has noframework, webkit, and universal. Could you do a sudo port selfupdate && port upgrade -u outdated, and then reinstall lprof?

Of further note, the portfile says it depends on the qt4-mac libraries, so it would have to be built prior to allowing the installing of lprof. If it actually doesn't depend on qt4-mac we should remove it from the dependencies.

[lassi.tuura@…]

LProf is a Qt application, so I assume qt4-mac is required. Or did I misunderstand your comment about the dependency?

Regarding self-update/upgrade -- no thanks, not right now :-) I did attempt a global upgrade about month and a half ago, and ended up in extended nightmare which eventually reduced to rm -fr /opt/local and reinstalling absolutely everything. As the system runs several macports servers I depend on for daily work, I am highly reluctant to attempt this difficult an upgrade much more than about once a year. (One feature of the previous upgrade was that it attempted to rebuild commonly used libraries, such as libintl, for _every single port that needed them._ Basically the reinstallation grew exponentially in time as it progressed up the tree. But to be honest I am not sure if it made any progress at all, it just seemed to run compilations in a near-infinite loop. Plus (re)building packages such as tetex or qt is just painful.)

[nerdling (Jeremy Lavergne)]

I'm sorry you went through most of that trouble with MacPorts 1.6. Those have almost entirely been addressed with MacPorts 1.7.

Rather than using sudo port upgrade -u outdated, would it be safe to just sudo port deactivate qt4-mac and sudo port -f install qt4-mac a new version of it (you can then activate/deactivate the different versions to fall back)? Please do a sudo port selfupdate beforehand.

[lassi.tuura@…]

OK, I'll try that tonight, thanks.

[lassi.tuura@…]

I braved for the macports upgrade to 1.7 plus "sudo port upgrade -u outdated" on another system. Other than running through the night and leaving broken doxygen and tetex, it appears it actually worked fine.

Yes I confirm there are a couple of problems finding qmake-mac and lrelease-mac programs. I guess qt4-mac package changes the names of the executables to avoid conflicts with x11-based qt. At any rate adding -DQT_QMAKE_EXECUTABLE=${prefix}/bin/qmake-mac -DQTTRANS_LRELEASE_EXECUTABLE=${prefix}/bin/lrelease-mac to configure.args fixes it.

At that point the build dies in link with SSL symbol errors. I didn't have time to investigate further, but it seems something may have changed about qt/openssl integration. I am fairly sure the application itself makes no use whatsoever of SSL, and probably could not care less about those symbols...

[nerdling (Jeremy Lavergne)]

I can create OS-dependent configure.args (through variant darwin X). That should address the QT problems.

As for SSL linking, I'll see what I can find at this end once I get these flags fixed.

[lassi.tuura@…]

Hi, I don't think there's any need to make the flags OS-dependent. I doubt the application will work on OS X with X11-flavour of Qt. At any rate, even if it was technically possible, it would probably be counter-productive since the application is designed to be colour managed, and I think there's better chance for the "native" APIs to accomplish that than going via X11.

[nerdling (Jeremy Lavergne)]

An interesting development: It now configures with your changes and is presently building. The Qt/SSL problems must have been fixed.

[nerdling (Jeremy Lavergne)]

added changes to configure.args

[nerdling (Jeremy Lavergne)]

Let me know if the 4th Portfile works and I'll commit it!

[nerdling (Jeremy Lavergne)]

Timeout: Committed in r47902.

[nerdling (Jeremy Lavergne)]

Sorry, meant r47905.

[(none)]

Milestone Port Submissions deleted