Hi Konstantin,

Thanks for sharing your work with the community.

Given the exhaustive list of modules provided within the installers, I
can appreciate the effort.

That said, as you may know, downloading unsigned binaries to build
applications is not an option for a lot of us.

Here are few initial suggestions to improve your platform:

  * transition the website to https
  * reference the version of each packages/modules bundled in the
respective installers
  * provide the a how to understand the different between
stable/testing/unstable
  * document the convention to integrate the different module in our
existing project. For example, for CMake did you write a
<Module>Config.cmake file with each project [1] ? And similar question
for qmake ?

Good luck,
Jc

[1] http://www.cmake.org/cmake/help/git-next/manual/cmake-packages.7.html

On Thu, Sep 10, 2015 at 10:12 AM, Konstantin Podsvirov
<konstan...@podsvirov.pro> wrote:
> 10.09.2015, 16:41, "Curtis Mitch" <mitch.cur...@theqtcompany.com>:
>>> From: Konstantin Podsvirov [mailto:konstan...@podsvirov.pro]
>>>
>>> By clicking on the link, you will be able to get the installer is the same
>>> as the QtSDK and a few clicks to get the binaries, libraries and linking
>>> headers of any of the participating modules.
>>
>> But what am I even clicking the link for? What service does this thing 
>> provide?
>
> For example, You want to create a very large and useful application which 
> uses a lot of dependencies.
> And you want to deploy it on the Windows.
>
> You go to the site:
>
> http://dad.podsvirov.pro
>
> Download appropriate to your development environment setup.
>
> Quickly and easily install any required dependent modules and receives a 
> development environment, local deployment and testing.
>
> When you're finished designing, you can create compatible with this 
> environment the installer to install your application on other machines.
>
> Main technologies:
> * Development languages: C, C++ (Qt, Qml, Quick) and other
> * Project management: CMake, but can use other
> * Creating installer based QtIFW (CMake allows you to automate the process of 
> creating an installer).
>
> I answered Your question?
>
> Regards,
> Konstantin Podsvirov
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake-developers



-- 
+1 919 869 8849
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Reply via email to