Eike, Thanks, it was a good advice. Shall we write it down on some wiki page, what do you think?
Kakadu On Wed, Nov 23, 2016 at 6:54 PM, Eike Ziller <[email protected]> wrote: > >> On Nov 23, 2016, at 4:38 PM, Kakadu <[email protected]> wrote: >> >> Hey, folks >> >> At the moment we need to compile QtCreator itself to setup right paths >> and compile a plugin. I'm kind of curious is it possible to compile >> QtCreator, do `make install` and do `make install-some-dev-files` >> after that to be able not to store whole source and build files that >> are required to compile a pluign (I think only some headers and shared >> objects are really required). >> >> This thing should generally be possible because GNU/Linux -dev >> packages suit the same purpose. I just do not want to dive into >> packaging scripts... Maybe you have this thing described in some wiki >> page which I'm not aware about? > > Check out <qtcreator_src>/scripts/createDevPackage.py > Takes a source tree and a build tree and collects all things that are need > besides the result of ‘make install’. > I.e. if you set IDE_SOURCE_TREE/QTC_SOURCE to the result of > createDevPackage.py and IDE_BUILD_TREE/QTC_BUILD to the result of ‘make > install’, you should be able to build a plugin against that, without the need > to keep the whole build directory (or source directory). > Should also work on all platforms (Lin/Win/mac). > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > [email protected] > http://qt.io > Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B > > > > _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
