Results 1 to 4 of 4

Thread: Need help accessing AVT camera (with wrapper?)!

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Mar 2009
    Location
    Brisbane, Australia
    Posts
    7,729
    Qt products
    Qt4 Qt5
    Platforms
    Unix/X11 Windows
    Thanks
    13
    Thanked 1,610 Times in 1,537 Posts
    Wiki edits
    17

    Default Re: Need help accessing AVT camera (with wrapper?)!

    The *.lib files will not work directly with MingW (the second paragraph is about Dev C++). You should find the MingW linker will work directly against the C wrapper DLL. Try this:
    Qt Code:
    1. INCLUDEPATH += C:/FirePackage/FireGrab/Lib/Extra
    2. LIBS += -LC:/FirePackage/FireGrab/Lib/Extra -lFGWrap
    To copy to clipboard, switch view to plain text mode 

  2. The following user says thank you to ChrisW67 for this useful post:

    emigrand (8th April 2012)

  3. #2
    Join Date
    Dec 2011
    Location
    Jena, Germany
    Posts
    13
    Qt products
    Qt4
    Platforms
    Windows
    Thanks
    2

    Default Re: Need help accessing AVT camera (with wrapper?)!

    Thanks a lot Chris, that did it! Although I didn`t "fully" understand the magic behind your code. A short comment would be nice

  4. #3
    Join Date
    Mar 2009
    Location
    Brisbane, Australia
    Posts
    7,729
    Qt products
    Qt4 Qt5
    Platforms
    Unix/X11 Windows
    Thanks
    13
    Thanked 1,610 Times in 1,537 Posts
    Wiki edits
    17

    Default Re: Need help accessing AVT camera (with wrapper?)!

    INCLUDEPATH is used during the compilation of your C++ code into object files (*.obj or *.o). Any #include "file.h" directive will potentially search through directories listed in INCLUDEPATH in order to find "file.h" if it is not in the current directory.

    LIBS controls the linking phase, where your object files are coalesced into your target executable or library. The "-L" entries specify a directory to search for named libraries (there can be several). The "-l" (lower case L) entries specify the name of libraries (*.lib or *.a) to search for routines used by your program that are not present in your program.

    C++ compilers do not generally create libraries compatible with other C++ compilers for technical reasons: which is why the C++ interface library built with MSVC is not available to you using MingW. A C-style interface is portable between compilers but, for obvious reasons, cannot export classes or other C++ constructs. The C-style interface gives you a handle-based interface in your wrapper. MingW can often use a DLL with C-style interfaces directly without a separate *.lib or *.a file: this is what has worked here.

Similar Threads

  1. Accessing Symbian Camera trough QCamera
    By daleotar in forum Qt for Embedded and Mobile
    Replies: 4
    Last Post: 25th September 2011, 17:18
  2. Qt Wrapper for bzip2
    By wirasto in forum Newbie
    Replies: 11
    Last Post: 24th December 2009, 09:45
  3. wrapper of methods
    By mickey in forum General Programming
    Replies: 8
    Last Post: 15th August 2008, 15:33
  4. wrapper in C for QT
    By YuriyRusinov in forum Qt Programming
    Replies: 4
    Last Post: 29th October 2007, 20:06
  5. V4L Qt wrapper
    By scarvenger in forum Qt Programming
    Replies: 1
    Last Post: 6th May 2007, 15:54

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Qt is a trademark of The Qt Company.