Manual make install step for static libraries with a .pro file
-
Hi,
Is that static library part of your main Qt Project ? e.g. as a subdir
-
My static library is not part of my qt app. It is built separately as a static library using qt. My app only uses the static library for certain functionality but it is only dependent on one header file from the library which is the library's API/interface. And this is the header file I want to provide into the build directory as a part of building the static library.
Imagine a situation where I tell you as my co-developer that you need to use my library as a part of your app. Qt is great to provide the option that I can add a install step detail by using INSTALL += . I am using this to specify my header to be installed as part of the build but I wish to avoid the manual step so that my co-developer does not need add a install step manually to build my library in his qt creator.
Is there some config or something I can add to my library's .pro which enforces this make install automatically.. Or is there some completely different way to share my static library's header ? Surely should be a way.. aah.. I am sort of new to this
-
Since that library is also built with Qt, why not make it part of your current project through a git submodule and use the SUBDIR template to build everything together ?
That way all your co-worker will use the same version of that static library, there's no need to install it and you can easily point your current project to the needed header.
-
sorry to be late in replying. I am not very sure about the git submodule process. I need to check that out. If this cannot be handled by adding any code to mu library's .pro file, then I would have to look into the git submodule way.
May be making the "make install" step automatic is not in the purview of a project .pro file.. -
http://www.vladislavonline.com/installing-library-header-files-with-qmake/
Just to clarify readers, Step # 2 in above link is what I wish my co-developers to omit. So that they don't have to do add "make install" step manually. It should come inherent with the library.
-
I figured this out by some more searching around. QMAKE_POST_LINK does something that I was looking for. We can copy a particular file to the build directory or somewhere else by putting it into QMAKE_POST_LINK. Like I added the following line to my .pro file
QMAKE_POST_LINK = cp "mylibrary_header" "destination_directory"
-
Again, you are complicating your life for that static library. Integrating it in your current project will avoid your fellows developer to have to build and install it before building the application. Also, that will make their life easier if it's also an actively developed library. With the submodule you can ensure that they are getting a version of this library that is known to work with the application. They won't have to check an external library state + rebuild/install.
By the way, your current QMAKE_POST_LINK will only work on systems where there's a
cpcommand. -
Very good points indeed @SGaist. I will take that down. I need to look into how to make it as a git submodule which looks to be much better approach.
Thanks for your dude. Appreciate
