Qwt-6.0.0-rc1

Hi all,

I have uploaded the first release candidate of Qwt 6.0.0 to
https://sourceforge.net/project/admi...group_id=13693. See the
qwt-beta section.

The main intention of this release candidate is to check whether it compiles
and builds in the various environments. Like always my tests were with gcc +
Linux/X11 only.

Beside building the examples I would be interested in tests of qwt.prf - the
configuration features file of Qwt. When it is properly installed (make
install) and can be seen ( http://doc.qt.nokia.com/4.7/qmake-ad...ation-features ) by qmake it you should be enough to write "CONFIG += qwt" in your application qmake project file.

Because there are already several applications using Qwt from SVN trunk most
new classes are already tested to a certain level - beside the changes to the
raster item classes ( f.e spectrogram ), that have been implemented recently.
I would be interested in some feedback in this area ( particularly about
QwtMatrixRasterData ).

Qwt 6.0 is intended to support Qt versions >= Qt 4.4.

Uwe

Here are my experiences (Mac OS X 10.6, Qt 4.7):

1. for me, the link you posted does not work (permission denied)

2. if I compile the package as is (without modification of any of the files) I get linker errors:


linking plugins/designer/libqwt_designer_plugin.dylib
ld: warning: directory '/tmp/qt-stuff-6474/source/qt-everywhere-opensource-src-4.7.0/lib' following -L not found
ld: warning: directory '/tmp/qt-stuff-6474/source/qt-everywhere-opensource-src-4.7.0/lib' following -F not found
ld: framework not found qwt
collect2: ld returned 1 exit status
make[1]: *** [plugins/designer/libqwt_designer_plugin.dylib] Error 1
make: *** [sub-designer-make_default-ordered] Error 2


Deactivating the compilation of the examples and the Designer plugins solves the issue.

3. only debug libraries are built. Is this the intended behaviour?

Thanks for testing.

Quote:

---

Originally Posted by mariposa

1. for me, the link you posted does not work (permission denied)

---

Right, this one should be better: http://sourceforge.net/projects/qwt/

Quote:

---

Originally Posted by mariposa

2. if I compile the package as is (without modification of any of the files) I get linker errors:

---

Please tell me the reason for the bad linker command - I don't have a Mac.

Quote:

---

Originally Posted by mariposa

3. only debug libraries are built. Is this the intended behaviour?

---

Ah no - this is a bug in my package build script. Only release libraries should be built on the Mac.

Uwe

Quote:

---

Originally Posted by Uwe

Please tell me the reason for the bad linker command - I don't have a Mac.

---

I'm afraid, I never had to debug such linker problems, therefore I am not sure how to find the reason. Would you tell me what to do?

This is no linker problem - it's a problem of the linker command in the Makefile, that is generated by qmake. So you need to fine out which line in the qwt project files are responsible for the bad linker options.

I guess you have to check "qtAddLibrary", that is implemented in <qtdir>/mkspecs/features/qt_functions.prf.

Uwe

Quote:

---

Originally Posted by Uwe

This is no linker problem - it's a problem of the linker command in the Makefile, that is generated by qmake. So you need to fine out which line in the qwt project files are responsible for the bad linker options.

---

After some investigation I think I have found the problem. On Mac OS X, the linker is looking for the qwt libraries in /Libary/Frameworks/qwt.framework/, and with the current build configuration, no such framework is created. I managed to successfully compile the designer plugin and examples by doing the following:

First, I deactivated the compilation of examples and plugin and added the following line to the src.pro file:

Code:

---

CONFIG            += lib_bundle

---

This activates the creation of the needed framework. Now I compiled and installed as usual. Now the framework folder is in /usr/local/qwt-6.0.0-rc1/lib/qwt.framework/.

I moved the folder to /Library/Frameworks and recompiled qwt, but now with examples and designer plugin activated. Now everything compiled without errors.

But, unfortunately, I have not yet found a solution on how to make the linker search for the framework in the build directory, since at compile-time the framework cannot be where the linker expects it.

PS: Of course directly specifying the location of the library (LIBS +=) would also solve the problem.

Quote:

---

Originally Posted by mariposa

PS: Of course directly specifying the location of the library (LIBS +=) would also solve the problem.

---

You find "LIBS += " lines in examples.pri ( for building the examples ) and designer.pro ( for the designer ). When building an application against an installed Qwt package - by adding "CONFIG += qwt" - qwt.prf is included, where you also find a "LIBS *= ..." line.

Why do these lines result in an empty -L and -F linker option in your Makefile ?

Uwe

Quote:

---

Originally Posted by Uwe

Why do these lines result in an empty -L and -F linker option in your Makefile ?

---

I am not sure, at first glance, it should work. I tried the following: After commenting out "qtAddLibrary(qwt)" in examples.pri and designer.pro and chnaging the LIBS line to "LIBS += -L$${QWT_ROOT}/lib -lqwt" (in both files) everything compiles fine.

Manually adding linker commands for all types of platforms and debug/release combinations is what I did in Qwt 5. Fortunately in Qt4 this is not necessary anymore because of qtAddLibrary.

Please look into the implementation of qtAddLibrary ( in qt_functions.prf ) and check why it doesn't work in your environment.

Uwe

Quote:

---

Originally Posted by Uwe

Please look into the implementation of qtAddLibrary ( in qt_functions.prf ) and check why it doesn't work in your environment.

---

I'm trying to understand the code of the qt_functions.prf file, but since I'm very new to programming, this is not that easily done. But I hope that I can work it out.

My experience was very good. ( Windows 7, msvc2005, Qt 4.7.0)

Built and installed with no problems. In case I did not build and install in normal manner, this is what I did:

1. Set my QWT_INSTALL_PREFIX in qwtconfig.pri to the location I installed Qt 4.7.0. I did not change anything else.

2. Ran the following sequence from Visual Studio 2005 Command Prompt:
qmake -recursive qwt.pro
nmake
nmake install


3. Manually copied qwt.dll from the lib directory of my install location to the bin directory.


Ran QtDesigner, and qwtPlot widgets appearred correctly in the designer. Ran some examples made during the build, and they ran fine.

So, all in all, it was the simplest build and install I've ever had.

Cheers

Quote:

---

Originally Posted by Uwe

Please look into the implementation of qtAddLibrary ( in qt_functions.prf ) and check why it doesn't work in your environment.

---

I did not completely understand every detail that happens in the qtAddLibrary function, but I think I found out what causes the problem:

Code:

---

INCLUDEPATH -= $$QMAKE_INCDIR_QT/$$1
    INCLUDEPATH = $$QMAKE_INCDIR_QT/$$1 $$INCLUDEPATH
 
    LIB_NAME = $$1
    unset(LINKAGE)
 
 
 mac {
       CONFIG(qt_framework, qt_framework|qt_no_framework) { #forced
          QMAKE_FRAMEWORKPATH *= $${QMAKE_LIBDIR_QT}
          FRAMEWORK_INCLUDE = $$QMAKE_LIBDIR_QT/$${LIB_NAME}.framework/Headers
          !qt_no_framework_direct_includes:exists($$FRAMEWORK_INCLUDE) {
             INCLUDEPATH -= $$FRAMEWORK_INCLUDE
             INCLUDEPATH = $$FRAMEWORK_INCLUDE $$INCLUDEPATH
           }
           LINKAGE = -framework $${LIB_NAME}$${QT_LIBINFIX}
        } else:!qt_no_framework { #detection
           for(frmwrk_dir, $$list($$QMAKE_LIBDIR_QT $$QMAKE_LIBDIR $$(DYLD_FRAMEWORK_PATH) /Library/F$
              exists($${frmwrk_dir}/$${LIB_NAME}.framework) {
                QMAKE_FRAMEWORKPATH *= $${frmwrk_dir}
                FRAMEWORK_INCLUDE = $$frmwrk_dir/$${LIB_NAME}.framework/Headers
                !qt_no_framework_direct_includes:exists($$FRAMEWORK_INCLUDE) {
                  INCLUDEPATH -= $$FRAMEWORK_INCLUDE
                  INCLUDEPATH = $$FRAMEWORK_INCLUDE $$INCLUDEPATH
                }
                LINKAGE = -framework $${LIB_NAME}
                break()
              }
           }
       }
    }

---

The variable $$1 gets the value "qwt" and this is written into the variable LIB_NAME.

In every outcome for "mac" the LINKAGE option "-framework qwt" is thereofore added as compiler option. This causes the linker to look for the folder "qwt.framework" in the $$QMAKE_LIBDIR_QT and this is simply not present. Therefore the linking stops with the corresponding error.

But unfortunately I see no way in specifying a "custom" place (namely ../lib) to look for the framework. It seems to be the intention of this function to look in the system framework directory for the specified framework. All options that are set using the "LIBS" variable are not considered for the addition of the "-framework" flag.

But (as I already said) my experince is negligible and therefore my "analysis" of the error might be totally wrong.

Hello!
Just like gedrite I'm on Win7 but I'm using the SDK-install of Qt.

I've managed to build qwt 6 using both nmake and mingw. Either way I'm able to compile and run the examples from Qt Creator but in neither case am I able to get the widgets to show up in the Creator (Form Editor) area for drag-and-drop-placing.
Qwt is not listed at all in the Help->About plugins-menu.

I've put the qwt_designer_plugin-files in the Qt\2010.05\bin\designer-folder but nothing shows up in Creator/Designer.

What might be wrong?

Cheers!
/Tottish

Quote:

---

Originally Posted by mariposa

But unfortunately I see no way in specifying a "custom" place (namely ../lib) to look for the framework. It seems to be the intention of this function to look in the system framework directory for the specified framework. All options that are set using the "LIBS" variable are not considered for the addition of the "-framework" flag.

---

Doesn't qtAddLibrary iterate over the path stored in the environment variable DYLD_FRAMEWORK_PATH ? Also manually setting "QMAKE_FRAMEWORKPATH *= ..." might help.

But back to your initial posting: when you don't set "CONFIG += lib_bundle" and also remove "CONFIG += silent" from qwtbuild.pri - how does the failing linker command look like ?

Uwe

Quote:

---

Originally Posted by Uwe

But back to your initial posting: when you don't set "CONFIG += lib_bundle" and also remove "CONFIG += silent" from qwtbuild.pri - how does the failing linker command look like ?

---

The failing command is the following:

Code:

---

g++ -headerpad_max_install_names -single_module -dynamiclib -o libqwt_designer_plugin.dylib debug/qwt_designer_plugin.o debug/qwt_designer_plotdialog.o debug/moc_qwt_designer_plugin.o debug/moc_qwt_designer_plotdialog.o debug/qrc_qwt_designer_plugin.o  -F/Library/Frameworks -L/Library/Frameworks -L../lib -framework qwt -L/tmp/qt-stuff-6474/source/qt-everywhere-opensource-src-4.7.0/lib -F/tmp/qt-stuff-6474/source/qt-everywhere-opensource-src-4.7.0/lib -framework QtDesigner -framework QtScript -framework QtXml -framework QtGui -framework QtCore 
ld: framework not found qwt
collect2: ld returned 1 exit status
make[2]: *** [plugins/designer/libqwt_designer_plugin.dylib] Error 1
make[1]: *** [debug-all] Error 2
make: *** [sub-designer-make_default-ordered] Error 2

---

As far as I understand ( without knowing much about frameworks on the Mac ) the commands generated by qtAddLibrary depend on the qmake variable qt_framework. ( Guess whether it is enabled depends on how Qt had been built. )

So the first thing should be to add the following to src.pro:

Code:

---

CONFIG(qt_framework, qt_framework|qt_no_framework) {
 
    CONFIG += lib_bundle
}

---

But what has to be in this bundle ? Could you check what changes, when you use the following sequence:

Code:

---

CONFIG(qt_framework, qt_framework|qt_no_framework) {
 
    CONFIG += lib_bundle
 
    FRAMEWORK_HEADERS.version = Versions
    FRAMEWORK_HEADERS.files   = $${HEADERS}
    FRAMEWORK_HEADERS.path    = Headers
    QMAKE_BUNDLE_DATA += FRAMEWORK_HEADERS
}

---

What has happened after you have build the qwt library ( in src ) and what is installed where, when you do "make install" then ?

Uwe

PS: Is nobody out there knowing about Mac frameworks and qmake ?

Quote:

---

Originally Posted by Uwe

What has happened after you have build the qwt library ( in src ) and what is installed where, when you do "make install" then ?

---

My investigation has led to the following results:

(just to mention: to make it compile I disabled the designer_plugin and the examples, furthermore I added the release libraries to the config since they are not built by default; I didn't change anything else)

If you add "lib_bundle" to the config (as in your posted code), then in the lib-directory a folder "qwt.framework" is created which is copied to "/usr/local/qwt-6.0.0-rc1/lib" by the install script. The folder contains the files depicted in this screenshot:

Attachment 5319

By the way: the folder is absolutely identical if the variable declarations after "CONFIG += lib_bundle" (in your post) are omitted. The values of these variables already seem to be appropriately set.

If you do not specifiy the lib_bundle option, no "qwt.framework" folder is created and the "/usr/local/qwt-6.0.0-rc1/lib" folder looks the following:

Attachment 5320

The rest of the "/usr/local/qwt-6.0.0-rc1/" folder is identical no matter if "lib_bundle" is set or not. It contains the subfolders "docs" "features" "include" (with all header files) and the already mentioned "lib" folder.

So the framework-folder basically contains the release and debug library and "Headers" file which is a symlink to "Versions/6/Headers" (a folder that does not exist).

PS: The qwt.framework-folder seems to be "okay" that way, because if I move it manually to "/Library/Frameworks", the linking no longer fails.

Quote:

---

Originally Posted by Tottish

Hello!
....
Qwt is not listed at all in the Help->About plugins-menu.

I've put the qwt_designer_plugin-files in the Qt\2010.05\bin\designer-folder but nothing shows up in Creator/Designer.
....

/Tottish

---

My plugin does not listed in Help->About Plugins either. However, in Tools->FormEditor->About Qt Designer Plugins, the qwt plugin does show up as being installed. You should look there to see if it lists the dll at all.

My qwt_designer_plugin.dll appears in my QtCreator-2.0.1/bin/designer directory, which should be equivalent to your location, so I'm not sure why yours does not show up, as mine shows up fine.

I'm reading elsewhere where people, in a general sense, are having problems when the plugin dll's are built in mingw whereas the QtCreator is built with visual studio, and vice-versa, so perhaps make sure both are built with the same tool chain.

Good luck.

Quote:

---

Originally Posted by mariposa

If you add "lib_bundle" to the config (as in your posted code), then in the lib-directory a folder "qwt.framework" is created which is copied to "/usr/local/qwt-6.0.0-rc1/lib" by the install script.

---

What about "/usr/local/qwt-6.0.0-rc1/include" - I hope installing the headers there too is omitted in case of "lib_bundle" ?

Quote:

---

Originally Posted by mariposa

The qwt.framework folder seems to be "okay" that way, because if I move it manually to "/Library/Frameworks", the linking no longer fails.

---

O.k. - when you don't move the qwt.framework folder how can you build against it ?

Qwt 6 supports qmake features, what means that a couple of qwt specific settings are loaded from a file qwt.prf, when you add "CONFIG += qwt" to your application qmake project file. But before building your application Makefiles you have to configure qmake, so that it can find qwt.prf in /usr/local/qwt-6.0.0-rc1. ( See http://doc.qt.nokia.com/4.7/qmake-ad...ation-features ).

What happens, when you use the following qwt.prf ?

Code:

---

include ( ./qwtconfig.pri )
 
QMAKE_FRAMEWORKPATH *= $${QWT_INSTALL_PREFIX}
qtAddLibrary(qwt)

---

Beside QMAKE_FRAMEWORKPATH qtAddLibrary(qwt) also checks the DYLD_FRAMEWORK_PATH environment variable. By setting it qmake should be able to find a framework folder at any other place too:

Code:

---

export DYLD_FRAMEWORK_PATH=...
qmake

---

Uwe

Quote:

---

Originally Posted by Uwe

What about "/usr/local/qwt-6.0.0-rc1/include" - I hope installing the headers there too is omitted in case of "lib_bundle" ?

---

No, the headers are always in "/usr/local/qwt-6.0.0-rc1/include", even if lib_bundle is set.

Quote:

---

Originally Posted by Uwe

O.k. - when you don't move the qwt.framework folder how can you build against it ?

---

I think one would have to specify the location of the framework with the -F option.

Quote:

---

Originally Posted by Uwe

What happens, when you use the following qwt.prf ?

---

I added the line "QMAKE_FRAMEWORKPATH *= $${QWT_INSTALL_PREFIX}" to the qwt.prf but the very same error (framework not found) persists. But this should not be unusual since at compile time, the framework is not yet installed in $${QWT_INSTALL_PREFIX}.

I also tried exporting the DYLD_FRAMEWORK_PATH variable with the path to the lib-folder, but it did not work either.

Quote:

---

Originally Posted by mariposa

No, the headers are always in "/usr/local/qwt-6.0.0-rc1/include", even if lib_bundle is set.

---

Ok then I need to remove the install directive for the headers in src.pro in case of qt_framework.

Quote:

---

Originally Posted by mariposa

I added the line "QMAKE_FRAMEWORKPATH *= $${QWT_INSTALL_PREFIX}" to the qwt.prf but the very same error (framework not found) persists. But this should not be unusual since at compile time, the framework is not yet installed in $${QWT_INSTALL_PREFIX}.

---

qwt.prf is for building your application after qwt has been installed. So my question was about what happens, when you have changed qwt.prf + built and installed everything and then you try to build your application with "CONFIG += qwt".

About building qwt: I thought you could build designer plugin and examples successfully when "CONFIG += lib_bundle" was added without any further changes ?

If not the local directory of the framework ( in the build directory ) needs to be added to QMAKE_FRAMEWORKPATH in the project files used for building qwt. Please try this.

Uwe

Quote:

---

Originally Posted by Uwe

qwt.prf is for building your application after qwt has been installed. So my question was about what happens, when you have changed qwt.prf + built and installed everything and then you try to build your application with "CONFIG += qwt".

---

Ah, sorry for the misunderstanding. I tried it, and the linking aborts with "ld: symbol(s) not found" (the messages before this "last" error message are referring to the unknown qwt-class symbols, I think pasting them doesn't make much sense)

Quote:

---

Originally Posted by Uwe

About building qwt: I thought you could build designer plugin and examples successfully when "CONFIG += lib_bundle" was added without any further changes ?

---

No, this only works if I move the framework-folder manually to "/Library/Frameworks". I have not yet managed to make the compiler "automatically" look in "/usr/local/qwt-6.0.0-rc1/".

Quote:

---

Originally Posted by Uwe

If not the local directory of the framework ( in the build directory ) needs to be added to QMAKE_FRAMEWORKPATH in the project files used for building qwt. Please try this.

---

I already had tried all variants of directories (including the one in the build directory), without success.

Thanks for your reply, gedrite!
I will try a bit more in a few days and if I fail I will start a new thread listing all my attempts... or perhaps just switch to Linux where I have got it all to work before. =)
Anyway, thanks!

Cheers!
/Tottish

Hi Uwe,

I have been using version 6.0 off the developers svn trunk for a while now and using the qwt.prf/qwtconfig.prf method of install and configuring and it is working fine for me.

tim

Quote:

---

Originally Posted by mariposa

Ah, sorry for the misunderstanding. I tried it, and the linking aborts with "ld: symbol(s) not found" (the messages before this "last" error message are referring to the unknown qwt-class symbols, I think pasting them doesn't make much sense)

---

Ah sorry I read the wrong piece of code in qtAddLibrary. After looking around in other qmake files I would guess the -F option is what we are looking for. So f.e in designer.pro:

Code:

---

LIBS += -F$${QWT_ROOT}/lib
qtAddLibrary(qwt)

---

If this doesn't work please check the man page of ld, what the right option is to add a path to a framework.

Uwe

Hi Tim,

Quote:

---

Originally Posted by twells5

... it is working fine for me.

---

The problems of mariposa are specific for working with frameworks on the Mac. What environment are you using ?

Uwe

Quote:

---

Originally Posted by Uwe

Ah sorry I read the wrong piece of code in qtAddLibrary. After looking around in other qmake files I would guess the -F option is what we are looking for. So f.e in designer.pro:

Code:

---

LIBS += -F$${QWT_ROOT}/lib
qtAddLibrary(qwt)

---

---

Yes, that worked. I changed the "LIBS"-lines for the examples and designer-plugin as indicated in your post, and it compiled fine :)

Quote:

---

Originally Posted by Tottish

Thanks for your reply, gedrite!
I will try a bit more in a few days and if I fail I will start a new thread listing all my attempts... or perhaps just switch to Linux where I have got it all to work before. =)
Anyway, thanks!

Cheers!
/Tottish

---

See the bottome two sections on this page: http://doc.qt.nokia.com/qtcreator-2....g-plugins.html

It clearly explains the msvc/mingw & QtCreator/plugin requirements.

Quote:

---

Originally Posted by mariposa

Yes, that worked. I changed the "LIBS"-lines for the examples and designer-plugin as indicated in your post, and it compiled fine :)

---

I have updated the qmake project files according to what we have learned.

Please check SVN trunk if everything compiles and installs ( headers should be installed inside the framework only ) without any manual interfering. If successful please try to use "CONFIG += qwt" and check if this is working too.

Uwe

Quote:

---

Originally Posted by Uwe

Please check SVN trunk if everything compiles and installs ( headers should be installed inside the framework only ) without any manual interfering. If successful please try to use "CONFIG += qwt" and check if this is working too.

---

I really would like to report something better, but there are some issues left:

1.) On the mac, there is still only the debug library being built by default. For testing purposes I changed that, of course.

2.) The designer plugin links fine, but this does not apply to the examples. I had to change the "-L" option in line 20 of examples.pri to the "-F" option to make it work. After that everything compiled and installed fine.

3.) Unfortunately, now there aren't any header files installed at all. Only one header file is present in the framework directory. I have a screenshot of all contents of "/usr/local/qwt-6.0.0-svn/":

Attachment 5324

Therefore I didn't test compiling my application against the library, because (as far as I know) this won't work without header files.

Quote:

---

Originally Posted by mariposa

I really would like to report something better, but there are some issues left:

---

Writing project files for a system I don't have is somehow cumbersome - anyway some day we will have a solution.

Quote:

---

Originally Posted by mariposa

1.) On the mac, there is still only the debug library being built by default.

---

In SVN debug is always enabled, but the script, that builds packages from SVN branches modifies the pri files. This was buggy for rc1, but in this situation it is o.k.

Quote:

---

Originally Posted by mariposa

2.) The designer plugin links fine, but this does not apply to the examples. I had to change the "-L" option in line 20 of examples.pri to the "-F" option to make it work.

---

Indeed I forgot to fix the project file of the designer + made several other mistakes.

Quote:

---

Originally Posted by mariposa

3.) Unfortunately, now there aren't any header files installed at all. Only one header file is present in the framework directory. I have a screenshot of all contents of "/usr/local/qwt-6.0.0-svn/":.

---

Of course the one header is also false ...

Concerning the missing headers in the framework directory I guess when removing headers from INSTALL the behaviour of lib_bundle is affected. I hope explicitely setting QMAKE_BUNDLE_DATA will solve this problem ( the code that had no effect in your test before ).

Please check the updated SVN trunk.

Uwe

Quote:

---

Originally Posted by Uwe

In SVN debug is always enabled, but the script, that builds packages from SVN branches modifies the pri files. This was buggy for rc1, but in this situation it is o.k.

---

Ah, okay :)

Quote:

---

Originally Posted by Uwe

Please check the updated SVN trunk.

---

I checked, and it worked. It compiled at once, and all header files are at the right place. No errors during the compilation of the examples and designer plugin.

I wanted to compile my application using "CONFIG += qwt", but I always got errors about missing headers, so obviously the qwt.prf file was not found by qmake. I checked the link that you posted some time ago (on how to make qmake know where the .prf file is), but setting "QMAKEFEATURES = /usr/local/qwt-6.0.0-svn/features" in my project file did not help. I therefore just loaded the file using "load(/usr/local/qwt-6.0.0-svn/features/qwt.prf)" and omitted the "CONFIG += qwt" line. This worked.

Quote:

---

Originally Posted by mariposa

I checked, and it worked. It compiled at once, and all header files are at the right place. No errors during the compilation of the examples and designer plugin.

---

Please one more check: is everything okay, when you build Qwt for debug and release ?

Code:

---

CONFIG           += debug_and_release
CONFIG           += build_all

---

Quote:

---

I wanted to compile my application using "CONFIG += qwt", but I always got errors about missing headers, so obviously the qwt.prf file was not found by qmake. I checked the link that you posted some time ago (on how to make qmake know where the .prf file is), but setting "QMAKEFEATURES = /usr/local/qwt-6.0.0-svn/features" in my project file did not help.

---

This is a environment variable, so do "export QMAKEFEATURES = /usr/local/qwt-6.0.0-svn/features" in the shell ( assuming it is a bash ), where you execute qmake.

Or if you want to have it permanently you can set it as qmake property: "qmake -set QMAKEFEATURES /usr/local/qwt-6.0.0-svn/features".

Uwe

Quote:

---

Originally Posted by Uwe

Please one more check: is everything okay, when you build Qwt for debug and release ?

---

I checked, everything works fine.

Quote:

---

Originally Posted by Uwe

This is a environment variable, so do "export QMAKEFEATURES = /usr/local/qwt-6.0.0-svn/features" in the shell ( assuming it is a bash ), where you execute qmake.

Or if you want to have it permanently you can set it as qmake property: "qmake -set QMAKEFEATURES /usr/local/qwt-6.0.0-svn/features".

---

Ah, many thanks, now it works using the "CONFIG += qwt" option :)

Hello,

I installed qwt library and all the examples are built without problems.
However when I create a project I can't use Qwt.

I tried:
export QMAKEFEATURES = /usr/local/qwt-6.0.0/features
qmake -set QMAKEFEATURES /usr/local/qwt-6.0.0/features

The qwt.prf file is in the specified directory.

But when Im building the project I still get the error:

Quote:

---

/home/mribeiro/Qt_Projects/QwtTest/qwttest: error while loading shared libraries: libqwt.so.6: cannot open shared object file: No such file or directory
/home/mribeiro/Qt_Projects/QwtTest/qwttest exited with code 127

---

The contens of .pro file are:

Code:

---

TARGET = qwttest
 
SOURCES += main.cpp \
    mainwindow.cpp \
    plot.cpp \
    curvedata.cpp \
    signaldata.cpp
HEADERS += mainwindow.h \
    plot.h \
    curvedata.h \
    signaldata.h
 
CONFIG += qwt

---

What am I doing wrong?

[Im using Ubuntu 10.04]

Quote:

---

Originally Posted by msr

But when Im building the project I still get the error: ...

---

No you already have built your application successfully - these are error messages of the loader !

See LD_LIBRARY_PATH, ldd, ldconfig and friends.

Uwe

Thanks for your response.

I tried the following:

Quote:

---

export LD_LIBRARY_PATH=/usr/local/qwt-6.0.0/lib/
Edit file /etc/ld.so.conf and include "/usr/local/qwt-6.0.0/lib/"
Run ldconfig
Run ldconfig -n "/usr/local/qwt-6.0.0/lib"

---

None of them worked.

Any suggestions?

Im also reading http://tldp.org/HOWTO/Program-Librar...libraries.html and I think Im doing the right thing but it still doesn't work...

Code:

---

mribeiro@mribeiro-linux:/usr/local/lib/qwt-6.0.0/lib$ ls
libqwtmathml.so    libqwtmathml.so.6.0    libqwt.so    libqwt.so.6.0
libqwtmathml.so.6  libqwtmathml.so.6.0.0  libqwt.so.6  libqwt.so.6.0.0

---

Edit1:
Well, I copy-pasted libqwt.so.6 to /usr/lib and now it works. However I wonder how can I configure loader to search libraries in other directories. Any help is greatly appreciated!

Edit2: Done! For further reference: create a file "*.conf" (f.e., qwt.conf) in "/etc/ld.so.conf.d/" and add path "/usr/local/qwt-6.0.0/lib"

Good afternoon,

I am continuing a project that colleague started and he is using qwt. Now, I use a Mac whereas the project used a PC and would love to port it and use Qwt, however I am experiencing the same problems listed here from 5 years ago regarding -F and -L libraries.

I have no experience using Qt and haven't had any success making Qwt in the past few days with the help of this thread and a few others.

I am trying to use the release version of 6.1.2.

Thanks

Quote:

---

Originally Posted by Uwe

Hi Tim,


The problems of mariposa are specific for working with frameworks on the Mac. What environment are you using ?

Uwe

---

I added these lines to my designer project file but did not overcome my issue

Quote:

---

rm -f libqwt_designer_plugin.dylib
linking plugins/designer/libqwt_designer_plugin.dylib
ld: warning: directory not found for option '-L/private/tmp/qt20151227-81699-ciya8n/qt-everywhere-opensource-src-4.8.7/lib'
ld: warning: directory not found for option '-F/private/tmp/qt20151227-81699-ciya8n/qt-everywhere-opensource-src-4.8.7/lib'
mv -f libqwt_designer_plugin.dylib plugins/designer/

---

I am at a loss on how to link these files.

I would really like to stick with Qwt for this project if possible