[Solved] Compiling Qt (with OpenSSL) failing
-
[quote author="ZapB" date="1302254313"]OK so this has nothing to do with OpenSSL then. Can you edit the title of the thread to reflect this please?
What is the exact configure line you are using please?[/quote]
As I said what I always used before, configure -openssl. About the thread title, even tough the problem encountered does not seem related to OpenSSL the result I'm looking for is, so will leave it as is. -
Downloaded the source code separately and it just compiled fine.
So here is my question why supply borked source code as an download option in the SDK if it doesn't even compile (at least on windows)? Cause it is a bit confusing as it includes everything to make it look like compilable but it isn't. -
Good question. If I were you I would file a bug report about this. I too would expect an SDK to ship sources with which I could recompile if wanted.
-
Yeah you'r right think thats the best to do :)
-
Bug report: "QTSDK-658":http://bugreports.qt.nokia.com/browse/QTSDK-658
-
Solved perl was missing from the path.
Strangely I had to install ActivePerl, until now I don't remember needing perl to compile Qt from source?
-
Just by curiosity does anyone knows since when perl is required?
-
I just commented on the bug report. Perl is required when building from git for the syncqt tool to be able to run. However, I do not think this should be required when using an sdk. It just raises the barrier to entry.
-
@ZapB I totally agree.
At least it would be good to have configure check for perl in the path and warn when it ain't there. It's mentioned on the installation webpage after digging through the requirements but you easily read over it so it's not that obvious.
Btw. I downloaded the qt-everywhere sources and they also need perl to run syncqt. I tried some old sources (4.5) I had lying around and they don't require perl. So somewhere along the road it was added :-)
-
Really? I don't remember seeing syncqt run when I built Qt-4.7.2 from sources. I'll have to check later and see.
Hopefully the trolls will sort this in time for Qt SDK 1.1 or 1.2.