Compilation problem with Mac OS X El Capitan 10.11.5

Started by Pg, June 09, 2016, 10:40:04 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Pg

Hi,

I have an MacBook Pro 13", 2010.
I installed :

Xcode 7.3.1

Qt 5.6.1 (Clang 7.0 (Apple), 64 bit (https://download.qt.io/official_releases/qt/5.6/5.6.1/)

FET 5.29.4

but don't work...

terminal :
Last login: Thu Jun  9 09:52:55 on console
MacBook-Pro-di-****:~ Roby$ cd fet-5.29.4 
MacBook-Pro-di-****:fet-5.29.4 Roby$ /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -spec macx-g++ fet.pro 
MacBook-Pro-di-****:fet-5.29.4 Roby$ make
cd src/ && ( test -e Makefile || /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake /Users/Roby/fet-5.29.4/src/src.pro -spec macx-g++ -o Makefile ) && /Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile 
/Users/Roby/Qt5.6.0/5.6/clang_64/bin/qmake -spec macx-g++ -o Makefile src.pro
make[1]: /Users/Roby/Qt5.6.0/5.6/clang_64/bin/qmake: No such file or directory
make[1]: *** [Makefile] Error 1
make: *** [sub-src-src-pro-make_first] Error 2
MacBook-Pro-di-****:fet-5.29.4 Roby$ 

I installed other old Qt but don't work.

even with only the command line : qmake -spec macx-g++ fet.pro 

can you help me?

thanks

Liviu Lalescu

#1
Please keep installed Qt 5.6.1 only, and try:

> /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake fet.pro
> make

If the above does not work, let me know and I'll search some more on the internet.

Edit: I found http://qt.apidoc.info/5.1.1/qtdoc-online/developing-on-mac.html , see: "Note: You can also use the qmake -spec macx-xcode command to generate the .xcodeproj file, which is required to open your Qt project in XCode." Might help.

Pg


Liviu Lalescu


Pg


Liviu Lalescu

Try:

./Users/yourname/QT5_build/bin/qmake [Your .pro file] -r -spec /Users/yourname/QT5_build/mkspecs/macx-clang
make -f [Path to your make file] release

and tell me what you get.

Pg

cd fet-5.29.4

enter

./Users/Roby/QT5_build/bin/qmake -spec macs-g++fet.pro -r -spec /Users/Roby/QT5_build/mkspecs/macx-clang

enter

make -f [Path to your make file] release        (what is this?)

enter

Volker Dirr

#7
we need to know the "answer" from the terminal.

i suggest to set a PATH to the qt bin stuff and start compiling from fet directory. that is much easier, because you don't need to write always the whole path.

Liviu Lalescu

Quote
./Users/yourname/QT5_build/bin/qmake [Your .pro file] -r -spec /Users/yourname/QT5_build/mkspecs/macx-clang

Please replace the first part with the path to qmake: /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake , and the last part with /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang

Quote
make -f [Path to your make file] release

Inside the same FET-5.29.4 directory type make -f Makefile release

Pg

MacBook-Pro-di-*****:~ Roby$ cd fet-5.29.4
MacBook-Pro-di-**********:fet-5.29.4 Roby$ /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang
Cannot read /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang: file to open is a directory
Error processing project file: /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang
MacBook-Pro-di-************:fet-5.29.4 Roby$ make -f Makefile release
make: *** No rule to make target `release'.  Stop.
MacBook-Pro-di-*********:fet-5.29.4 Roby$

Liviu Lalescu

Please do:

/Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -r -spec /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang
then
make -f Makefile release

(you forgot "-r -spec" in the first line).

Pg

I installed FET 5.29.5
I have tried with the normal procedure :
cd fet-5.29.5
enter
/Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -spec macx-g++ fet.pro
enter
make
enter

but :

/Users/Roby/Qt5.6.1/5.6/clang_64/lib/QtCore.framework/Headers/qpair.h:62:52: error:
      'T1' does not refer to a value
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && ...
                                                   ^
/Users/Roby/Qt5.6.1/5.6/clang_64/lib/QtCore.framework/Headers/qpair.h:42:17: note:
      declared here
template <class T1, class T2>
                ^
/Users/Roby/Qt5.6.1/5.6/clang_64/lib/QtCore.framework/Headers/qpair.h:62:55: error:
      expected expression
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && ...
                                                      ^
/Users/Roby/Qt5.6.1/5.6/clang_64/lib/QtCore.framework/Headers/qpair.h:62:57: error:
      expected expression
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && ...
                                                        ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[1]: *** [../tmp/gui/timetableexport.o] Error 1
make: *** [sub-src-src-pro-make_first] Error 2
MacBook-Pro-di-Roberta-Cabianca:fet-5.29.5 Roby$

I have tried with the last procedure :

cd fet-5.29.5
enter/Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -r -spec /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang
enter
make -f Makefile release
enter

but :

MacBook-Pro-di-******:~ Roby$ cd fet-5.29.5
MacBook-Pro-di-******:fet-5.29.5 Roby$ /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -r -spec /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang
Reading /Users/Roby/fet-5.29.5/src/src.pro
Reading /Users/Roby/fet-5.29.5/src/src-cl.pro
MacBook-Pro-di-********:fet-5.29.5 Roby$ make -f Makefile release
make: *** No rule to make target `release'.  Stop.
MacBook-Pro-di-********:fet-5.29.5 Roby$

Liviu Lalescu

In the last line, instead of "make -f Makefile release" type only "make -f Makefile" or also try simply "make".

If it does not work, try removing the FET unpacked and unpack it again and only do the clang part (/Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -r -spec /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang and make).

If it does not work, try again with: /Users/Roby/Qt5.6.1/5.6/clang_64/bin/qmake -spec /Users/Roby/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang and make.

Pg

Work!

cd fet-5.29.5

enter

/Users/Yourname/Qt5.6.1/5.6/clang_64/bin/qmake -r -spec /Users/Yourname/Qt5.6.1/5.6/clang_64/mkspecs/macx-clang

enter

make

enter

Thanks!

Liviu Lalescu

#14
You are welcome! :)

Note: The "-r" parameter might be not necessarily needed.