1

Topic: Switching-on of not assembled library in the VS/QtCreator-project

There is a project which uses a functional of indirect library, and there are source codes of this indirect library. As though to make so that separately not to collect library, and at once all in one project? The matter is that, program usage on different platforms that is why constant recompilation is supposed is supposed, and it would not be desirable its amount to increase twice because of necessity still separately permanently to recompile library. And still, it is necessary to have possibility easily to transfer the project from a Visual Studio on QtCreator, accordingly, it would be desirable to manage to the general approaches which is supported both in that, and in other development environment. I was tried to include simply library source codes in the project, but at compilation there were conflicts of object files because of identical names... The item with. CMake it would not be desirable to use, therefore as would wash a Visual Studio 2013 it like as does not support. Thanks.

2

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, _hum _, you wrote: __> There is a project which uses a functional of indirect library, and there are source codes of this indirect library. As though to make so that separately not to collect library, and at once all in one project? If  does not change, it is necessary to collect once simply it under each platform and everything, not? If it is used same  for  and studios problems like as are not present. It is possible to try to create the  under nuget and   on  the server then to tighten dependence therefrom (itself not ).

3

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, Kernan, you wrote: K> Hello, _hum _, you wrote: __>> There is a project which uses a functional of indirect library, and there are source codes of this indirect library. As though to make so that separately not to collect library, and at once all in one project? K> if  does not change, it is necessary to collect once simply it under each platform and everything, not? If it is used same  for  and studios problems like as are not present. At first,  changes (it too in development process), and secondly, platforms not  (the program on the given computer is necessary - compiled, launched). K> It is possible to try to create the  under nuget and   on  the server then to tighten dependence therefrom (itself not ). Looks more difficult, than library evolution.

4

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, _hum _, you wrote: __> There is a project which uses a functional of indirect library, and there are source codes of this indirect library. As though to make so that separately not to collect library, and at once all in one project? The matter is that, __> program usage on different platforms that is why constant recompilation is supposed is supposed, and it would not be desirable its amount to increase twice because of necessity still separately permanently to recompile library. If to change source codes it is not necessary, for such purposes it is possible to make a repository with ready . In a project file by default it is supposed that a repository  parallely to the project, further a way depend on a platform, an assembly type, . It is possible as . __> And still, it is necessary to have possibility easily to transfer the project from a Visual Studio on QtCreator, accordingly, it would be desirable to manage to the general approaches which is supported both in that, and in other development environment. __> I was tried to include simply library source codes in the project, but at compilation there were conflicts of object files because of identical names... If from source codes at first  library, and then with it  such problems should not be. __> the item with. CMake it would not be desirable to use, therefore as would wash a Visual Studio 2013 it like as does not support. As the variant qbs is able  projects for studio and  is supported in Kreatore.

5

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, Skorodum, you wrote: __>> I was tried to include simply library source codes in the project, but at compilation there were conflicts of object files because of identical names... S> If from source codes at first  library, and then with it  such problems should not be. How it can be organized easily transferred with VS on QtCreator a method? In VS in one  to organize two projects? __>> the item with. CMake it would not be desirable to use, therefore as would wash a Visual Studio 2013 it like as does not support. S> as the variant qbs is able  projects for studio and  is supported in Kreatore. Thanks, I will look narrowly.

6

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, _hum _, you wrote: __> Hello, Skorodum, you wrote: __>>> I was tried to include simply library source codes in the project, but at compilation there were conflicts of object files because of identical names... S>> If from source codes at first  library, and then with it  such problems should not be. __> how it can be organized easily transferred with VS on QtCreator a method? In VS in one  to organize two projects? In VS2013 it like is called a solution, instead of . And as a whole so: two projects in a solution, one your program, another is library and to register dependence in between. Approximately too most in qbs how much it I am good  a file of the project for Studio I do not know, but to make test Hello World and to look - not a problem.

7

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, _hum _, you wrote: __>>> There is a project which uses a functional of indirect library, and there are source codes of this indirect library. As though to make so that separately not to collect library, and at once all in one project? K>> if  does not change, it is necessary to collect once simply it under each platform and everything, not? If it is used same  for  and studios problems like as are not present. __> At first,  changes (it too in development process) If changes it is possible to rebuild on  the server daily or on  and to tighten time a day through  command in  script on  Pre-Compile, will be possible to make the project in a solution on a basis   these actions to produce, but will be nothing . In  it is possible to make too most. It is the normal task on CM. __> and secondly, platforms not  (the program on the given computer is necessary - compiled, launched). What does it mean? At you  from ?  them like only 3, and last two use one . K>> It is possible to try to create the  under nuget and   on  the server then to tighten dependence therefrom (itself not ). __> looks more difficult, than library evolution. Does not look. It is necessary to understand once with it, to adjust, integrate into process and all.

8

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, _hum _, you wrote: __> the item with. CMake it would not be desirable to use, therefore as would wash a Visual Studio 2013 it like as does not support. cmake certainly supports visual studio 2013: https://cmake.org/cmake/help/v3.0/gener … 02013.html so use cmake and all problems will be solved. You probably were a little tangled because of ignorance cmake. Originally cmake it was used as the generator of design files, that is the project description in a format cmake and it generates projects for eclipse/visualt studio/make/nmake etc., etc., then it became so popular that some IDE began to support it directly, CLion for example, is possible Qt Creator. The Visual Studio command too like wanted, but it in any way does not hinder to use its old method - to generate the project for IDE which use.

9

Re: Switching-on of not assembled library in the VS/QtCreator-project

Hello, _hum _, you wrote: I at first would look for this library in already ready type in one of package managers for developers  https://bincrafters.github.io or https://github.com/Microsoft/vcpkg