03 ----- COMPUTREE PLATFORM ----- » A - Computree Platform Core » ComputreeDevTools

Thats amazing if it works. Thanks...

Hello,

Sorry, but this topic is not in the good place. Here is the user forum.
This question has to be discussed here, in the developper forum:
http://rdinnovation.onf.fr/projects/computreedevtools/boards

Moreover the solution you give is NOT the good one.
To have customs paths you just have to use user_path.pri files, as described in the Computree compilation documentation, that you can find here:
http://rdinnovation.onf.fr/projects/computreedevtools/wiki/En_quickstart

So, to avoid mistakes in the future, I will remove your attached files.

Best regards.
Alexandre Piboule.

Hello again,

I’ve moved this subject to development forum, to avoid spaming Computree users with development and compilation questions.

To take account for you proposal Francis, I’m working on the modification of the default_path files, to avoid the necessity of using user_path files (not versioned and so able to manage local specificity of dependencies installation) , when installing Computree according to the dedicated wiki.
The commit is coming now.
I will also modify the wiki, to simplify things.

Thanks for the proposal. The previous paths used in the default_path files, were ones used by defaults by each dependent library. These files were written before I proposed the compilation wiki.
But now this wiki exist it is indeed better to directly have concordant default_path files.

For the future, please:
1) Post compilation questions in this development forum, because the majority of the 400+ followers of this forum don’t compile Computree themselves.
2) For any modification proposal of the core (even for the compilation process), please first ask to me or Michael. We will try to answer quickly and take account for your proposals each time it is possible.

Best regards.
Alexandre Piboule.

Commit done and wiki updated.

I confirm that the changes works. Thinking at loud, it would be nice to set the directory containing the dependencies in a single variable, instead of overriding each .pri files individually. Cheers!

I understand now why the .qmake.conf is not the proper solution. If a subproject (i.e. a plugin) is directly opened, then the .qmake.conf at the root directory is not taken into account. Thanks for your fix!