How to compile a project, with the same folder structure as the source code.

Good friends, today I come to the next question that has me going around for a long time.

I started developing a small application that would allow me to generate classes for PHP, where I would create all the class structure and all the dependencies that required the same, as well as the documentation.

The point is that now he created a kind of "frame" in PHP and thought about developing a small text editor that allowed me to streamline its use and how I have not worked in Qt / C ++ I thought I would do this with . The detail is in what was supposed to be something small has become a fairly large project.

The problem is the following:

I have the following project structure:

Code:

---

src/
  /addons/ // Structure to accommodate any add-ons you wish to add and / or develop for the application
    /addon_1/
      /controller/
      /model/
      /view/
    /addon_2/
      /controller/
      /model/
      /view/
    /addon_3/
      /controller/
      /model/
      /view/
  /bin/ // Main Application
    /controller/
    /model/
    /view/
  /com/ecosoftware/  // General libraries for handling the common functions of any application that has been developed
    /app/ 
    /patterns/
    /singleinstance/
    /window/
      /components/
        /expandtoolbar/
        /menubar/
        /statusbar/
        /tabbar/
        /tabpanel/
        /workspace/
      /mainwindow/
  /common/  // Libraries commonly used for the application and / or any component thereof
    /actions/
    /files/
    /language/
    /utils/
  /config/
  /data/
  /doc/
  /editor/ // Text Editor Tools
    /controller/
    /model/
    /view/

---

The point is, I want to compile the whole project, I stay the same way I have my source code.

From what I researched by different means, is that thing by the makefile, but I can not understand how.

On the other hand qMake can apparently help me with this, but in the documentation I do not know how to get the final build structure.

In addition to this, I have managed to create all my code as Dynamic libraries (to reduce the size of it, to reach 500 MB, which is not good hehehe), but adding them to the project, but to the added ones, when Compilo, tell me what to do.

To recap, How to compile my project and to stay in the same way that I have my source code.

Thanks in advance.

You basically just need a ".pro" file in each directory that has the same name as the directory itself.

Depending on whether the directory is just a container for sub directories or an actual build target, the .pro TEMPLATE type is either "subdirs" or the respective "lib" or "app".

E.g. in src/ you would have a src.pro

Code:

---

TEMPLATE = subdirs
 
SUBDIRS = addon bin com common editor

---

You can define dependencies for getting the right build order if neccessary, e..g if "bin" depends on "com" being built first this would do that

Code:

---

bin.depends = com

---

Cheers,
_

Thank you very much for your quick reply anda_skoa.

By making some tests about the structure of the project and the compilation of it, I have already achieved a pretty good approach of how I want to see the fruit of many sleepless nights hehehe.

What I had to do in effect is what you advised me and in the "final folder" the project and / or library that I want to compile.

An example of this is the following:

Code:

---

src/
  mainproject.pro
  /addons/
    /addon_1/
                 addon_1.pro
    /addon_2/
                 addon_2.pro
    /addon_3/
                 addon_3.pro
  /bin/
        addon_1.pro
  .
  .
  .

---

Thus, when compiling everything is in the place indicated, except a small detail.

I want different dynamic libraries to be in the same folder, but as they are different projects, there are the folders of the projects and within them obviously a single file that is the compiled library, not that it is my biggest problem, but the truth to me You do not see anything elegant.

I know that I can compile each project separately and append the already compiled libraries to the project, but I'm having problems adding them because compiling does not recognize the libraries, so the need to create them all within the same project.

So, if I need to make any modifications I can do it directly inside the project and not in a separate project where I have to compile and re-attach the library to the main project.

The point is, as I could do to compile several libraries in the same folder, for example:

Code:

---

Src/common/
                Library_1.so
                Library_2.so
                Library_3.so

---

Instead of

Code:

---

Src/common/
                Library_1/Library_1.so
                Library_2/Library_2.so
                Library_3/Library_3.so

---

I would have to do it in separate projects and add the libraries to the main project or there is some way to do this that I am thinking.

As I said in the first post, I read that with adjusting the makefile can be done, but the truth is not much or little like manipulating the makefile.

Thanks in advance.

You can set DESTDIR to have the final build artifact in a different directory than where the build happens.

E.g. in your Library_1.pro you could try

Code:

---

DESDIR= ..
# or
DESTDIR = ../
# or
DESTDIR = $$PWD/..

---

Cheers,
_

Many thanks anda_skoa, with your guidance and rereading the qmake documentation now if I have managed to understand how the compilation process works for an end application.

In effect with

Code:

---

DESTDIR = ../path/where/we/want/our/library/or/binary/

---

Now everything is where I want.

I hope this post will serve to anyone who has the same doubt as me.

Thank you again, theme solved.

I do not know how to put it solved in the title :(