cannot find library...
-
@AnneRanch said in cannot find library...:
It is pretty useless
Yes. Because you posted the wrong file.
We need the.profile containinglibBT_Utility.so.1in a line starting withLIBS +=Have you located
libBT_Utility.so.1in your file system?@Axel-Spoerl Sorry . I got involved in another issue.
There is no .so info when "add library" is used
HERE
( I believe INCLUDEPATH can be printed but I forgot how )unix:!macx: LIBS += -L$$OUT_PWD/../MS_BASE_CLASS/ -lMS_BASE_CLASS
INCLUDEPATH += $$PWD/../MS_BASE_CLASS
DEPENDPATH += $$PWD/../MS_BASE_CLASSYes. Because you posted the wrong file.
We need the .pro file containing libBT_Utility.so.1 in a line starting with LIBS +=Have you located libBT_Utility.so.1 in your file system?
-
@Axel-Spoerl Sorry . I got involved in another issue.
There is no .so info when "add library" is used
HERE
( I believe INCLUDEPATH can be printed but I forgot how )unix:!macx: LIBS += -L$$OUT_PWD/../MS_BASE_CLASS/ -lMS_BASE_CLASS
INCLUDEPATH += $$PWD/../MS_BASE_CLASS
DEPENDPATH += $$PWD/../MS_BASE_CLASSYes. Because you posted the wrong file.
We need the .pro file containing libBT_Utility.so.1 in a line starting with LIBS +=Have you located libBT_Utility.so.1 in your file system?
@AnneRanch
Hi Anne,hm. And could you locate any of the libraries on your drive?
(libBT_Utility.so.1orlibBT_Utility.so.1)I am insisting on that question for a number of reasons.
- Compilation and linking does quite some heavy lifting on the file system. Building on an external drive puts a bottle neck into the game. It really would be good to know, if everything the compiler says it has done is really done.
- Some of your file paths contain dates (e.g.
DEC10). Such paths might confuse the linker as well: Something expected in theDEC10tree, may have been built on another day and be in another tree, e.g.NOV17. - Maybe you have turned an existing project into a SUBDIRS project. That is likely to change a lot of relative paths.
Brgds
Axel -
A Axel Spoerl referenced this topic on