July 18, 2012

gewv gewv
Lab Rat
1 posts

Fortran and Qt

 

Hello I am new in working with Qt.
I work with the Creator on Windows.

I would like to integrate Fortran into Qt.
Fortran is involved in the project file.

  1. TEMPLATE = app
  2. TARGET =
  3. DEPENDPATH += .
  4. INCLUDEPATH += .
  5. LIBS +=c:/Programme/MinGW/bin/libgfortran-3.dll
  6.  
  7. HEADERS += mywidget.h \
  8.     konvert.h \
  9.  
  10. SOURCES += main.cpp mywidget.cpp \
  11.     konvertF.f90

The compiler gives me the following error message.
_ 09:14:17: Führe Build-Schritte für Projekt Fortran_C_Qt aus…
09:14:17: Unveränderte Konfiguration, qmake-Schritt wird übersprungen.
09:14:17: Starte “C:\Programme\QtSDK\mingw\bin\mingw32-make.exe”
C:/Programme/QtSDK/mingw/bin/mingw32-make.exe -f Makefile.Debug
mingw32-make.exe1: Entering directory `D:/Qt/Beispiele/Fortran_C_Qt’
gcc -c -g -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I“c:\Programme\QtSDK\Desktop\Qt\4.8.1\mingw\include\QtCore” -I“c:\Programme\QtSDK\Desktop\Qt\4.8.1\mingw\include\QtGui” -I“c:\Programme\QtSDK\Desktop\Qt\4.8.1\mingw\include” -I”.” -I“c:\Programme\QtSDK\Desktop\Qt\4.8.1\mingw\include\ActiveQt” -I“debug” -I“c:\Programme\QtSDK\Desktop\Qt\4.8.1\mingw\mkspecs\win32-g++” -o debug\konvertF.o konvertF.f90
mingw32-make.exe1: Leaving directory `D:/Qt/Beispiele/Fortran_C_Qt’
gcc: CreateProcess: No such file or directory
mingw32-make.exe1: *** [debug/konvertF.o] Error 1
mingw32-make.exe: *** [debug] Error 2
09:14:17: Der Prozess “C:\Programme\QtSDK\mingw\bin\mingw32-make.exe” wurde mit dem Rückgabewert 2 beendet.
Fehler beim Erstellen des Projekts Fortran_C_Qt(Ziel: Desktop)
Bei der Ausführung von Build-Schritt ‘Make’_

But if I call individually gcc (gcc-c konvertF.f90) it works and I get an Objectfile. Then also the Linkingis o.K. and I get an .exe.

Must I change any FLAGS in qmake?

  1. # qmake configuration for win32-g++
  2. #
  3. # Written for MinGW
  4. #
  5.  
  6. MAKEFILE_GENERATOR = MINGW
  7. TEMPLATE  = app
  8. CONFIG   += qt warn_on release link_prl copy_dir_files debug_and_release debug_and_release_target precompile_header
  9. QT   += core gui
  10. DEFINES   += UNICODE QT_LARGEFILE_SUPPORT
  11. QMAKE_COMPILER_DEFINES  += __GNUC__ WIN32
  12.  
  13. QMAKE_EXT_OBJ           = .o
  14. QMAKE_EXT_RES           = _res.o
  15.  
  16. QMAKE_CC  = gcc
  17. QMAKE_LEX  = flex
  18. QMAKE_LEXFLAGS  =
  19. QMAKE_YACC  = byacc
  20. QMAKE_YACCFLAGS  = -d
  21. QMAKE_CFLAGS  =
  22. QMAKE_CFLAGS_DEPS = -M
  23. QMAKE_CFLAGS_WARN_ON = -Wall
  24. QMAKE_CFLAGS_WARN_OFF = -w
  25. QMAKE_CFLAGS_RELEASE = -O2
  26. QMAKE_CFLAGS_DEBUG = -g
  27. QMAKE_CFLAGS_YACC = -Wno-unused -Wno-parentheses
  28.  
  29. QMAKE_CXX  = gcc
  30. QMAKE_CXXFLAGS  = $$QMAKE_CFLAGS
  31. QMAKE_CXXFLAGS_DEPS = $$QMAKE_CFLAGS_DEPS
  32. QMAKE_CXXFLAGS_WARN_ON = $$QMAKE_CFLAGS_WARN_ON
  33. QMAKE_CXXFLAGS_WARN_OFF = $$QMAKE_CFLAGS_WARN_OFF
  34. QMAKE_CXXFLAGS_RELEASE = $$QMAKE_CFLAGS_RELEASE
  35. QMAKE_CXXFLAGS_DEBUG = $$QMAKE_CFLAGS_DEBUG
  36. QMAKE_CXXFLAGS_YACC = $$QMAKE_CFLAGS_YACC
  37. QMAKE_CXXFLAGS_THREAD = $$QMAKE_CFLAGS_THREAD
  38. QMAKE_CXXFLAGS_RTTI_ON = -frtti
  39. QMAKE_CXXFLAGS_RTTI_OFF = -fno-rtti
  40. QMAKE_CXXFLAGS_EXCEPTIONS_ON = -fexceptions -mthreads
  41. QMAKE_CXXFLAGS_EXCEPTIONS_OFF = -fno-exceptions
  42.  
  43.  
  44. QMAKE_INCDIR  =
  45. QMAKE_INCDIR_QT  = $$[QT_INSTALL_HEADERS]
  46. QMAKE_LIBDIR_QT  = $$[QT_INSTALL_LIBS]
  47.  
  48. QMAKE_RUN_CC  = $(CC) -c $(CFLAGS) $(INCPATH) -o $obj $src
  49. QMAKE_RUN_CC_IMP = $(CC) -c $(CFLAGS) $(INCPATH) -o $ $<
  50. QMAKE_RUN_CXX  = $(CXX) -c $(CXXFLAGS) $(INCPATH) -o $obj $src
  51. QMAKE_RUN_CXX_IMP = $(CXX) -c $(CXXFLAGS) $(INCPATH) -o $ $<
  52.  
  53. QMAKE_LINK  = gcc
  54. QMAKE_LINK_C  = gcc
  55. QMAKE_LFLAGS  =
  56. QMAKE_LFLAGS_EXCEPTIONS_ON = -mthreads
  57. QMAKE_LFLAGS_EXCEPTIONS_OFF =
  58. QMAKE_LFLAGS_RELEASE = -Wl,-s
  59. QMAKE_LFLAGS_DEBUG =
  60. QMAKE_LFLAGS_CONSOLE = -Wl,-subsystem,console
  61. QMAKE_LFLAGS_WINDOWS = -Wl,-subsystem,windows
  62. QMAKE_LFLAGS_DLL        = -shared
  63. QMAKE_LINK_OBJECT_MAX = 10
  64. QMAKE_LINK_OBJECT_SCRIPT= object_script
  65. QMAKE_PREFIX_STATICLIB  = lib
  66. QMAKE_EXTENSION_STATICLIB = a
  67.  
  68.  
  69. QMAKE_LIBS  =
  70. QMAKE_LIBS_CORE         = -lole32 -luuid -lws2_32 -ladvapi32 -lshell32 -luser32 -lkernel32
  71. QMAKE_LIBS_GUI          = -lgdi32 -lcomdlg32 -loleaut32 -limm32 -lwinmm -lwinspool -lws2_32 -lole32 -luuid -luser32 -ladvapi32
  72. QMAKE_LIBS_NETWORK      = -lws2_32
  73. QMAKE_LIBS_OPENGL       = -lglu32 -lopengl32 -lgdi32 -luser32
  74. QMAKE_LIBS_COMPAT       = -ladvapi32 -lshell32 -lcomdlg32 -luser32 -lgdi32 -lws2_32
  75. QMAKE_LIBS_QT_ENTRY     = -lmingw32 -lqtmain
  76.  
  77. !isEmpty(QMAKE_SH) {
  78.     MINGW_IN_SHELL      = 1
  79.  QMAKE_DIR_SEP  = /
  80.  QMAKE_QMAKE  ~= s,\\\\,/,
  81.  QMAKE_COPY  = cp
  82.         QMAKE_STREAM_EDITOR     = sed
  83.  QMAKE_COPY_DIR  = cp -r
  84.  QMAKE_MOVE  = mv
  85.  QMAKE_DEL_FILE  = rm
  86.  QMAKE_MKDIR  = mkdir -p
  87.  QMAKE_DEL_DIR  = rmdir
  88.     QMAKE_CHK_DIR_EXISTS = test -d
  89. } else {
  90.  QMAKE_COPY  = copy /y
  91.  QMAKE_COPY_DIR  = xcopy /s /q /y /i
  92.  QMAKE_MOVE  = move
  93.  QMAKE_DEL_FILE  = del
  94.  QMAKE_MKDIR  = mkdir
  95.  QMAKE_DEL_DIR  = rmdir
  96.     QMAKE_CHK_DIR_EXISTS = if not exist
  97. }
  98.  
  99. QMAKE_MOC  = $$[QT_INSTALL_BINS]$${DIR_SEPARATOR}moc.exe
  100. QMAKE_UIC  = $$[QT_INSTALL_BINS]$${DIR_SEPARATOR}uic.exe
  101. QMAKE_IDC  = $$[QT_INSTALL_BINS]$${DIR_SEPARATOR}idc.exe
  102.  
  103. QMAKE_IDL  = midl
  104. QMAKE_LIB  = ar -ru
  105. QMAKE_RC  = windres
  106. QMAKE_ZIP  = zip -r -9
  107.  
  108. QMAKE_STRIP  = strip
  109. QMAKE_STRIPFLAGS_LIB  += --strip-unneeded
  110. load(qt_config)

Would be nice if someone could help me.

0 replies

 
  ‹‹ Where are FindShiboken and FindPySide.cmake? for PySide Binding Generation Tutorial      [Solved] PyQt Dialog Window Not Popping up in Function ››

You must log in to post a reply. Not a member yet? Register here!