Menu

Build errors on Fedora Core 5 x86_64

Help
wally_666
2006-04-12
2013-05-08
  • wally_666

    wally_666 - 2006-04-12

    I realized I should have started a new thread instead of continuing in the Debian package thread, I've copied my reply as a new thread here.  Sorry for the screw up.

    I'm using Fedora Core 5 on x86_64. Its QT version 3.3  (./configure; make) gives the same errors

    Errors:
    [wally@Knopbox v4l2ucp-1.2]$ make
    make all-am
    make[1]: Entering directory `/home/wally/v4l2ucp-1.2'
    if g++ -DPACKAGE_NAME=\"v4l2ucp\" -DPACKAGE_TARNAME=\"v4l2ucp\" -DPACKAGE_VERSION=\"1.2\" -DPACKAGE_STRING=\"v4l2ucp\ 1.2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"v4l2ucp\" -DVERSION=\"1.2\" -DHAVE_LINUX_VIDEODEV2_H=1 -I. -I. -g -O2 -MT mainWindow.o -MD -MP -MF ".deps/mainWindow.Tpo" -c -o mainWindow.o mainWindow.cpp; \
    then mv -f ".deps/mainWindow.Tpo" ".deps/mainWindow.Po"; else rm -f ".deps/mainWindow.Tpo"; exit 1; fi
    mainWindow.cpp:24:25: error: qscrollview.h: No such file or directory
    mainWindow.cpp:25:25: error: qfiledialog.h: No such file or directory
    mainWindow.cpp:26:21: error: qstring.h: No such file or directory
    mainWindow.cpp:27:20: error: qlabel.h: No such file or directory
    mainWindow.cpp:28:25: error: qpushbutton.h: No such file or directory
    mainWindow.cpp:29:26: error: qapplication.h: No such file or directory
    mainWindow.cpp:30:22: error: qmenubar.h: No such file or directory
    mainWindow.cpp:31:25: error: qmessagebox.h: No such file or directory
    In file included from mainWindow.cpp:33:
    v4l2controls.h:23:19: error: qhbox.h: No such file or directory
    v4l2controls.h:24:23: error: qcheckbox.h: No such file or directory
    v4l2controls.h:25:21: error: qslider.h: No such file or directory
    v4l2controls.h:26:23: error: qcombobox.h: No such file or directory
    v4l2controls.h:27:23: error: qlineedit.h: No such file or directory
    In file included from mainWindow.cpp:34:
    mainWindow.h:19:25: error: qmainwindow.h: No such file or directory
    mainWindow.h:20:20: error: qtimer.h: No such file or directory
    mainWindow.h:21:24: error: qpopupmenu.h: No such file or directory
    mainWindow.h:22:19: error: qgrid.h: No such file or directory
    v4l2controls.h:30: error: expected class-name before ‘{’ token
    v4l2controls.h:31: error: ISO C++ forbids declaration of ‘Q_OBJECT’ with no typev4l2controls.h:32: error: expected ‘;’ before ‘public’
    v4l2controls.h:42: error: ‘QWidget’ has not been declared
    v4l2controls.h:51: error: ISO C++ forbids declaration of ‘Q_OBJECT’ with no type

    The error cascade continues ....
    Seems its not finding the <QT.h> header files

    But they are there:
    [wally@Knopbox v4l2ucp-1.2]$ ls $QTINC
    jri.h qgvector.h qrtlcodec.h
    jri_md.h qhbox.h qscrbar.h
    jritypes.h qhbuttongroup.h qscrollbar.h

    ... and many more.

    I had to do an automake command since FC5 has v1.9, but it seemed to proceed wihtout errors.

    Any ideas?

    I've started a v4l2 based image processing application and my test capture program compiled and ran fine (originally developed on knoppix 4.0.2). I was looking at your program as a starting point for my user interface and a simple way to get brightness contrast adjustments (my crude program uses up/down arrow keys, but at least I can see the v4l2 ioctrls work).

    thanks for any help.
    --wally.

     
    • Scott J. Bertin

      Scott J. Bertin - 2006-04-13

      It appears that configure did not find qt. Try ./configure --with-Qt-dir=/usr/lib64/qt-3.3. If that doesn't work, send me the output of your configure command.

      Scott

       
    • wally_666

      wally_666 - 2006-04-13

      Made no difference, here is the output:

      [wally@Knopbox v4l2ucp-1.2]$ ./configure --with-Qt-dir=/usr/lib64/qt-3.3
      checking for a BSD-compatible install... /usr/bin/install -c
      checking whether build environment is sane... yes
      checking for gawk... gawk
      checking whether make sets $(MAKE)... yes
      checking whether to enable maintainer-specific portions of Makefiles... no
      checking for g++... g++
      checking for C++ compiler default output file name... a.out
      checking whether the C++ compiler works... yes
      checking whether we are cross compiling... no
      checking for suffix of executables...
      checking for suffix of object files... o
      checking whether we are using the GNU C++ compiler... yes
      checking whether g++ accepts -g... yes
      checking for style of include used by make... GNU
      checking dependency style of g++... gcc3
      checking for a BSD-compatible install... /usr/bin/install -c
      checking for gcc... gcc
      checking whether we are using the GNU C compiler... yes
      checking whether gcc accepts -g... yes
      checking for gcc option to accept ANSI C... none needed
      checking dependency style of gcc... gcc3
      checking how to run the C preprocessor... gcc -E
      checking for X... libraries , headers
      checking for gethostbyname... yes
      checking for connect... yes
      checking for remove... yes
      checking for shmat... yes
      checking for IceConnectionNumber in -lICE... yes
      checking for Qt... yes:
          QT_CXXFLAGS=-I/usr/lib64/qt-3.3/include -DQT_THREAD_SUPPORT
          QT_DIR=/usr/lib64/qt-3.3
          QT_LIBS=-L/usr/lib64/qt-3.3/lib -lqt-mt  -lSM -lICE  -lX11 -lXext -lXmu -lXt -lXi
          QT_UIC=/usr/lib64/qt-3.3/bin/uic
          QT_MOC=/usr/lib64/qt-3.3/bin/moc
      checking correct functioning of Qt installation... success
      checking for linux/videodev2.h... yes
      configure: creating ./config.status
      config.status: creating Makefile
      config.status: creating v4l2ucp.spec
      config.status: executing depfiles commands

      [wally@Knopbox v4l2ucp-1.2]$ make
      make  all-am
      make[1]: Entering directory `/home/wally/v4l2ucp-1.2'
      if g++ -DPACKAGE_NAME=\&quot;v4l2ucp\&quot; -DPACKAGE_TARNAME=\&quot;v4l2ucp\&quot; -DPACKAGE_VERSION=\&quot;1.2\&quot; -DPACKAGE_STRING=\&quot;v4l2ucp\ 1.2\&quot; -DPACKAGE_BUGREPORT=\&quot;\&quot; -DPACKAGE=\&quot;v4l2ucp\&quot; -DVERSION=\&quot;1.2\&quot; -DHAVE_LINUX_VIDEODEV2_H=1  -I. -I.      -g -O2 -MT mainWindow.o -MD -MP -MF ".deps/mainWindow.Tpo" -c -o mainWindow.o mainWindow.cpp; \ then mv -f ".deps/mainWindow.Tpo" ".deps/mainWindow.Po"; else rm -f ".deps/mainWindow.Tpo"; exit 1; fi
      mainWindow.cpp:24:25: error: qscrollview.h: No such file or directory
      mainWindow.cpp:25:25: error: qfiledialog.h: No such file or directory
      mainWindow.cpp:26:21: error: qstring.h: No such file or directory
      mainWindow.cpp:27:20: error: qlabel.h: No such file or directory
      mainWindow.cpp:28:25: error: qpushbutton.h: No such file or directory
      mainWindow.cpp:29:26: error: qapplication.h: No such file or directory
      mainWindow.cpp:30:22: error: qmenubar.h: No such file or directory
      mainWindow.cpp:31:25: error: qmessagebox.h: No such file or directory
      In file included from mainWindow.cpp:33:
      v4l2controls.h:23:19: error: qhbox.h: No such file or directory
      v4l2controls.h:24:23: error: qcheckbox.h: No such file or directory

      --wally.

       
    • wally_666

      wally_666 - 2006-04-13

      From what little I know of QT/KDE I thought I needed to run automake, configure, and make to build.

      Seems the v1.9 automake causes the problem, whatever it is.

      I deleted my v4l2ucp directory and recreated it from the tarball.  Doing ./configure;make build an apparently working program.

      Thanks.  I think you should add the ./configure;make commands to the README file as it seems the sequence of operations is pretty fragile, and it seems one must not run automake (or at least the 1.9 version of it).

      --wally.

       
    • wally_666

      wally_666 - 2006-04-13

      I just discovered that because of the shared opening allowed by v4l2 devices, I can run your v4l2ucp application as ./v4l2ucp /dev/video0 /dev/video1, then start my image processing code and use your controls to optimize the captures from my two frame grabbers with no changes to my code!

      Great job!
      --wally.

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.