How to name makefile in .pro file?

[DigiDrag]

Hi

I want to cross-compile a QT project.
And I am accessing the same project folder from different OS over the network.
And this leads to a problem:
All OS are using the same makefile name 'Makefile' and this leads to problems as QT does not re-create that file on the next OS.


Does anyone know how I can specify the makefile name in the .pro file?


I want to get something like this:
mac {
make_name = Makefile_Mac
} else:unix {
make_name = Makefile_Linux
} else {
make_name = Makefile_Win
}


thanks,
dd

[mcosta]

You can set the QMAKE_MAKEFILE variable!

mac {
QMAKE_MAKEFILE = Makefile_Mac
} else:unix {
QMAKE_MAKEFILE = Makefile_Linux
} else {
QMAKE_MAKEFILE = Makefile_Win
}

mac {
QMAKE_MAKEFILE = Makefile_Mac
} else:unix {
QMAKE_MAKEFILE = Makefile_Linux
} else {
QMAKE_MAKEFILE = Makefile_Win
}

To copy to clipboard, switch view to plain text mode 

[DigiDrag]

Hi

Thanks so far, got half the solution.

It does not seem to work with the QT Creator.
It now generates the makefile with a different name, but QT Creator does not start make with the new filename...

And I cannot define make arguments in the .pro file.
And the arguments in the QtCreator file are not platform-dependants.
And I am also not able to use and system-wide variable as make argument in QtCreator as it is not resolved...

[wysota]

Wouldn't it be easier to do shadow builds so that makefiles for each platform end up in different directories? Your problem would vanish instantly.

[DigiDrag]

Wouldn't it be easier to do shadow builds so that makefiles for each platform end up in different directories? Your problem would vanish instantly.

I found the option to enable and change a shadow build directory in the QT Creator.
But again, this setting is the same on all platforms...

[ChrisW67]

Does something like this fly for you?

macx { 
  MOC_DIR = build_mac
  OBJECTS_DIR = build_mac
  RCC_DIR = build_mac
  UI_DIR = build_mac
} else:win32 { 
  MOC_DIR = build_win32
  OBJECTS_DIR = build_win32
  RCC_DIR = build_win32
  UI_DIR = build_win32
} else {
  MOC_DIR = build_unix
  OBJECTS_DIR = build_unix
  RCC_DIR = build_unix
  UI_DIR = build_unix
}

macx { 
  MOC_DIR = build_mac
  OBJECTS_DIR = build_mac
  RCC_DIR = build_mac
  UI_DIR = build_mac
} else:win32 { 
  MOC_DIR = build_win32
  OBJECTS_DIR = build_win32
  RCC_DIR = build_win32
  UI_DIR = build_win32
} else {
  MOC_DIR = build_unix
  OBJECTS_DIR = build_unix
  RCC_DIR = build_unix
  UI_DIR = build_unix
}

To copy to clipboard, switch view to plain text mode 

You leave Qt Creator's shadow build feature off in this case.

[DigiDrag]

Hi

Thanks, but I am already using these parameters.
This works fine, it is just the makefile itself.

If I compile on Mac and then try to compile on Linux, then the makefile is not re-generated.
And therefore the MOC_DIR, OBJECTS_DIR, RCC_DIR, UI_DIR are not updated in the makefile...

[wysota]

Honestly I would just rerun qmake and forget about the problem.

[miwarre]

I have the same problem.

Honestly I would just rerun qmake and forget about the problem.

This would be sub-optimal; and what is the point of an automated make, if you have to run some (quite important) step manually?

Anyway, I tried the above solution and it is not an out-of-source (or shadow) build: all makefile's are in the same directory of each .pro as well as the debug and release sub-dirs with the executable(s).

So, I would re-formulate the question in this way:

Is there a way to have a REAL out-of-source AND multi-platform build by using .pro settings and without using the Shadow build setting of Qt Creator (which IS out-of-source but IS NOT multi-platform) ?

The best of any possible world would be to be able to launch the build from within Qt Creator itself, with just a click on the the 'hammer' button...

Thanks!!

M.

[wysota]

This would be sub-optimal; and what is the point of an automated make, if you have to run some (quite important) step manually?

What is the point of placing intermediate files (such as the Makefile) on a shared remote disk?

Is there a way to have a REAL out-of-source AND multi-platform build by using .pro settings and without using the Shadow build setting of Qt Creator

I don't really see a point of doing that in a single directory. But if you insist... Use the -o parameter of qmake and -f parameter of make.

[miwarre]

What is the point of placing intermediate files (such as the Makefile) on a shared remote disk?
...
I don't really see a point of doing that in a single directory. But if you insist... Use the -o parameter of qmake and -f parameter of make.

Hmmm, am I missing something? It is not me, it is Qt Creator which insists on creating makefile's in the same folder as the .pro's files.

I tried any combination of .pro settings I could think of and none seems to work:

Using either MAKEFILE = Makefile_<platform> or QMAKE_MAKEFILE = Makefile_<platform> or both, 6 Makefile's are created in the .pro dir: Makefile, Makefile.Debug, Makefile.Release, Makefile_<platform>, Makefile_<platform>.Debug, Makefile_platform>.Release.

Using something in the line of [QMAKE_]MAKEFILE = ../build_<platform>/Makefile simply does not work: at some point some of the programmes involved complains about there being no target or no makefile.

But if you insist... Use the -o parameter of qmake and -f parameter of make.

Which parameters cannot be places in a .pro file, I assume. They have to be placed in Qt Creator project configuration dialogues (Ctrl-4) whose settings are common across all platforms and we are at square one again...

Let me re-state my goals once again:

Thesis: I have one src dir with all the sources and I access this dir from BOTH Windows and Linux Qt;
Goal 1) I would like no leftover step from the build on one platform to be mistaken for an already performed step by the other platform
Goal 2) I would like no intermediate file to pollute the src dir
Goal 3) I would like to work from inside an IDE, Qt Creator being the obvious choice in this case.

It seems to me a reasonable pretense, isn't it?

Yours very confused,
M.