[cmake-developers] [Development] [ANNOUNCE] DaD's House! (Beta)

Fri Oct 2 17:02:07 EDT 2015

Some time passed and DaD's House was much more informative!

Now on the website, you can:
- See the list of modules provided by a specific installer;
- See the list of all build-specific module;
- Show details on specific build of the specific module.

See "Details" links.

Perhaps this is the first ever web-based interface to view the information
from QtIFW binary repository.

Welcome once again DaD's House:

http://dad.podsvirov.pro

Good luck everyone!

10.09.2015, 21:09, "Konstantin Podsvirov" <konstantin at podsvirov.pro>:
> Hi, Jean-Christophe Fillion-Robin (the short name?)!
>
> Thanks for Your reply. You gave a lot of valuable advice.
>
> 10.09.2015, 17:59, "Jean-Christophe Fillion-Robin" <jchris.fillionr at kitware.com>:
>> Hi Konstantin,
>>
>> Thanks for sharing your work with the community.
>
> I'm glad to be helpful.
> Thank You for giving the community such a useful tool like CMake.
>
>> Given the exhaustive list of modules provided within the installers, I
>> can appreciate the effort.
>
> I agree, thanks for the rating.
> It really is now a lot of work.
>
> But now better order and it was good.
>
> Early in the development of their projects I was trying to find ABI compatible
> binaries for dependent modules. And pretty soon I realized that this is not always possible.
>
> Then I began to study dependent projects and try to build them yourself. Then for each project I reinvent the wheel on
> adding dependencies during development and deployment.
>
> Meanwhile I already owned a nice CMake and he helped me a lot.
>
> Routine work became more and more. I tried a few different frames to create the installers - they were all completely different and I didn't like.
>
> When QtIFW, then I read its documentation and stasis realized that his
> need to make friends with CMake (or Vice versa).
>
> This was the prerequisite for the appearance of Dad's project.
>
> It's just tie a big story, which I hope some will live with me together.
>
>> That said, as you may know, downloading unsigned binaries to build
>> applications is not an option for a lot of us.
>
> Yes, I understand that. The trust of our users is very important.
> But as one cartoon character: I'm not a magician - I'm just learning.
>
> Well I know how to build projects of their own and others :-)
>
> To sign application I haven't learned.
> We are talking about signing applications or installers themselves within modules?
>
>> Here are few initial suggestions to improve your platform:
>>
>> * transition the website to https
>
> It's all about the confidence of users, as mentioned above.
> I need to get the certificate.
> Understandable comment. Will try to organize.
>
>> * reference the version of each packages/modules bundled in the
>> respective installers
>
> I thought about it. You are not the first who comes to me!
> The list of available module versions and can be seen by running the particular setup on the feature selection page, but that's not enough.
> Of course, users want to see it before downloading the installer.
> The proposal was adopted. I'll think how to do it.
>
>> * provide the a how to understand the different between
>> stable/testing/unstable
>
> For a quick start, I refer everyone to the website of the Debian community
>
> http://debian.org
>
> I will try to add a description on the website.
>
>> * 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 ?
>
> I plan to have a section on the website with more detailed information for each module.
> Now on the page with the list of modules I have provided a link to the native source of information.
>
> The need to create a CMake configuration for modules is controversial.
> Each project is independent and most of them are family managed by CMake scripts. Provide Some package configurations to import. Some can be found with the Find modules distributed by CMake.
>
> Presents the installers are just transferral these projects
> a local directory of the user. Further, their use is no different, from say download from the original site.
>
>> Good luck,
>> Jc
>
> Thanks for valuable advice.
>
> I'm doing a project in my spare time. And I will try to improve it and continue to share with the community.
>
> Now I'm building modules in an automated way. Not always the case goes smoothly. Some modules require minor tweaks.
> The real CI is still far. But I hope with time I'll come to that.
>
> I apologize for linguistic errors. English is not my native language.
>
>> [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
>> <konstantin at podsvirov.pro> wrote:
>>> 10.09.2015, 16:41, "Mitch Curtis" <mitch.curtis at theqtcompany.com>:
>>>>> From: Konstantin Podsvirov [mailto:konstantin at 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
>
> Regards,
> Konstantin Podsvirov
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

Regards,
Konstantin Podsvirov