Thank you all ! It worked !!!!!

Yes the solution was TEMPLATE = lib !

@Bonnie
.pro file is identify the path but the issue is, whenever I do rebuild at that time it is not call to linuxdeploy.sh.

I want to know if any variable is call the to script on build.

@jsulm
I need it for the rcc command. Whenever I run rcc in terminal, the binary output is re-generated, although the .qrc is the same.

Is there a way to check it in qmake for example? Like a flag?
Thanks in advance!

Thank you for the hint about 'solved'.

Just thought of something: you are trying to cross-compile a linux kernel on OS X. You should rather create a virtual machine using e.g. VirtualBox and do everything directly form Linux. That will save you time.

@ankit-thakar said:

@koahnig
Thanks for looking into problem
I got your point. and as you said i had also the same doubt that it was causing due to parallel execution of jom. as a part of solution i thought i need to change in .pro file in such a way that jom can interpret correctly,
Is this ok to implement?
I do not know, since I am not using msvc anymore. My experience is with msvc 2005 and Qt libs, but that is outdated for sure (and also hard to remember)

And one more thing also i found is that When i start debugging using nmake.exe it takes around 10 minutes to just do one step into process and when i am using jom.exe for debugging it takes only 30 sec / 1 min.
i don't know what is the story behind this....(may be jom performs parallel execution that's why)

I do not think that this is directly related. jom is basically a substitute for nmake. The only influence is can imagine is that nmake/jom is started prior to the debugging process. What could have happened is that nmake had to compile your whole project. However, 10 minutes is a pretty long time and requires a larger project I would expect. Anyway you will see in the compilation output, when all is compiled. You can compare then to the procedure with jom. The start of debugging itself should be independent of jom and nmake afterwards. I do not know that there could be an influence of multi-threading on the debugging process. But again I am not using msvc compiler.

qmake provides functions for processing the contents of variables during the configuration process.

As QMAKE_FILE_NAME is a run-time and not a configuration-time variable it cannot be edited by clean_path, seems this problem cannot be solved this way, anyone any ideas?

EDIT:

I think I finally found a proper solution:

PROTOS = interface_definitions.proto PROTOPATH = $$relative_path($$PWD, $$OUT_PWD) \

protoc is now being called this way:

protoc --cpp_out=. --proto_path=. --proto_path=../project/ ../project/interface_definitions.proto

everything works fine now!

Hi and welcome to devnet,

your project uses Qt to build so you need it.
In your case I suggest to move to CMake (but still you need to install it on the build machines)