You are not logged in.

Problems with qmake

Dear visitor, welcome to QtForum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

flowerJT

Trainee

  • "flowerJT" is male
  • "flowerJT" started this thread

Posts: 73

Location: Berlin, Germany

  • Send private message

1

Thursday, February 10th 2005, 1:06pm

Problems with qmake

Hi,

we're using qmake to automatically generate our Makefiles. We have shared libs as well as static ones to link in our executable. The problem is that if one of the static libs has changed for some reason (i.e. lib is newer than executable) and we run make, it says "nothing to be done for ....".
In our .pro-file:

LIBS += -L./lib

LIBS += -lstaticLib
LIBS += -lsharedLib

Does anyone know what's wrong with that?


Thanks in advance

Jupp Tscheak

This post has been edited 1 times, last edit by "flowerJT" (Feb 10th 2005, 1:18pm)

wysota

Sage

  • "wysota" is male

Posts: 4,276

Location: Warsaw, POLAND

  • Send private message

2

Thursday, February 10th 2005, 1:24pm

RE: Problems with qmake

Things you put into LIBS are not part of your project, thus make doesn't check if they change. If you want it to work that way, you have to force a dependency between the project executable (or one of its object files) and libraries which you keep in LIBS. You could try to put each library into HEADERS variable, this might create such dependency.
QtCentre.org - the largest Qt community site and forum where questions get answered

jacek

Master

  • "jacek" is male

Posts: 2,729

Location: Warsaw, Poland

  • Send private message

3

Thursday, February 10th 2005, 1:51pm

RE: Problems with qmake

Maybe this will help:

Quoted

From qmake Command Reference:
PRE_TARGETDEPS
All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is support internally by these build tools, this is usefull for explicitly listing dependant static libraries.
This list will go before all builtin dependencies.
You can meet me at Qt Centre - The Ultimate Qt Community site.

flowerJT

Trainee

  • "flowerJT" is male
  • "flowerJT" started this thread

Posts: 73

Location: Berlin, Germany

  • Send private message

4

Thursday, February 10th 2005, 5:05pm

Thanks for responding...

Jacek, your suggestion sounded promising ... Unfortunatly it did not work. I tried several notations like libStatic.a, Static, Static.a, etc. without result.
Probably we'll have to do a "make clean" in future ;)
Nevertheless thanks for your help!

Jupp Tscheak

wysota

Sage

  • "wysota" is male

Posts: 4,276

Location: Warsaw, POLAND

  • Send private message

5

Thursday, February 10th 2005, 5:29pm

Quoted

Originally posted by flowerJT
Thanks for responding...

Jacek, your suggestion sounded promising ... Unfortunatly it did not work. I tried several notations like libStatic.a, Static, Static.a, etc. without result.
Probably we'll have to do a "make clean" in future ;)
Nevertheless thanks for your help!

Jupp Tscheak


You probably have to use an absolute path. Make has to know exactly where those files are.
QtCentre.org - the largest Qt community site and forum where questions get answered

flowerJT

Trainee

  • "flowerJT" is male
  • "flowerJT" started this thread

Posts: 73

Location: Berlin, Germany

  • Send private message

6

Tuesday, May 10th 2005, 8:09pm

After losing sight of this problem, my workmate reminded me to solve this problem and i finally did so:

To create dependencies just include TARGETDEPS += libFoo.a to your .pro-file.

Best regards

Jupp Tscheak