Re: [CMake] List all packages

[Konstantin Podsvirov]

Hello, Lectem.11:43, 13 January 2019 г., Lectem : Hi, Is there a way to list all the packages (both config files and find-modules) that find_package could find ?Could we even imagine this would also permit to list the variables and targets created in it ?I think that would be a very helpful to have for debugging find_package, especially when you don’t have access to the system having issues (user bug reports for example).Cheers,LectemYou can visualize dependencies between targets with Graphvis:https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/Graphviz--With 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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Who want find_package(ImGui)?

[Konstantin Podsvirov]

Hello dear CMake users!Anybody use Dear ImGui project?Please help to review PR for add CMake support:https://github.com/ocornut/imgui/pull/1713Have a nice day!
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] [CMake] cmake-gui on windows and qt5 dlls

[Konstantin Podsvirov]

 instead or maybe prefix
>>
>>>>>> the Qt5 libs shipped with cmake-gui somehow?
>>
>>>>>>
>>
>>>>>> Thx,
>>
>>>>>> Christian
>>
>>>>>>
>>
>>>>>> --
>>
>>>>>>
>>
>>>>>> 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
>>
>>>>>
>>
>>>>>
>>
>>>>>
>>
>>>>>
>>
>>>>> --
>>
>>>>> Craig Scott
>>
>>>>> Melbourne, Australia
>>
>>>>> https://crascit.com
>>
>>>>> --
>>
>>>>>
>>
>>>>> 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
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>> --
>>
>>> Craig Scott
>>
>>> Melbourne, Australia
>>
>>> https://crascit.com
>>
>>>
>>
>>> --
>>
>>>
>>
>>> 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
> ,--
>
> 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


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

Re: [CMake] cmake-gui on windows and qt5 dlls

[Konstantin Podsvirov]

 instead or maybe prefix
>>
>>>>>> the Qt5 libs shipped with cmake-gui somehow?
>>
>>>>>>
>>
>>>>>> Thx,
>>
>>>>>> Christian
>>
>>>>>>
>>
>>>>>> --
>>
>>>>>>
>>
>>>>>> 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
>>
>>>>>
>>
>>>>>
>>
>>>>>
>>
>>>>>
>>
>>>>> --
>>
>>>>> Craig Scott
>>
>>>>> Melbourne, Australia
>>
>>>>> https://crascit.com
>>
>>>>> --
>>
>>>>>
>>
>>>>> 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
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>> --
>>
>>> Craig Scott
>>
>>> Melbourne, Australia
>>
>>> https://crascit.com
>>
>>>
>>
>>> --
>>
>>>
>>
>>> 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
> ,--
>
> 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


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

Re: [cmake-developers] Fwd: [CMake] cmake-gui on windows and qt5 dlls

[Konstantin Podsvirov]

14.08.2017, 16:18, "Ben Boeckel" <ben.boec...@kitware.com>:
> On Mon, Aug 14, 2017 at 20:09:17 +1000, Craig Scott wrote:
>>  It shouldn't be an issue having non-static Qt libs linked to cmake-gui, but
>>  as reported on the CMake users mailing list, it can be a problem when the
>>  directory cmake-gui is in is on the PATH. If CMake's bin directory appears
>>  on the PATH, the Qt DLL's bundled with it can take precedence over other
>>  applications' own Qt DLLs. The cmake and ccmake executables have a
>>  reasonable case for being on the PATH, but cmake-gui is typically going to
>>  be started via a desktop or menu icon and doesn't really need to be on the
>>  PATH.
>>
>>  Rather than forcing static Qt libs to be used (I'm not aware of the reason
>>  for the change from static to dynamic Qt libs), we could instead move
>>  cmake-gui out of the bin directory so that it isn't in the same directory
>>  as the cmake and ccmake executables. This top level directory should never
>>  be added to the PATH, so it would resolve problems like the above. It is
>>  not unusual for the main executable to be in the top level directory of an
>>  installation rather than in a bin subdirectory. What do people think of
>>  moving cmake-gui and the Qt DLL's up to the top level? This may just be for
>>  Windows, other platforms could stay as they are now. Would obviously have
>>  to adjust not just the install location but also any internal code that
>>  tries to work out where other files are located relative to the cmake-gui
>>  executable. Things like the qt.conf file would also probably need some
>>  adjustment.
>>
>>  Thoughts?
>
> Git splits it between bin/ and cmd/ where cmd/ is meant to be in PATH.
> Then the structure doesn't need to change either.

+1 Add script (.bat) to `cmd` subfolder to invoke tools from `bin` on Windows 
(and add to PATH variable if needed).

> --Ben
> --
>
> 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

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

Re: [cmake-developers] [ISSUES 17125] CPackIFW doesn't work properly on OSX

[Konstantin Podsvirov]

Hello dear CMake developers!

Interested in your opinion and the proposal to issue settings CPack generator.

https://gitlab.kitware.com/cmake/cmake/issues/17125

As it turned out CPack IFW generator capable of creating output in different 
formats, and it's not only files but also folders.

PS: Removed unnecessary formatting.

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

[cmake-developers] [ISSUES 17125] CPackIFW doesn't work properly on OSX

[Konstantin Podsvirov]

Hello dear CMake developers! Interested in your opinion and the proposal to issue settings CPack generator. https://gitlab.kitware.com/cmake/cmake/issues/17125 As it turned out CPack IFW generator capable of creating output in different formats, and it's not only files but also folders. 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

Re: [CMake] Boost moves to CMake

[Konstantin Podsvirov]

Hello all! 18.07.2017, 20:48, "Gonzalo Garramuño" <ggarr...@gmail.com>:> Just posted in the boost mailing list. Congratulations to both teams!> It seems that we are talking about this thread: https://lists.boost.org/Archives/boost/2017/07/237248.php > --> Gonzalo Garramuño>> -->> 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 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

[CMake] [Config-file Package] The best practice of finding package dependencies?

[Konstantin Podsvirov]

Hello community!

I want to give a little discussion :)

If I export a package containing several targets.
And these target are publicly linked to the targets imported from another 
package.
Where is the best place to look for package dependencies?

I assume the following options:
- In the Config-file of the package itself;
- The user himself must find them in his project.

It seems to me that to force the user to look for the dependencies of the 
package, which he himself seeks there is bad tone, but also to impose on the 
user, then how I myself found these dependencies in Config-file may not appeal 
to everyone.

Perhaps there should be some option for setting the behavior of the 
`find_package` command in the part of finding package dependencies? Or she 
already is, but I have not yet studied it.

--
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

Re: [cmake-developers] Where execute_process INPUT_CONTENT or INPUT_VARIABLE?

[Konstantin Podsvirov]

Hi!16:05, 24 April 2017 г., Brad King <brad.k...@kitware.com>:On 04/23/2017 01:30 AM, Konstantin Podsvirov wrote: Where execute_process INPUT_CONTENT or INPUT_VARIABLE? This would be very convenient for a small input. Why should I always write a file for input?I agree that the options should be there but they can't be easilyimplemented without choosing our own temporary file which will haveits own problems.The reason is that our internal process execution implementationdoes not support communication from the parent on stdin.  Fixingthat is not something I'm prepared to do or even accept as acontribution because I'd rather migrate to libuv than extend ourown process management implementation further.  That is a morelong-term process so in the meantime I think it is best to justask projects to use INPUT_FILE.-BradI apologize. I saw the library libuv in the dependencies and thought that it was used in the current implementation.I incorrectly assumed that this function is easy to add.__RegardsKonstantin 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

Re: [cmake-developers] Where execute_process INPUT_CONTENT or INPUT_VARIABLE?

[Konstantin Podsvirov]

23.04.2017, 12:26, "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>:
> On 2017-04-23 10:24+0300 Konstantin Podsvirov wrote:
>
>>  Hi Alan!
>>
>>  23.04.2017, 10:01, "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>:
>>>  On 2017-04-23 08:30+0300 Konstantin Podsvirov wrote:
>>>
>>>>   Where execute_process INPUT_CONTENT or INPUT_VARIABLE?
>>>>
>>>>   This would be very convenient for a small input.
>>>>
>>>>   Why should I always write a file for input?
>>>
>>>  Hi Konstantin:
>>>
>>>  I assume that last sentence refers to using the CMake FILE command
>>>  directly to write the required file at cmake time in the build tree
>>>  (as opposed to having to create an actual permanent file in the source
>>>  tree to be used directly or as a prototype for a configured file in
>>>  the build tree)? If so, I use that approach quite a bit in various
>>>  build systems I have helped to develop to help drastically reduce the
>>>  number of small CMake-related files in the source tree. And I far
>>>  prefer that approach to what you seem to be asking for above which is
>>>  some added syntax variation to EXECUTE_PROCESS to provide the same
>>>  ability that the FILE command currently has.
>>>
>>>  Note, I had to make some assumptions when answering you, and my
>>>  apologies in advance if I have misinterpreted anything you said
>>>  above.
>>
>>  You have correctly understood and assumed. Thanks for your reply.
>
>>  But imagine that we need to perform a simple process and process its
>
> standard output. But this process unfortunately awaits user input to
> complete.
>
> Interesting use case!
>
> Of course, if it is really simple user input to the process involving
> just a few values, then for that use case the user could enter those
> values via environment variables or CMake variables while the designed
> build system writes those via FILE to a temporary file in the right
> order that is then read by the process that is being executed by
> execute_process. But that idea becomes clumsy as the number of values
> increases. So I agree it would be useful to deal with the case where
> user input of a substantial number of values via stdin (presumably
> interactively prompted by the process to help guide that user input)
> is the best and most flexible way to control the process.

No. Do not complicate things. You do not need to implement interactive 
communication with the user through CMake streams.
I just want to add the convenient INPUT_CONTENT and INPUT_VARIABLE options.
The input data is known in advance, even before the process is started.

> One possibility to address that use case is whenever an appropriate
> optional argument was specified to execute_process, i.e., that
> execute_process command had the correct optional signature, then, for
> example, you could connect cmake stdin with the stdin for the process
> that is being executed by execute_process.
>
> Of course, one concern with this solution for the use case might be
> this makes the user build process difficult for a project's developers
> to debug in case the whole thing is failing because the user typed in
> the wrong stdin data for the process. But I would argue against that
> concern because this capability does give CMake-based build-system
> designers more power and freedom which I fundamentally like as such a
> build-system designer. And with each such additional increase in power
> and freedom of CMake, build-system designers have a documentation
> responsibility (i.e., in this case documenting exactly the stdin user
> choices for the process they have forced users to run at cmake time
> with execute_process), and the process design responsibility
> (sanitizing user input, prompting user input, etc.). Also
> build-system users have the responsibility of reading that process
> input documentation! :-)
>
> I must stop there because I have test project simplification and very
> likely git bisect work to do on a completely different issue I have
> raised here today.
>
> Alan
> __
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Pr

Re: [cmake-developers] Where execute_process INPUT_CONTENT or INPUT_VARIABLE?

[Konstantin Podsvirov]

Hi Alan!

23.04.2017, 10:01, "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>:
> On 2017-04-23 08:30+0300 Konstantin Podsvirov wrote:
>
>>  Where execute_process INPUT_CONTENT or INPUT_VARIABLE?
>>
>>  This would be very convenient for a small input.
>>
>>  Why should I always write a file for input?
>
> Hi Konstantin:
>
> I assume that last sentence refers to using the CMake FILE command
> directly to write the required file at cmake time in the build tree
> (as opposed to having to create an actual permanent file in the source
> tree to be used directly or as a prototype for a configured file in
> the build tree)? If so, I use that approach quite a bit in various
> build systems I have helped to develop to help drastically reduce the
> number of small CMake-related files in the source tree. And I far
> prefer that approach to what you seem to be asking for above which is
> some added syntax variation to EXECUTE_PROCESS to provide the same
> ability that the FILE command currently has.
>
> Note, I had to make some assumptions when answering you, and my
> apologies in advance if I have misinterpreted anything you said
> above.

You have correctly understood and assumed. Thanks for your reply.

But imagine that we need to perform a simple process and process its standard 
output. But this process unfortunately awaits user input to complete.

>
> Alan
> __
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __
>
> Linux-powered Science
> __

My suggestion:

Add support for the INPUT_CONTENT or INPUT_VARIABLE arguments in 
execute_process command.

It seems to me that this will be a very useful improvement.

Will anyone take up the implementation of this improvement?

--
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

[cmake-developers] [DISCUSSION] CMake Localization (L10N)

[Konstantin Podsvirov]

Draft code:

> set(GREETING "greeting message" # Optional default value
>  en "Hello, world!"
>  ru "Привет, мир!")
>
> set(CMAKE_OUTPUT_LOCALE "en") # Or CMAKE_L10N_LOCALE...
> 
> message("$L10N{GREETING}") # Hello, world!
> 
> set(CMAKE_OUTPUT_LOCALE "fr")
>
> message("$L10N{GREETING}") # greeting text
>
> message("$L10N:ru{GREETING}") # Привет, мир!

Any feedback?

--
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

Re: [CMake] Packaging issues

[Konstantin Podsvirov]

The CPackIFW module learned the new hint CPACK_IFW_ROOT variable for finding 
the QtIFW tool suite installed in a non-standard place.

https://cmake.org/cmake/help/git-master/module/CPackIFW.html#variable:CPACK_IFW_ROOT

This feature available in 'master' branch and will be released with CMake 3.9.0.

03.04.2017, 19:44, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hello Volker!
>
> 03.04.2017, 18:50, "Volker Enderlein" <volker.enderl...@ifm-chemnitz.de>:
>>  Am 03/04/2017 um 12:30 schrieb Volker Enderlein:
>>>   Hi,
>>>
>>>   I'm facing problems using the packaging with CPACK.
>>>
>>>   I try to build three different packages, a MSI (via WIX), an IFW, and
>>>   a ZIP package.
>>>
>>>   According to the documentation I set the following variables in my
>>>   CMakeLists.txt (and a few more which are required):
>>>
>>>   set(CPACK_WIX_ROOT "C:/Temp/WiX-3.10/binaries")
>>>
>>>   set(QTIFWDIR "${GLOBAL}/Qt/Tools/QtInstallerFramework/2.0/bin")
>
> As wrote in the documentation:
>
> https://cmake.org/cmake/help/latest/module/CPackIFW.html#overview
>
> QTIFWDIR (like QTDIR) - it's QtIFW installation path (without "/bin").
>
> You can set it's as your environment variable and use for all your projects.
>
>>>   set(CPACK_GENERATOR "WIX;IFW;ZIP")
>>>
>>>   After creating the build dir and running from there
>>>
>>>   cmake -G "Visual Studio 14 2015 Win64" ..\TestProject
>>>
>>>   the files CMakeCache.txt, CPackConfig.cmake, CPackSourceConfig.cmake,
>>>   and CPackProperties.cmake are generated.
>>>
>>>   When running `cpack -C Release` to build all three installers at once,
>>>   the first one (WIX) is built, but the second one (QtIFW) fails with
>>>   the messages
>>>
>>>   CPack Error: Cannot find QtIFW compiler "binarycreator": likely it is
>>>   not installed, or not in your PATH
>>>   CPack Error: Cannot initialize the generator IFW
>>>
>>>   I inspected the CMakeCache.txt file but found the following entries
>>>   properly defined:
>>>
>>>   //QtIFW binarycreator command line client
>>>   
>>> CPACK_IFW_BINARYCREATOR_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/binarycreator.exe
>>>
>>>   //QtIFW devtool command line client
>>>   
>>> CPACK_IFW_DEVTOOL_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/devtool.exe
>>>
>>>   //QtIFW installer executable base
>>>   
>>> CPACK_IFW_INSTALLERBASE_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/installerbase.exe
>>>
>>>   //QtIFW repogen command line client
>>>   
>>> CPACK_IFW_REPOGEN_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/repogen.exe
>>>
>>>   //Enable to build 7-Zip source packages
>>>   CPACK_SOURCE_7Z:BOOL=ON
>>>
>>>   //Enable to build ZIP source packages
>>>   CPACK_SOURCE_ZIP:BOOL=ON
>>>
>>>   //Path to a program.
>>>   CPACK_WIX_CANDLE_EXECUTABLE:FILEPATH=C:/Temp/WiX-3.10/binaries/candle.exe
>>>
>>>   //Path to a program.
>>>   CPACK_WIX_LIGHT_EXECUTABLE:FILEPATH=C:/Temp/WiX-3.10/binaries/light.exe
>>>
>>>   But when I checked the CPack*Config.cmake files none of the entries
>>>   above are referenced. After running the `cmake -G "Visual Studio 14
>>>   2015 Win64" ..\TestProject` a second time everything is fine; the
>>>   entries are referenced in CPack*Config.cmake files and all three
>>>   installers can be built.
>>>
>>>   So I really get stuck at this point.
>>>
>>>   Any ideas what could be the issue and how to avoid it?
>>>
>>>   Cheers Volker
>>
>>  A close follow up.
>>
>>  I finally figured out what didn't work.
>>
>>  The setting of the QTIFWDIR variable is not saved to the
>>  CPack*Config.cmake files. But the CMAKE_WIX_ROOT variable is. Those
>>  variables seem to be evaluated at runtime by CPack. Therefore the WIX
>>  build run successfully but the IFW build complained about a the path.
>>  Adding the variable with its current setting made everything run as
>>  expected.
>>
>>  Cheers Volker
>>
>>  --
>>
>>  Powered by www.kitware.com
>>
>>  Please keep messages on-topic and check the CMake FAQ at: 
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
&g

Re: [cmake-developers] [Discussion] Down with discrimination CPack!

[Konstantin Podsvirov]

Hello all!

19.01.2017, 00:16, "Alexander Neundorf" <neund...@kde.org>:
> On 2017 M01 18, Wed 22:20:14 CET Konstantin Podsvirov wrote:
>>  What about add to CMake language new packaging problematic scopes:
>>
>>  - COMPONENT;
>>  - COMPONENT_GROUP;

- INSTALL_TYPE;

>>  - PACKAGE;
>>  - INSTALLER;
>>  - REPOSITORY?
>
> that's a quite terse proposal...
>
> Alex
>
> --
>
> 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

The topic was not actively supported (except for one person), but I decided to 
give a new life at GitLab:

https://gitlab.kitware.com/cmake/cmake/issues/16777

--
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

Re: [CMake] Packaging issues

[Konstantin Podsvirov]

Hello Volker!

03.04.2017, 18:50, "Volker Enderlein" <volker.enderl...@ifm-chemnitz.de>:
> Am 03/04/2017 um 12:30 schrieb Volker Enderlein:
>>  Hi,
>>
>>  I'm facing problems using the packaging with CPACK.
>>
>>  I try to build three different packages, a MSI (via WIX), an IFW, and
>>  a ZIP package.
>>
>>  According to the documentation I set the following variables in my
>>  CMakeLists.txt (and a few more which are required):
>>
>>  set(CPACK_WIX_ROOT "C:/Temp/WiX-3.10/binaries")
>>
>>  set(QTIFWDIR "${GLOBAL}/Qt/Tools/QtInstallerFramework/2.0/bin")

As wrote in the documentation:

https://cmake.org/cmake/help/latest/module/CPackIFW.html#overview

QTIFWDIR (like QTDIR) - it's QtIFW installation path (without "/bin").

You can set it's as your environment variable and use for all your projects.

>>  set(CPACK_GENERATOR "WIX;IFW;ZIP")
>>
>>  After creating the build dir and running from there
>>
>>  cmake -G "Visual Studio 14 2015 Win64" ..\TestProject
>>
>>  the files CMakeCache.txt, CPackConfig.cmake, CPackSourceConfig.cmake,
>>  and CPackProperties.cmake are generated.
>>
>>  When running `cpack -C Release` to build all three installers at once,
>>  the first one (WIX) is built, but the second one (QtIFW) fails with
>>  the messages
>>
>>  CPack Error: Cannot find QtIFW compiler "binarycreator": likely it is
>>  not installed, or not in your PATH
>>  CPack Error: Cannot initialize the generator IFW
>>
>>  I inspected the CMakeCache.txt file but found the following entries
>>  properly defined:
>>
>>  //QtIFW binarycreator command line client
>>  
>> CPACK_IFW_BINARYCREATOR_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/binarycreator.exe
>>
>>  //QtIFW devtool command line client
>>  
>> CPACK_IFW_DEVTOOL_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/devtool.exe
>>
>>  //QtIFW installer executable base
>>  
>> CPACK_IFW_INSTALLERBASE_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/installerbase.exe
>>
>>  //QtIFW repogen command line client
>>  
>> CPACK_IFW_REPOGEN_EXECUTABLE:FILEPATH=N:/Global/Qt/Tools/QtInstallerFramework/2.0/bin/repogen.exe
>>
>>  //Enable to build 7-Zip source packages
>>  CPACK_SOURCE_7Z:BOOL=ON
>>
>>  //Enable to build ZIP source packages
>>  CPACK_SOURCE_ZIP:BOOL=ON
>>
>>  //Path to a program.
>>  CPACK_WIX_CANDLE_EXECUTABLE:FILEPATH=C:/Temp/WiX-3.10/binaries/candle.exe
>>
>>  //Path to a program.
>>  CPACK_WIX_LIGHT_EXECUTABLE:FILEPATH=C:/Temp/WiX-3.10/binaries/light.exe
>>
>>  But when I checked the CPack*Config.cmake files none of the entries
>>  above are referenced. After running the `cmake -G "Visual Studio 14
>>  2015 Win64" ..\TestProject` a second time everything is fine; the
>>  entries are referenced in CPack*Config.cmake files and all three
>>  installers can be built.
>>
>>  So I really get stuck at this point.
>>
>>  Any ideas what could be the issue and how to avoid it?
>>
>>  Cheers Volker
>
> A close follow up.
>
> I finally figured out what didn't work.
>
> The setting of the QTIFWDIR variable is not saved to the
> CPack*Config.cmake files. But the CMAKE_WIX_ROOT variable is. Those
> variables seem to be evaluated at runtime by CPack. Therefore the WIX
> build run successfully but the IFW build complained about a the path.
> Adding the variable with its current setting made everything run as
> expected.
>
> Cheers Volker
>
> --
>
> 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

Good luck with creating your installers!

--
Regards,
Konstantin Podsvirov (CPackIFW author)
-- 

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

Re: [CMake] best practice for bundling 3rdparty dependencies in windows

[Konstantin Podsvirov]

Hello!22:02, 19 February 2017 г., "tonka3...@gmail.com" <tonka3...@gmail.com>:Hey @everybody,I have a question about best practice for app bundling especially 3rdparty libs. In Linux it is not some common to bundle 3rdparty libs with my application but in windows this is highly recommended. What’s a good way to bundle 3rdparty libs (mostly .dll, sometimes also .exe) in windows (maybe macos x has the same „problem“).At the moment i use install(FILES …) to install the 3rdparty libs (i’ve tried to install imported target, but thats not possible :-( ). I use a cmake variable to activate (default is off) to copy 3rdparty libs to the install directory. The only other way i could go is to add a cpack_install_script file, but this is only availabe in cpack time.So is there a better way to bundle 3rdparty libs or is this the recommended approach?Thanks in advanceTonka-- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmakeYou can try DaD's Way:https://dad.podsvirov.pro/houseBuild each module separately and use a cross-platform installer.--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

Re: [CMake] Disabling INSTALL target for subdirectory

[Konstantin Podsvirov]

Hello all!10:00, 16 February 2017 г., Milan Ziegler <mi...@fastmail.com>:Hi,we are using the CMake install mechanism "install(...)" to copy allrelevant files and target binaries of the product into the CMake installprefix folder, for further packaging. So far so good.We are also using several thirdparty libraries, hosting them inside ourown repository and building them along with our own code, usually usingadd_subdirectory utilizing their native CMake buildsystem.Turns out, other developers also like the CMake install mechanism.So now the INSTALL target of our whole project also installs thirdpartycomponents, which we do not want to deliver with our own product (thinkstatic libraries, which are already linked into our executable).After a lot of googling, here's my question: Is there a clean way todisable the install target for a subdirectory _without_ also disablingit completely for the remaining project?What we already tried:* Setting CMAKE_INSTALL_PREFIX to a temporary directory for thesubdirectory (doesn't work)* "function(install) endfunction()" to disable the install function forthe subdirectory (breaks CMake in hilarious ways)What we now do:Using a custom target, we patch the cmake_install.cmake files in thebuild directories before installing (works, but it's an  abomination ofa hack)Any help? I think it's a valid usecase for CMake but there doesn't seemto be an easy way to do it.We are using CMake 3.5.Thank you :)--   Milan  mi...@fastmail.com-- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmakeIt common actual problem.My suggestion:a) Separate CMakeLists.txt code to several files: - CMakeLists.txt; - CTestLists.txt; - CDashLists.txt; - CPackLists.txt;b) Add common options to enable/disable feature for directory: - CMAKE_LISTS_TXT:BOOL; - CTEST_LISTS_TXT:BOOL; - CDASH_LISTS_TXT:BOOL; - CPACK_LISTS_TXT:BOOL;c) Fix add_subdirectory command implementation :-)--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

Re: [cmake-developers] Debugger for CMake

[Konstantin Podsvirov]

19:54, 14 February 2017 г., Ben Boeckel :On Mon, Feb 13, 2017 at 20:18:02 -0700, Justin Berger wrote: I agree on the maximizing code reuse, but that doesn't require them to use the same operational mode -- the two modes do fundamentally different things; even while sharing most internal components. Is the idea that you could only start a debug session if you have cmake-server running, and then you instruct it to configure?What about debugging CMake `-P` scripts? Or does server-mode not work inscript mode?Where UTILITY targets 'all', 'install', 'clean', edit_cash' and 'rebuild_cash' in server mode? I do mot see it via latest Qt Creator (master)?--Ben-- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmake-developersОтправлено из мобильной Яндекс.Почты: http://m.ya.ru/ymail
-- 

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

Re: [cmake-developers] [Qt-creator] ​Qt Creator vs CMake server mode

[Konstantin Podsvirov]

10.02.2017, 11:02, "Tobias Hunger" <tobias.hun...@gmail.com>:
> Hi all,
>
> On Fri, Feb 10, 2017 at 1:08 AM, Mike Jackson <imikejack...@gmail.com> wrote:
>> I can confirm with QtCreator 4.3 nightly builds and CMake 3.7.1 those
>> "utility" targets do not show up.
>
> Server-mode reports the following targets: EXECUTABLE, STATIC_LIBRARY,
> SHARED_LIBRARY, MODULE_LIBRARY, OBJECT_LIBRARY, UTILITY and
> INTERFACE_LIBRARY, provided they are not marked as "IsImported".
>
> So these should be reported and I do see lots of UTILITY targets in
> the project tree of creator.
>
> Best Regards,
> Tobias
> ___
> Qt-creator mailing list
> qt-crea...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

Yes, I see UTILITY targets now, but I don't see:

- all;
- clean;
- edit_cache;
- rebuild_cache;

This is a very important targets.

--
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

Re: [cmake-developers] ​Qt Creator vs CMake server mode

[Konstantin Podsvirov]

Ping and hello again! 25.12.2016, 21:42, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:Since Qt Creator 4.3 release (now aka master branch) will get project information via CMake server (since 3.7 release). For more info see: https://blog.qt.io/blog/2016/11/15/cmake-support-in-qt-creator-and-elsewhere In my expirienceit's look like utility targets (install, rebuild_cache, edit_cache, package) do not exported now. Now Qt Creator use project information via CodeBlocks extra generator (*.cbp files) and utility targets available now. I check it on Windows with "NMake Makefiles" generator. You can try my experimental prebuilt binaries: http://download.podsvirov.pro/installers/dad-0.3.1-windows-vc14x64-unstable.exe Can anybody check it too?  Fresh CMake and QtCreator binaries form `master` branches available via my new experimental installer: http://download.podsvirov.pro/installers/dad-0.3.1-windows-mingw64-unstable.exe (Windows, MinGW-w64 64bit) You need components: MinGW, CMake, QtCreator (cofigure Kit manualy). > In my expirienceit's look like utility targets (install, rebuild_cache, edit_cache, package) do not exported now. Any help and feedback? --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

[cmake-developers] [Discussion] Down with discrimination CPack!

[Konstantin Podsvirov]

What about add to CMake language new packaging problematic scopes: - COMPONENT;- COMPONENT_GROUP;- PACKAGE;- INSTALLER;- REPOSITORY? --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

Re: [CMake] Managing a local installation of cmake-built open source packages

[Konstantin Podsvirov]

18.01.2017, 21:32, "ardi" <ardillasdelmo...@gmail.com>:On Wed, Jan 18, 2017 at 7:19 PM, Konstantin Podsvirov<konstan...@podsvirov.pro> wrote: Hello Ardi! [...]  Sounds like, you need cross-platform (several desktops) package manager compatible with cmake. If all desktops with GUI, what about using CPack IFW generator? https://cmake.org/cmake/help/latest/module/CPackIFW.htmlThanks for the idea, Konstantin. Yes, all the OSs I use have a GUI,although I don't use Qt. If the best solution is IFW, I'd use Qt onlyfor this. BTW, I'm new to IFW, and if I'm reading it correctly, cpackgenerates an installer, which I guess is an executable... but... canthe installer also be used for uninstalling? Will an installer of anew version of a package uninstall an older version if it exists?CPack IFW generator help you to create installer (yes, it's executable based on Qt,but static linked) thats you need run on target platform (you don't have preinstalled Qt). CPack IFW generator can also help you to create packages repository to use from installers(local or from network). Installer will remove old package before update him to new version. --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

Re: [CMake] Managing a local installation of cmake-built open source packages

[Konstantin Podsvirov]

Hello Ardi! 18.01.2017, 20:39, "ardi" <ardillasdelmo...@gmail.com>:Hi,I want to install (on UNIX-like systems) a collection of open sourcepackages which use cmake as the build tool, but I need theinstallation to be performed in a local directory (inside my homedirectory), and I wish convenient updating to new versions of thepackages.I didn't arrive to a convincing solution, so any advice will be welcome.Here are my thoughts:The trivial solution is of course to directly install to a non-rootprefix when invoking cmake, but, however, this isn't well suited forupdating a previous installation of the packages (building andinstalling a new version will only overwrite files that have the samename, but it will keep old files that no longer exist in the newversion, cluttering the local installation directory with no longerneeded and mismatched files).A possibility would be to keep a copy of install_manifest.txt wheneverI install a package, and remembering to always run 'xargs rm <install_manifest.txt' before installing a different version of apreviously installed package.But keeping the install_manifest.txt of each installed package (andusing it before updating a package) looks like a too-manual task,candidate to some kind of automation.Another (perhaps wiser) possibility would be to use cpack for creatingeither a RPM or DEB, and then use the corresponding package manager toinstall the package. But this has problems too: most package managersassume a / root installation directory. Also, I use several OSs: OSX,Linux, and some BSDs, and I'm not sure that either the RPM nor the DEBpkg managers will work flawlessly across all the OSs I use.What would you recommend here?Thanks a lot! Sounds like, you need cross-platform (several desktops) package manager compatible with cmake. If all desktops with GUI, what about using CPack IFW generator? https://cmake.org/cmake/help/latest/module/CPackIFW.html --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

Re: [cmake-developers] [Discussion] Add python support for CMakeLists

[Konstantin Podsvirov]

Hello all! 13.01.2017, 18:56, "Brad King" <brad.k...@kitware.com>:On 01/12/2017 01:20 PM, Shmuel H, wrote: maybe a general problem with dependencies, which generally make our life harder?Yes. People typically install CMake only in order to build something else.If Python were added as an external dependency then that would be yetanother step. If it were bundled then our bootstrap script and CMake-basedbuild of CMake itself would both have to learn to build Python. Pythonis also a distribution in addition to a language, so deploying it raisesthe question of what to bundle with it. None of these is something I'dlike to have added to the responsibilities of maintaining and distributingCMake.There are already other build systems that use Python as their language,but many people still choose CMake over them anyway. I believe that language should be one. Many of us well know C ++, and so we understand each other.   However, for me - a user, a known and well-designed programming language for CMake would be very helpful. I can't say that for every other user, but I think it would make their life a lot easier too.As Charles Huet mentioned Lua is a good choice because it provides alanguage and is portable to everywhere that has C. It is also not adistribution. I've posted in the past a design for a cmake_lua commandthat allows one to use Lua code within CMakeLists.txt files. Actuallyusing it as a full replacement language though will first require morerefactoring internally as I mentioned in my previous post.As I've mentioned in previous discussions, if we're going to go througha language change we should make sure it addresses important needs.Having a declarative specification that can be externally tooled willbe helpful to IDEs. I'd envision such a format that is then importedby the procedural-language part of the configuration process forevaluation of conditions and finalization for the current target.Without a comprehensive design I'm hesitant to proceed on any such effort. I completely agree. Must first be designed very, very good design decision. -Brad-- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmake-developers  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

Re: [CMake] CMake 3.7.1 gui fails to launch

[Konstantin Podsvirov]

Hm...18:52, 6 january 2017 г., David Cole via CMake :Can you use Qt5? CMake 3.7 is typically built using Qt5: perhaps a Qt5**requirement** has crept in since it's the commonly used one now.It's work for me with RedHat and Qt 4.8.6.No problem cmake-gui work.HTH,David C.On Fri, Jan 6, 2017 at 10:41 AM,   wrote: I'm running Ubuntu 14.04 and I'm trying to get the current version of CMake to run.  (The apt-get version is 2.8). I installed Qt4 (version 4.8.6) with   $ sudo apt-get install libqt4-core libqt4-dev libqt4-gui qt4-dev-tools I installed cmake   $ ./bootstrap & make & sudo make install all seemed to run without issue.  Running "cmake-gui --version" reported version 3.7.1, but running "cmake-gui" failed: = daryl@eve-ldb:~/cmake/cmake-3.7.1$ cmake-gui --version cmake version 3.7.1 CMake suite maintained and supported by Kitware (kitware.com/cmake). daryl@eve-ldb:~/cmake/cmake-3.7.1$ cmake-gui cmake-gui: symbol lookup error: cmake-gui: undefined symbol: _ZN9QListData11detach_growEPii == That looks like a Qt linkage error.  Any suggestions on resolving this? -- 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-- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmakeОтправлено из мобильной Яндекс.Почты: http://m.ya.ru/ymail
-- 

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

Re: [cmake-developers] Allow CodeBlocks for NMake Makefiles JOM

[Konstantin Podsvirov]

Hello again! 24.12.2016, 15:09, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:Hello all! Any promotion please :-) CMake: https://gitlab.kitware.com/cmake/cmake/merge_requests/360  QtCreator: https://codereview.qt-project.org/#/c/180814  QtCreator CR now merged to 4.2 branch: https://codereview.qt-project.org/#/c/180814 And we can configure CodeBlocks extra generator for NMake Makefiles JOM generator via QtCreator. I need help to push my CMake changes to next branch, then master, then release. You can try my binary preview by online installer: http://download.podsvirov.pro/installers/dad-0.3.1-windows-vc14x64-unstable.exe (You need manualy configure 'Kit' with provided CMake) --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

[cmake-developers] ​Qt Creator vs CMake server mode

[Konstantin Podsvirov]

Since Qt Creator 4.3 release (now aka master branch) will get project information via CMake server (since 3.7 release). For more info see: https://blog.qt.io/blog/2016/11/15/cmake-support-in-qt-creator-and-elsewhere In my expirienceit's look like utility targets (install, rebuild_cache, edit_cache, package) do not exported now. Now Qt Creator use project information via CodeBlocks extra generator (*.cbp files) and utility targets available now. I check it on Windows with "NMake Makefiles" generator. You can try my experimental prebuilt binaries: http://download.podsvirov.pro/installers/dad-0.3.1-windows-vc14x64-unstable.exe Can anybody check it too? --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

[cmake-developers] Allow CodeBlocks for NMake Makefiles JOM

[Konstantin Podsvirov]

Hello all! Any promotion please :-) CMake: https://gitlab.kitware.com/cmake/cmake/merge_requests/360  QtCreator: https://codereview.qt-project.org/#/c/180814 --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

[CMake] [SUGGESTION] Add %ONLY alternative for configure_file command

[Konstantin Podsvirov]

Relative issue: https://gitlab.kitware.com/cmake/cmake/issues/16471 Uncomfortable now create templates for file which themselves use `@` (the dog) to separate the variables. For example, this occurs in QtIFW scripts for components and installer (for example, see [QtSDK](http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/configurations/pkg_templates) templates). Now I have to set a variable to a value `set(VAR "@VAR@")` that would get the same result. The alternative use of the `%` symbol and leave `@VAR@` variables as there. Who is for and who is against? --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

Re: [cmake-developers] QtSDK integration

[Konstantin Podsvirov]

Well, thank you Brad!22:14, 28 november 2016 г., Brad King <brad.k...@kitware.com>:On 11/28/2016 08:49 AM, Konstantin Podsvirov wrote: Anybody known where Brad King? Or anybody can help me to review and merge !280, !281 and !282 MRs into 'next' for testing?I was on vacation for the US Thanksgiving holiday.  I'll get tothese when I can.Thanks,-BradI would also like to say thank you that I have included in the project team on GitLab site and in the Copyright text.--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

Re: [cmake-developers] QtSDK integration

[Konstantin Podsvirov]

Hello all!Anybody known where Brad King?Or anybody can help me to review and merge !280, !281 and !282 MRs into 'next' for testing?7:04, 17 november 2016 г., Konstantin Podsvirov <konstan...@podsvirov.pro>:Hi, dear CMake developers! Some of us actively using the Qt technology, but remain fans of CMake. I had the idea to extend the CMake part of the QtSDK. I created proposals for appropriate changes in QtCreator: https://bugreports.qt.io/browse/QTCREATORBUG-17290 It also requires improvements in the CMake. I'm working on it here: http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cpack-ifw-options and here: http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cmake-ifw-root-component Demo repository for Windows: http://download.podsvirov.pro/online/qtsdkrepository/windows_x86/desktop/tools_cmake You can add this repository in Qt Maintenance Tool and try to install CMake as part of the QtSDK, but now QtSDK (QtCreator) does not recognize this installation automatically. How do you like this idea? What has to be installed in this case? (tools, cmake-gui?, docs?...) I'm waiting feedback from support or a reasoned rejection of this idea. --Regards,Konstantin Podsvirov -- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmake-developersОтправлено из мобильной Яндекс.Почты: http://m.ya.ru/ymail
-- 

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

[cmake-developers] QtSDK integration

[Konstantin Podsvirov]

Hi, dear CMake developers! Some of us actively using the Qt technology, but remain fans of CMake. I had the idea to extend the CMake part of the QtSDK. I created proposals for appropriate changes in QtCreator: https://bugreports.qt.io/browse/QTCREATORBUG-17290 It also requires improvements in the CMake. I'm working on it here: http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cpack-ifw-options and here: http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cmake-ifw-root-component Demo repository for Windows: http://download.podsvirov.pro/online/qtsdkrepository/windows_x86/desktop/tools_cmake You can add this repository in Qt Maintenance Tool and try to install CMake as part of the QtSDK, but now QtSDK (QtCreator) does not recognize this installation automatically. How do you like this idea? What has to be installed in this case? (tools, cmake-gui?, docs?...) I'm waiting feedback from support or a reasoned rejection of this idea. --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

Re: [CMake] ExternalProject_Add : set the location of CMakeLists.txt

[Konstantin Podsvirov]

Hello again.

25.10.2016, 20:31, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hello, Benjamin.
>
> 25.10.2016, 19:41, "Benjamin Ballet via CMake" <cmake@cmake.org>:
>>  Hi,
>>
>>  I'm trying to get GLEW (https://github.com/nigels-com/glew) with 
>> ExternalProject_Add
>>  It's buildable with cmake but the CMakeLists.txt is in build/cmake 
>> directory.
>>
>>  Is there a way to specify the directory of the CMakeLists.txt file ?
>>
>>  If I change SOURCE_DIR it will only clone the repo in SOURCE_DIR and still 
>> run the cmake command in repo root.
>>
>>  --
>>  Benjamin BALLET
>>  Ingénieur R
>>
>>  ACTIVISU
>>  19, rue Klock - 92110 Clichy
>>>  Standard Tél :  01 44 69 37 37
>>>  www.activisu.com
>>  ,--
>
> Try it:
>
> ExternalProject_Add(
>   ...
>   SOURCE_DIR ${CMAKE_CURRENT_BINARY_DIR}/source
>   ...
>   CONFIGURE_COMMAND ${CMAKE_COMMAND} [additional args...] 
> ${CMAKE_CURRENT_BINARY_DIR}/source/build/cmake
>   ...)


Or try it:

ExternalProject_Add(
  ...
  SOURCE_DIR ${CMAKE_CURRENT_BINARY_DIR}/source
  ...
  CONFIGURE_COMMAND ${CMAKE_COMMAND} [additional args...]
   -DCMAKE_GENERATOR=${CMAKE_GENERATOR}
   -DCMAKE_GENERATOR_PLATFORM=${CMAKE_GENERATOR_PLATFORM}
   -DCMAKE_GENERATOR_TOOLSET=${CMAKE_GENERATOR_TOOLSET}
${CMAKE_CURRENT_BINARY_DIR}/source/build/cmake
  ...)

--
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

Re: [CMake] ExternalProject_Add : set the location of CMakeLists.txt

[Konstantin Podsvirov]

Hello, Benjamin.

25.10.2016, 19:41, "Benjamin Ballet via CMake" <cmake@cmake.org>:
> Hi,
>
> I'm trying to get GLEW (https://github.com/nigels-com/glew) with 
> ExternalProject_Add
> It's buildable with cmake but the CMakeLists.txt is in build/cmake directory.
>
> Is there a way to specify the directory of the CMakeLists.txt file ?
>
> If I change SOURCE_DIR it will only clone the repo in SOURCE_DIR and still 
> run the cmake command in repo root.
>
> --
> Benjamin BALLET
> Ingénieur R
>
> ACTIVISU
> 19, rue Klock - 92110 Clichy
>> Standard Tél :  01 44 69 37 37
>> www.activisu.com
> ,--

Try it:

ExternalProject_Add(
  ...
  SOURCE_DIR ${CMAKE_CURRENT_BINARY_DIR}/source
  ...
  CONFIGURE_COMMAND ${CMAKE_COMMAND} [additional args...] 
${CMAKE_CURRENT_BINARY_DIR}/source/build/cmake
  ...)

---
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

Re: [cmake-developers] [MODERN] CMake 3.6+ vs Qt 5.7 vs MSVC2015

[Konstantin Podsvirov]

Hi all! CMake Master (Win32/Win64) updated! :-)

It's time to upgrade: CMake 3.6.20160921 now available!

"CMake Master" - is himself created (IFW generator) online installer for CMake 
users and developers.

23.06.2016, 19:38, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Let me remind you of the link.
>
> Windows 32bit:
>
> http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
>
> Windows 64bit:
>
> http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
>
> If you have used it before, you can update via "CMake Maintenance Tool"
>
> I used Windows 7, but it should work for Windows Vista and Windows 8 and 
> Windows 10.
>
> I ask those wishing to test the functionality.
>
> Please test it :-)

Pay your attention:

Added new component "CMake Developer Reference" - Doxygen based source code 
reference.
You can install it by online installer in HTML and Qt Compressed Help formats 
or preview it
in your browser online at http://ifw.podsvirov.pro/cmake/doc/doxygen/

>>>>    01.10.2015, 09:29, Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>>>>> Hi all! Modern master alive! :-)
>>>>>
>>>>> It's been almost a month and it's time to upgrade:
>>>>>
>>>>> 3.3.20150901 CMake => CMake 3.3.20151001
>>>>>
>>>>> Dear friends, I have a question and call for help.
>>>>>
>>>>> With my assistance the project has an option for component 
>>>>> installation project:
>>>>>
>>>>> CMake_INSTALL_COMPONENTS
>>>>>
>>>>> Unfortunately not all files found your component.
>>>>> The files to be installed without specifying a component fall into 
>>>>> 'Unspecified' component.
>>>>> Need to parse them out and assign them to the component context.
>>>>>
>>>>> Now have the components:
>>>>>
>>>>> - cmake;
>>>>> - ctest;
>>>>> - cpack;
>>>>> - cmake-gui;
>>>>> - sphinx-man;
>>>>> - sphinx-html;
>>>>> - sphinx singlehtml;
>>>>>     - sphinx-qthelp
>>>>>
>>>>> and General for everything else
>>>>>
>>>>> Is Unspecified;
>>>>>
>>>>> A list of unaccounted for 'Unspecified' of files to install on the 
>>>>> Window is attached.
>>>>>
>>>>> Links to the installers were specified earlier (see below).
>>>>>
>>>>> On 28.07.2015, 17:49, "Konstantin Podsvirov" 
>>>>> <konstan...@podsvirov.pro>:
>>>>>> Hi dear CMake developers!
>>>>>>
>>>>>> 27.07.2015, 18:52, "Brad King" <brad.k...@kitware.com>:
>>>>>>> On 07/24/2015 03:46 AM, Konstantin Podsvirov wrote:
>>>>>>>> To solve the problem you run cmake-gui is now possible with the
>>>>>>>> the following changes:
>>>>>>>
>>>>>>> Applied as two separate commits with minor tweaks:
>>>>>>>
>>>>>>> cmake-gui: Install Qt5 Windows platform plugin
>>>>>>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f0155b
>>>>>>>
>>>>>>> CMake: Add option CMake_INSTALL_DEPENDENCIES
>>>>>>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=068e7962
>>>>>>
>>>>>> Code now in 'master' branch.
>>>>>>
>>>>>> Thanks, Brad!
>>>>>>
>>>>>> Meet/install/CMake built modern update on MSVC2015 c QtDialog based 
>>>>>> on Qt 5.5 from today :-)
>>>>>>
>>>>>> Windows 32bit:
>>>>>>
>>>>>> http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
>>>>>>
>>>>>> Windows 64bit:
>>>>>>
>>>>>> http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
>>>>>>
>>>>>> cmake-gui should work now, but if not, then update your system and 
>>>>>> install
>>>>>>
>>>>>> The Visual C++ Redistributable for Visual Studio 2015 from the link 
>>>>>> below:
>>

[cmake-developers] [Review Request] Doxygen alive, but limping

[Konstantin Podsvirov]

Hello dear CMake developers!

Changes there:

https://gitlab.kitware.com/cmake/cmake/merge_requests/58

--

Revive Doxygen documentation as CMake Developer Reference.

This is a complete change from the point of view of the installation process.

I expect that after the publication of the contents will be improved.


You can preview this changes from 'CMake Master' by me.

Linux:

http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

Windows:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

--
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

Re: [cmake-developers] [ISSUE] Bump to 3.2 and continue...

[Konstantin Podsvirov]

29.07.2016, 23:56, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hello CMake developers,
>
> I found bug:
>
> https://gitlab.kitware.com/cmake/cmake/issues/16220
>
> I found it, but I do not want to deal with it ...

Okay, I have solution.

May be attached patch will be more useful then MR 
(https://gitlab.kitware.com/cmake/cmake/merge_requests/51).

> --
> 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

Regards,
Konstantin Podsvirov
From c9d3fada704ffe40b996b0e8b33e0ba3935c7b01 Mon Sep 17 00:00:00 2001
From: Konstantin Podsvirov <konstan...@podsvirov.pro>
Date: Mon, 1 Aug 2016 23:16:55 +0300
Subject: [PATCH] Remove using of continue() method

It's needed for backward compatible with CMake 2.8.4.
---
 Utilities/Sphinx/CMakeLists.txt | 19 +++
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/Utilities/Sphinx/CMakeLists.txt b/Utilities/Sphinx/CMakeLists.txt
index 257ba62..256f1d5 100644
--- a/Utilities/Sphinx/CMakeLists.txt
+++ b/Utilities/Sphinx/CMakeLists.txt
@@ -156,18 +156,21 @@ if(SPHINX_MAN)
 if("x${m}" MATCHES "^x(.+)\\.([1-9])\\.rst$")
   set(name "${CMAKE_MATCH_1}")
   set(sec "${CMAKE_MATCH_2}")
+  set(_m_skip FALSE)
   if(NOT CMakeHelp_STANDALONE)
 if(name STREQUAL "ccmake" AND NOT BUILD_CursesDialog)
-  continue()
-endif()
-if(name STREQUAL "cmake-gui" AND NOT BUILD_QtDialog)
-  continue()
+  set(_m_skip TRUE)
+elseif(name STREQUAL "cmake-gui" AND NOT BUILD_QtDialog)
+  set(_m_skip TRUE)
 endif()
   endif()
-  CMake_OPTIONAL_COMPONENT(sphinx-man)
-  install(FILES ${CMAKE_CURRENT_BINARY_DIR}/man/${name}.${sec}
-  DESTINATION ${CMAKE_MAN_DIR}/man${sec}
-  ${COMPONENT})
+  if(NOT _m_skip)
+CMake_OPTIONAL_COMPONENT(sphinx-man)
+install(FILES ${CMAKE_CURRENT_BINARY_DIR}/man/${name}.${sec}
+DESTINATION ${CMAKE_MAN_DIR}/man${sec}
+${COMPONENT})
+  endif()
+  unset(_m_skip)
 endif()
   endforeach()
 endif()
-- 
2.8.3.windows.1

-- 

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

[cmake-developers] [ISSUE] Bump to 3.2 and continue...

[Konstantin Podsvirov]

Hello CMake developers,

I found bug:

https://gitlab.kitware.com/cmake/cmake/issues/16220

I found it, but I do not want to deal with it ...

--
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

[CMake] Fwd: [Review Request] [Draft] CMake project for QtIFW

[Konstantin Podsvirov]

Hello guys!

I like CMake and Qt and i initial write and now support CPack IFW generator.

For more project integrations i create sugestion:
https://bugreports.qt.io/browse/QTIFW-876

And start work on it:
https://codereview.qt-project.org/#/c/165493

It's draft, but any feedback will be appreciated.

--
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

[cmake-developers] [Review Request][Draft] CMake project for QtIFW

[Konstantin Podsvirov]

Hello guys!

I like CMake and Qt and i initial write and now support CPack IFW generator.

For more project integrations i create sugestion:
https://bugreports.qt.io/browse/QTIFW-876

And start work on it:
https://codereview.qt-project.org/#/c/165493

It's draft, but any feedback will be appreciated.

--
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

[cmake-developers] [PATCH] CMake installation improvements

[Konstantin Podsvirov]

Hello Brad,

please apply my changes.

--
Regards,
Konstantin Podsvirov
From 56137a0f7096bae99eeb45ca83567a5ee87d4cee Mon Sep 17 00:00:00 2001
From: Konstantin Podsvirov <konstan...@podsvirov.pro>
Date: Wed, 13 Jul 2016 00:10:28 +0300
Subject: [PATCH 1/3] CMake: install COMPONENT cmcldeps

Added in Tools group with IFW installer
---
 CMakeCPack.cmake   |  3 +++
 CMakeCPackOptions.cmake.in | 10 +-
 Source/CMakeLists.txt  | 18 +++---
 3 files changed, 23 insertions(+), 8 deletions(-)

diff --git a/CMakeCPack.cmake b/CMakeCPack.cmake
index 8879cb9..60011ae 100644
--- a/CMakeCPack.cmake
+++ b/CMakeCPack.cmake
@@ -70,6 +70,9 @@ if(EXISTS "${CMAKE_ROOT}/Modules/CPack.cmake")
   # Components
   if(CMake_INSTALL_COMPONENTS)
 set(_CPACK_IFW_COMPONENTS_ALL cmake ctest cpack)
+if(WIN32 AND NOT CYGWIN)
+list(APPEND _CPACK_IFW_COMPONENTS_ALL cmcldeps)
+endif()
 if(APPLE)
   list(APPEND _CPACK_IFW_COMPONENTS_ALL cmakexbuild)
 endif()
diff --git a/CMakeCPackOptions.cmake.in b/CMakeCPackOptions.cmake.in
index 59ae224..1d61613 100644
--- a/CMakeCPackOptions.cmake.in
+++ b/CMakeCPackOptions.cmake.in
@@ -102,13 +102,21 @@ if(CPACK_GENERATOR MATCHES "IFW")
   set(CPACK_IFW_COMPONENT_CPACK_PRIORITY 87)
   set(CPACK_IFW_COMPONENT_CPACK_VERSION "@_CPACK_IFW_PACKAGE_VERSION@")
 
+  set(CPACK_COMPONENT_CMCLDEPS_DISPLAY_NAME "cmcldeps")
+  set(CPACK_COMPONENT_CMCLDEPS_DESCRIPTION
+"The \"cmcldeps\" executable is wrapper around \"cl\" program")
+  set(CPACK_COMPONENT_CMCLDEPS_GROUP Tools)
+  set(CPACK_IFW_COMPONENT_CMCLDEPS_NAME "CMClDeps")
+  set(CPACK_IFW_COMPONENT_CMCLDEPS_PRIORITY 86)
+  set(CPACK_IFW_COMPONENT_CMCLDEPS_VERSION "@_CPACK_IFW_PACKAGE_VERSION@")
+
   set(CPACK_COMPONENT_CMAKEXBUILD_DISPLAY_NAME "cmakexbuild")
   set(CPACK_COMPONENT_CMAKEXBUILD_DESCRIPTION
 "The \"cmakexbuild\" executable is a wrapper program for \"xcodebuild\"")
   set(CPACK_COMPONENT_CMAKEXBUILD_REQUIRED TRUE)
   set(CPACK_COMPONENT_CMAKEXBUILD_GROUP Tools)
   set(CPACK_IFW_COMPONENT_CMAKEXBUILD_NAME "CMakeXBuild")
-  set(CPACK_IFW_COMPONENT_CMAKEXBUILD_PRIORITY 86)
+  set(CPACK_IFW_COMPONENT_CMAKEXBUILD_PRIORITY 85)
   set(CPACK_IFW_COMPONENT_CMAKEXBUILD_VERSION "@_CPACK_IFW_PACKAGE_VERSION@")
 
   # Dialogs
diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index d49ebbb..a790994 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -530,11 +530,14 @@ set(SRCS ${SRCS}
   cmNinjaUtilityTargetGenerator.h
   )
 
+# Temporary variable for tools targets
+set(_tools)
+
 if(WIN32 AND NOT CYGWIN)
   set_source_files_properties(cmcldeps.cxx PROPERTIES COMPILE_DEFINITIONS _WIN32_WINNT=0x0501)
   add_executable(cmcldeps cmcldeps.cxx ${MANIFEST_FILE})
+  list(APPEND _tools cmcldeps)
   target_link_libraries(cmcldeps CMakeLib)
-  install(TARGETS cmcldeps DESTINATION bin)
 endif()
 
 foreach(v CURL_CA_BUNDLE CURL_CA_PATH)
@@ -746,6 +749,7 @@ endif()
 
 if(APPLE)
   add_executable(cmakexbuild cmakexbuild.cxx)
+  list(APPEND _tools cmakexbuild)
   target_link_libraries(cmakexbuild CMakeLib)
   add_executable(OSXScriptLauncher
 CPack/OSXScriptLauncher.cxx)
@@ -755,14 +759,17 @@ endif()
 
 # Build CMake executable
 add_executable(cmake cmakemain.cxx cmcmd.cxx cmcmd.h ${MANIFEST_FILE})
+list(APPEND _tools cmake)
 target_link_libraries(cmake CMakeLib)
 
 # Build CTest executable
 add_executable(ctest ctest.cxx ${MANIFEST_FILE})
+list(APPEND _tools ctest)
 target_link_libraries(ctest CTestLib)
 
 # Build CPack executable
 add_executable(cpack CPack/cpack.cxx ${MANIFEST_FILE})
+list(APPEND _tools cpack)
 target_link_libraries(cpack CPackLib)
 
 # Curses GUI
@@ -781,15 +788,12 @@ include (${CMake_SOURCE_DIR}/Source/LocalUserOptions.cmake OPTIONAL)
 
 # Install tools
 
-set(_tools cmake ctest cpack)
-
-if(APPLE)
-  list(APPEND _tools cmakexbuild)
-endif()
-
 foreach(_tool ${_tools})
   CMake_OPTIONAL_COMPONENT(${_tool})
   install(TARGETS ${_tool} DESTINATION ${CMAKE_BIN_DIR} ${COMPONENT})
 endforeach()
 
 install(FILES cmCPluginAPI.h DESTINATION ${CMAKE_DATA_DIR}/include)
+
+# Unset temporary variables
+unset(_tools)
-- 
2.8.3.windows.1

From bfa20dc8074c0c70b94ebbc8b150df001590088e Mon Sep 17 00:00:00 2001
From: Konstantin Podsvirov <konstan...@podsvirov.pro>
Date: Wed, 13 Jul 2016 00:50:10 +0300
Subject: [PATCH 2/3] QtIFW: process USE_LGPL when CMake_INSTALL_COMPONENTS

---
 CMakeCPack.cmake | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/CMakeCPack.cmake b/CMakeCPack.cmake
index 60011ae..34bb6bb 100644
--- a/CMakeCPack.cmake
+++ b/CMakeCPack.cmake
@@ -90,8 +90,10 @@ if(EXISTS "${CMAKE_ROOT}/Modules/CPack.cmake")
 endif()
 if(BUILD_QtDialog)
   list(APPEND _CPACK_IFW_COMPONENTS_ALL cmake-gui)
-  set(_CPACK_IFW_COMPONENT_CMAKE-GUI_LICENSES "set(CPACK_

Re: [cmake-developers] [CpackIFW] Fix bug in cpack_ifw_configure_... commands

[Konstantin Podsvirov]

15:44, 7 jul 2016 г., Brad King <brad.k...@kitware.com>:On 07/07/2016 07:43 AM, Konstantin Podsvirov wrote: Can you also merge topic 'cpack-ifw-list-variable' to release branch?Does it fix a 3.6 regression or a bug in a 3.6 new feature?No.Fixes to long-standing bugs are not eligible to be backportedto the release.It's long-standing bug from 3.1 release.Ok. I will wait.Thanks,-Brad--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

[cmake-developers] [CpackIFW] Fix bug in cpack_ifw_configure_... commands

[Konstantin Podsvirov]

Hello, Brad!Can you also merge topic 'cpack-ifw-list-variable' to release branch?It's fix processing of LICENSES arguments of cpack_ifw_configure... commands where license display_name contain spaces.
-- 

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

[CMake] Disable removing generated file

[Konstantin Podsvirov]

Hello guys!How to disable removing generated file with clean target?My custom command generate or update file.
-- 

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

Re: [cmake-developers] Fix bug in CPack IFW Promoting Updates repository replacement

[Konstantin Podsvirov]

Thanks again, Brad!

05.07.2016, 22:58, "Brad King" <brad.k...@kitware.com>:
> On date 07/05/2016 03:39 PM, Konstantin Podsvirov wrote:
>> I found a small bug in CPackIFW. The patch is attached.
>
> Thanks, applied:
>
> CPackIFW: Fix attributes for Promoting Updates repository replacement
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7a30fa1a
>
>> Changes are best to send to a mailing list or use your networks?
>
> Either is fine. We're still experimenting with the Networks
> workflow so it is not documented in the CONTRIBUTING.rst yet.

I apologize that sometimes there are persistent, but thank you so much for your 
feedback and applying my changes.

The theme of integration and CMake QtIFW quite new and deals with both 
technologies.

I get good feedback from CMake and try to influence the development of QtIFW.

The project QtIFW included in the Qt infrastructure and make changes to it is 
not so simple. But I'm trying. Here's my first change (it is still pending):

https://codereview.qt-project.org/#/c/163220

I want to go further and to provide CMakeLists.txt to build the QtIFW.
I'm working on this theme in a topic branch "topic-cmake-project" on your 
server:

http://git.podsvirov.pro/?p=qt/qtifw.git;a=shortlog;h=refs/heads/topic-cmake-project

It is very dirty now, but there are already some results.
The project QtIFW for normal operation requires linking with the static version 
of the Qt library. This is not standard practice and could have a positive 
impact on the detection and correction of errors in this case.

I hope that this topic will ever be merged with the project QtIFW.

--
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

[cmake-developers] Fwd: CMake | CPackIFW: Using cpack_append_list_variable_set_command (!27)

[Konstantin Podsvirov]

 sending message  
05.07.2016, 22:37, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:

Thanks, Brad!

I've been waiting for your answer :-)

05.07.2016, 22:30, "Brad King" <git...@gitlab.kitware.com>:
>  Thanks. I've merged this to next for testing.

I found a small bug in CPackIFW. The patch is attached.

I read the wrong documentation for QtIFW 
(https://bugreports.qt.io/browse/QTIFW-873) and made the wrong generation.
I conducted a series of tests and now everything should work correctly.

I have a household question:
Changes are best to send to a mailing list or use your gitlab?
 sending message  

Regards,
Konstantin Podsvirov
From e52011d61867db107c3437d7e55e02bcdc555f41 Mon Sep 17 00:00:00 2001
From: Konstantin Podsvirov <konstan...@podsvirov.pro>
Date: Tue, 5 Jul 2016 22:30:12 +0300
Subject: [PATCH 3/3] CPackIFW: Fixed attributes for repository replace

---
 Source/CPack/IFW/cmCPackIFWRepository.cxx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Source/CPack/IFW/cmCPackIFWRepository.cxx b/Source/CPack/IFW/cmCPackIFWRepository.cxx
index ee6d5e5..fcb1c77 100644
--- a/Source/CPack/IFW/cmCPackIFWRepository.cxx
+++ b/Source/CPack/IFW/cmCPackIFWRepository.cxx
@@ -299,8 +299,8 @@ void cmCPackIFWRepository::WriteRepositoryUpdate(cmXMLWriter& xout)
   if (Update == Add || Update == Remove) {
 xout.Attribute("url", Url);
   } else if (Update == Replace) {
-xout.Attribute("oldurl", OldUrl);
-xout.Attribute("newurl", NewUrl);
+xout.Attribute("oldUrl", OldUrl);
+xout.Attribute("newUrl", NewUrl);
   }
   // Enabled
   if (!Enabled.empty()) {
-- 
2.8.3.windows.1

-- 

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

[cmake-developers] [ANNOUNCE] DaD's House Standalone Installers

[Konstantin Podsvirov]

Hello dear developers!

Standalone installers for some DaD's House releases now available at SF mirror:

https://sourceforge.net/projects/dad-mirror/files/standalone/2015/dad-0.3.1-windows-vc12x64-2015-standalone.exe/download

https://sourceforge.net/projects/dad-mirror/files/standalone/2015/dad-0.3.1-windows-vc12x86-2015-standalone.exe/download

https://sourceforge.net/projects/dad-mirror/files/standalone/2014/dad-0.3.1-windows-vc12x64-2014-standalone.exe/download

https://sourceforge.net/projects/dad-mirror/files/standalone/2014/dad-0.3.1-windows-vc12x86-2014-standalone.exe/download

This info also available at installers page:

http://dad.podsvirov.pro/house/installers

10.06.2016, 23:54, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hi guys! Hello developers!
>
> My "DaD's Project" is based on CMake and QtIFW (specifically CPackIFW) 
> continues its development:
>
> http://dad.podsvirov.pro - the official "DaD's House" website now.
>
> "DaD's House" is a resource where you can download the installers to install 
> necessary dependencies
> and immediately begin developing their projects.
>
> Already declared support 40 the following modules:
>
> Curses, ZLib, LibPNG, Jpeg, Libxml2, LibTIFF, Perl, OpenSSL, LibSSH2, cURL,
> PCRE, PROJ, Expat, FreeType, SQLite, GEOS, GDAL, Boost, Qt, QtIFW,
> CMake KDSoap, OSG, osgEarth, osgQtQuick, PostgreSQL, Apache.Apr, The 
> Apache.AprUtil, Apache.Httpd, Protobuf,
> gRPC, MapServer, Bullet, QCA, wxWidgets, LibXSLT, iconv, pgAdmin3, Wt, 
> FreeGLUT.
>
> Also available in 4 port:
>
>  - Windows Visual C++ Compiler 12.0 32bit
>  - Windows Visual C++ Compiler 12.0 64bit
>
> and NEW
>
>  - Windows 5.3.0 MinGW w64 32bit
>  - Windows 5.3.0 MinGW w64 64bit
>
> The last 2 ports have appeared recently and there are still large but 
> interesting work.
>
> All of this can be a good basis for your projects.
> All this is a good basis for my personal growth.
>
> I assess the status of the project as a Beta and write to lists for 
> developers of basic technologies.
>
> Open the curtain.
>
> For each module I have a small CMakeLists.txt:
>
> http://git.podsvirov.pro/?a=project_list;pf=dad/mod
>
> These scripts help me to build the modules and create a repository of binary 
> components.
>
> There is a need to spread content. All available here:
>
> http://download.podsvirov.pro
>
> My server is small and weak. I need help in distribution. I need a mirror 
> "main" module:
>
> rsync://podsvirov.pro
>
> If there are interested parties and you give me the address of the mirror, 
> then I can add them to MirrorBrain setup
> for more efficient distribution.
>
> If you are interested in developing this technology or already use my 
> installers, I would like to hear your opinion
> and to get feedback.
>
> Have a great weekend and good luck in development of your projects!
>
> --
> 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

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

[cmake-developers] [ANNOUNCE] New Modules and Ports at DaD's House

[Konstantin Podsvirov]

Hi guys! Hello developers!

My "DaD's Project" is based on CMake and QtIFW (specifically CPackIFW) 
continues its development:

http://dad.podsvirov.pro - the official "DaD's House" website now.

"DaD's House" is a resource where you can download the installers to install 
necessary dependencies
and immediately begin developing their projects.

Already declared support 40 the following modules:

Curses, ZLib, LibPNG, Jpeg, Libxml2, LibTIFF, Perl, OpenSSL, LibSSH2, cURL,
PCRE, PROJ, Expat, FreeType, SQLite, GEOS, GDAL, Boost, Qt, QtIFW,
CMake KDSoap, OSG, osgEarth, osgQtQuick, PostgreSQL, Apache.Apr, The 
Apache.AprUtil, Apache.Httpd, Protobuf,
gRPC, MapServer, Bullet, QCA, wxWidgets, LibXSLT, iconv, pgAdmin3, Wt, FreeGLUT.

Also available in 4 port:

 - Windows Visual C++ Compiler 12.0 32bit
 - Windows Visual C++ Compiler 12.0 64bit

and NEW

 - Windows 5.3.0 MinGW w64 32bit
 - Windows 5.3.0 MinGW w64 64bit

The last 2 ports have appeared recently and there are still large but 
interesting work.

All of this can be a good basis for your projects.
All this is a good basis for my personal growth.

I assess the status of the project as a Beta and write to lists for developers 
of basic technologies.

Open the curtain.

For each module I have a small CMakeLists.txt:

http://git.podsvirov.pro/?a=project_list;pf=dad/mod

These scripts help me to build the modules and create a repository of binary 
components.

There is a need to spread content. All available here:

http://download.podsvirov.pro

My server is small and weak. I need help in distribution. I need a mirror 
"main" module:

rsync://podsvirov.pro

If there are interested parties and you give me the address of the mirror, then 
I can add them to MirrorBrain setup
for more efficient distribution.

If you are interested in developing this technology or already use my 
installers, I would like to hear your opinion
and to get feedback.

Have a great weekend and good luck in development of your projects!

--
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

Re: [CMake] Calling find_package(self) for in-project builds

[Konstantin Podsvirov]

Hello.8:34, 3 june 2016 г., Walter Gray :Interesting idea, that could be possible.Possible, but realy need? It can be alternative. Now we can use ALIASES for build tree configuration - It's work (I check)On Thu, Jun 2, 2016 at 8:45 PM Dan Liew  wrote:> What would be the suggested way to handle this?  Couldn't you build the examples using CMake's ``ExternalProject`` module [1] and have that build after the main project has finished building?  [1] https://cmake.org/cmake/help/v3.5/module/ExternalProject.html  -- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmake
-- 

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

Re: [cmake-developers] [MODERN] CMake 3.6+ vs Qt 5.6 vs MSVC2015

[Konstantin Podsvirov]

Hi all! Modern master updated! :-)

It's time to upgrade: CMake 3.6.20160602 now available!

Let me remind you of the link.

Windows 32bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

Windows 64bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used it before, you can update via "CMake Maintenance Tool"

I used Windows 7, but it should work for Windows Vista and Windows 8 and 
Windows 10.

I ask those wishing to test the functionality.

And new:

 Linux (Debian) amd64:

 http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

 Please test it :-)

>>  01.10.2015, 09:29, Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>>>   Hi all! Modern master alive! :-)
>>>
>>>   It's been almost a month and it's time to upgrade:
>>>
>>>   3.3.20150901 CMake => CMake 3.3.20151001
>>>
>>>   Dear friends, I have a question and call for help.
>>>
>>>   With my assistance the project has an option for component installation 
>>> project:
>>>
>>>   CMake_INSTALL_COMPONENTS
>>>
>>>   Unfortunately not all files found your component.
>>>   The files to be installed without specifying a component fall into 
>>> 'Unspecified' component.
>>>   Need to parse them out and assign them to the component context.
>>>
>>>   Now have the components:
>>>
>>>   - cmake;
>>>   - ctest;
>>>   - cpack;
>>>   - cmake-gui;
>>>   - sphinx-man;
>>>   - sphinx-html;
>>>   - sphinx singlehtml;
>>>   - sphinx-qthelp
>>>
>>>   and General for everything else
>>>
>>>   Is Unspecified;
>>>
>>>   A list of unaccounted for 'Unspecified' of files to install on the Window 
>>> is attached.
>>>
>>>   Links to the installers were specified earlier (see below).
>>>
>>>   On 28.07.2015, 17:49, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>>>>   Hi dear CMake developers!
>>>>
>>>>   27.07.2015, 18:52, "Brad King" <brad.k...@kitware.com>:
>>>>>   On 07/24/2015 03:46 AM, Konstantin Podsvirov wrote:
>>>>>>   To solve the problem you run cmake-gui is now possible with the
>>>>>>   the following changes:
>>>>>
>>>>>   Applied as two separate commits with minor tweaks:
>>>>>
>>>>>   cmake-gui: Install Qt5 Windows platform plugin
>>>>>   http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f0155b
>>>>>
>>>>>   CMake: Add option CMake_INSTALL_DEPENDENCIES
>>>>>   http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=068e7962
>>>>
>>>>   Code now in 'master' branch.
>>>>
>>>>   Thanks, Brad!
>>>>
>>>>   Meet/install/CMake built modern update on MSVC2015 c QtDialog based on 
>>>> Qt 5.5 from today :-)
>>>>
>>>>   Windows 32bit:
>>>>
>>>>   http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
>>>>
>>>>   Windows 64bit:
>>>>
>>>>   http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
>>>>
>>>>   cmake-gui should work now, but if not, then update your system and 
>>>> install
>>>>
>>>>   The Visual C++ Redistributable for Visual Studio 2015 from the link 
>>>> below:
>>>>
>>>>   http://www.microsoft.com/en-us/download/details.aspx?id=48145
>>>>
>>>>   As always, questions and suggestions are welcome.
>>>
>>>   --
>>>   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
>>
>>  Regards,
>>  Konstantin Podsvirov

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

Re: [cmake-developers] [MODERN] CMake ~3.6 vs Qt 5.6 vs MSVC2015

[Konstantin Podsvirov]

Hi all! Modern master updated! :-)

It's time to upgrade: CMake 3.5.20160531 now available!

Previously had problems with that, but now it seems that it works.

Let me remind you of the link.

Windows 32bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

Windows 64bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used it before, you can update via "CMake Maintenance Tool"

I used Windows 7, but it should work for Windows Vista and Windows 8 and 
Windows 10.

I ask those wishing to test the functionality.

And new:

Linux (Debian) amd64:

http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

Please test it :-)

> 01.10.2015, 09:29, Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>>  Hi all! Modern master alive! :-)
>>
>>  It's been almost a month and it's time to upgrade:
>>
>>  3.3.20150901 CMake => CMake 3.3.20151001
>>
>>  Dear friends, I have a question and call for help.
>>
>>  With my assistance the project has an option for component installation 
>> project:
>>
>>  CMake_INSTALL_COMPONENTS
>>
>>  Unfortunately not all files found your component.
>>  The files to be installed without specifying a component fall into 
>> 'Unspecified' component.
>>  Need to parse them out and assign them to the component context.
>>
>>  Now have the components:
>>
>>  - cmake;
>>  - ctest;
>>  - cpack;
>>  - cmake-gui;
>>  - sphinx-man;
>>  - sphinx-html;
>>  - sphinx singlehtml;
>>  - sphinx-qthelp
>>
>>  and General for everything else
>>
>>  Is Unspecified;
>>
>>  A list of unaccounted for 'Unspecified' of files to install on the Window 
>> is attached.
>>
>>  Links to the installers were specified earlier (see below).
>>
>>  On 28.07.2015, 17:49, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>>>  Hi dear CMake developers!
>>>
>>>  27.07.2015, 18:52, "Brad King" <brad.k...@kitware.com>:
>>>>  On 07/24/2015 03:46 AM, Konstantin Podsvirov wrote:
>>>>>  To solve the problem you run cmake-gui is now possible with the
>>>>>  the following changes:
>>>>
>>>>  Applied as two separate commits with minor tweaks:
>>>>
>>>>  cmake-gui: Install Qt5 Windows platform plugin
>>>>  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f0155b
>>>>
>>>>  CMake: Add option CMake_INSTALL_DEPENDENCIES
>>>>  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=068e7962
>>>
>>>  Code now in 'master' branch.
>>>
>>>  Thanks, Brad!
>>>
>>>  Meet/install/CMake built modern update on MSVC2015 c QtDialog based on Qt 
>>> 5.5 from today :-)
>>>
>>>  Windows 32bit:
>>>
>>>  http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
>>>
>>>  Windows 64bit:
>>>
>>>  http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
>>>
>>>  cmake-gui should work now, but if not, then update your system and install
>>>
>>>  The Visual C++ Redistributable for Visual Studio 2015 from the link below:
>>>
>>>  http://www.microsoft.com/en-us/download/details.aspx?id=48145
>>>
>>>  As always, questions and suggestions are welcome.
>>
>>  --
>>  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
>
> 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.h

[cmake-developers] [PATCH] CPackIFW Updates

[Konstantin Podsvirov]

Hi again Brad!

Sorry for my tardiness, and work in small pieces, but please accept my changes 
to CPack IFW generator (2 of the latest commit):

commit 06ca7795f4c0a7503d98e856384f986a0047f811

 CPackIFW: Command cpack_ifw_configure_component learned ESSENTIAL option

commit 222fa595cd6106cb6a4948eedeb55b0314338dff

 CPackIFW: Doc decoration

It is also on my server.

http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cpackifw-generator

Option is ESSENTIAL are very important for the online update of the installer 
itself.

I checked availability via the git Protocol.
I also checked the formatting with clang-format 3.8.

Thanks in advance.

--
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

Re: [cmake-developers] [MODERN] CMake ~3.6 vs Qt 5.6 vs MSVC2015

[Konstantin Podsvirov]

Hi all! Modern master alive! :-)

It's time to upgrade: CMake 3.5.20160520 now available!

Previously had problems with that, but now it seems that it works.

Thank you brad for the new functionality:

https://cmake.org/cmake/help/git-master/release/dev/InstallRequiredSystemLibraries-Windows-UCRT.html

I tried to do it myself following the instructions, but I failed:

https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt

Let me remind you of the link.

Windows 32bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

Windows 64bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used it before, you can update via "CMake Maintenance Tool"

I used Windows 7, but it should work for Windows Vista and Windows 8 and 
Windows 10.

I ask those wishing to test the functionality.

01.10.2015, 09:29, Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hi all! Modern master alive! :-)
>
> It's been almost a month and it's time to upgrade:
>
> 3.3.20150901 CMake => CMake 3.3.20151001
>
> Dear friends, I have a question and call for help.
>
> With my assistance the project has an option for component installation 
> project:
>
> CMake_INSTALL_COMPONENTS
>
> Unfortunately not all files found your component.
> The files to be installed without specifying a component fall into 
> 'Unspecified' component.
> Need to parse them out and assign them to the component context.
>
> Now have the components:
>
> - cmake;
> - ctest;
> - cpack;
> - cmake-gui;
> - sphinx-man;
> - sphinx-html;
> - sphinx singlehtml;
> - sphinx-qthelp
>
> and General for everything else
>
> Is Unspecified;
>
> A list of unaccounted for 'Unspecified' of files to install on the Window is 
> attached.
>
> Links to the installers were specified earlier (see below).
>
> On 28.07.2015, 17:49, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>> Hi dear CMake developers!
>>
>> 27.07.2015, 18:52, "Brad King" <brad.k...@kitware.com>:
>>> On 07/24/2015 03:46 AM, Konstantin Podsvirov wrote:
>>>> To solve the problem you run cmake-gui is now possible with the
>>>> the following changes:
>>>
>>> Applied as two separate commits with minor tweaks:
>>>
>>> cmake-gui: Install Qt5 Windows platform plugin
>>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f0155b
>>>
>>> CMake: Add option CMake_INSTALL_DEPENDENCIES
>>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=068e7962
>>
>> Code now in 'master' branch.
>>
>> Thanks, Brad!
>>
>> Meet/install/CMake built modern update on MSVC2015 c QtDialog based on Qt 
>> 5.5 from today :-)
>>
>> Windows 32bit:
>>
>> http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
>>
>> Windows 64bit:
>>
>> http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
>>
>> cmake-gui should work now, but if not, then update your system and install
>>
>> The Visual C++ Redistributable for Visual Studio 2015 from the link below:
>>
>> http://www.microsoft.com/en-us/download/details.aspx?id=48145
>>
>> As always, questions and suggestions are welcome.
>
> --
> 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

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

Re: [cmake-developers] [PATCH] CPackIFW: Added cpack_ifw_update_repository command and other

[Konstantin Podsvirov]

18.05.2016, 16:52, "Brad King" <brad.k...@kitware.com>:
> On 05/17/2016 04:29 PM, Konstantin Podsvirov wrote:
>> Please consider my changes in part CPack IFW generator.
>
> I've applied the changes with a few tweaks and merged to 'next' for testing:
>
> CPackIFW: Add more known QtIFW releases
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6ca6b0dd
>
> CPackIFW: Add support for Promoting Updates
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=41199f8c

Thank you!

>> http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cpackifw-generator
>
> I'm unable to fetch from that repository anymore:
>
> $ git ls-remote git://podsvirov.pro/kitware/cmake.git
> fatal: unable to connect to podsvirov.pro:
> podsvirov.pro[0: 188.120.254.166]: errno=Connection refused
>
> What is the fetch URL for it?

All right now. This is the correct URL. Just my git-daemon forgot to start :-) 
Thanks for the notice.

> Thanks,
> -Brad

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

[cmake-developers] [PATCH] CPackIFW: Added cpack_ifw_update_repository command and other

[Konstantin Podsvirov]

Hello, Brad!

Please consider my changes in part CPack IFW generator.

This is a small but very useful functional improvement.
It came with 2.0.3 release QtIFW. Read Promoting Updates for more information:

http://doc.qt.io/qtinstallerframework/ifw-updates.html

The last 3 commits in a topic branch "topic-cpackifw-generator" on my server:

CPackIFW: Added cmCPackIFWRepository class
CPackIFW: Added cpack_ifw_update_repository command...
CPackIFW: Added the known QtIFW releases

http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-cpackifw-generator

I read about the changes in formatting and have tried to take this into account.

Hope to see these changes in release 3.6 :-)

--
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

Re: [cmake-developers] more use of cmXMLWriter

[Konstantin Podsvirov]

Hi all! Hi Daniel!

Thank you for the work done.

I'm the developer CPack IFW generator.

I heard about cmXMLWriter and planned to use it,
but I couldn't find the time to do it.

I looked 0007-CPack-IFW-port-to-cmXMLWriter.patch and at first glance
everything should work as before, but I haven't conducted tests
on the real packs.

If I find the time to test, I will report about results here.

20.03.2016, 00:24, "Daniel Pfeifer" <dan...@pfeifer-mail.de>:
> Hi,
> I ported. some more generators to cmXMLWriter.
> cheers, Daniel

--
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

Re: [cmake-developers] [ANNOUNCE] CMake 3.5.0 available for download

[Konstantin Podsvirov]

cess.
> This may break scripts that worked around the bug with their own
> extra quoting or escaping.
>
> * The "Xcode" generator was fixed to escape backslashes in strings
> consistently with other generators. Projects that previously worked
> around the inconsistecy with an extra level of backslashes
> conditioned on the Xcode generator must be updated to remove the
> workaround for CMake 3.5 and greater.
>
> Other Changes
> =
>
> * The "Visual Studio 14 2015" generator learned to map the
> "/debug:fastlink" to the linker flag ".vcxproj" file property.
>
> * The "FindGTK2" module now configures the "GTK2::function sigc++" imported
> target to enable c++11 on its dependents when using function sigc++ 2.5.1 or
> higher.
>
> * The precompiled Windows binary provided on "cmake.org" is now a
> ".msi" package instead of an installer executable. One may need to
> manually uninstall CMake versions lower than 3.5 before installing
> the new package.
> 
> Changes made since CMake 3.5.0-rc3:
>
> Ashley Whetter (1):
> Help: Fix typos in cmake-packages.7 manual
>
> Bartosz Kosiorek (1):
> Help: Clarify `cmake -E` command behavior with respect to file existence
>
> Brad King (3):
> VS: Fix VS 2015 .vcxproj debug setting for older toolsets (#15986)
> FindPython{Interp,Libs}: Clarify recommended call order
> CMake 3.5.0
> --
>
> 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

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

Re: [cmake-developers] CMake for 64Win7

[Konstantin Podsvirov]

Good day!

You can try the experimental installer (based on IFW generator) from my website:

http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-rc3-win64-x64.exe

You can also try the online version, which is based on code from branch 
"master":

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

Online installer supports online update.

Good luck :-)

08.03.2016, 03:32, "LI, NING" <l...@cec.sc.edu>:
> Dear Sirs,
>
> There are only 32Win version of CMake( cmake-3.5.0-rc3-win32-x86.msi or 
> cmake-3.5.0-rc3-win32-x86.zip ) on your web page( https://cmake.org/download/ 
> ). When will the version for 64Win available?
>
> Thank you for the help!
>
> Ning.
> ==
> LI, Ning. Ph.D.
> --
> E-mail Address: l...@cec.sc.edu
> ===The University of South Carolina===

--
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

Re: [cmake-developers] C++11 only for a specified subdirectory

[Konstantin Podsvirov]

Hi, Roman!

You can use properties for each target:

C_STANDART
C_STANDARD_REQUIRED

CXX_STANDARD
CXX_STANDARD_REQUIRED

Read online:

https://cmake.org/cmake/help/latest/manual/cmake-properties.7.html#properties-on-targets

And this question is for cm...@cmake.org list :-)

04.03.2016, 16:20, "Roman Wüger" <roman.wue...@gmx.at>:
> Hi,
>
> is it possible to activate C++11 only for a subdirectory?
>
> Regards
> Roman
> --
>
> 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

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

Re: [CMake] [cmake-developers] C++11 only for a specified subdirectory

[Konstantin Podsvirov]

Hi, Roman!

You can use properties for each target:

C_STANDART
C_STANDARD_REQUIRED

CXX_STANDARD
CXX_STANDARD_REQUIRED

Read online:

https://cmake.org/cmake/help/latest/manual/cmake-properties.7.html#properties-on-targets

And this question is for cmake@cmake.org list :-)

04.03.2016, 16:20, "Roman Wüger" <roman.wue...@gmx.at>:
> Hi,
>
> is it possible to activate C++11 only for a subdirectory?
>
> Regards
> Roman
> --
>
> 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

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

Re: [cmake-developers] [PATCH] FindProtobuf: fix wrong library list for Unix

[Konstantin Podsvirov]

Wonderful project "protobuf" ("protobuf" with a small letter "f") starting with 
version 3.0 (which is around the corner - now beta 2), will be built with CMake 
on Windows, and will contain CONFIG scripts with a description of the exported 
package and an imported goal.

That's the name of the project:

https://github.com/google/protobuf/blob/master/cmake/CMakeLists.txt#L5

All targets will be installed in the standard paths, which optionally can be 
configured to your needs (use the GNUInstallDirs module):

https://github.com/google/protobuf/blob/master/cmake/install.cmake#L10

There is also the option to configure Postfix in a debug configuration 
(protobuf_DEBUG_POSTFIX - default "d"):

https://github.com/google/protobuf/blob/master/cmake/CMakeLists.txt#L26

So for protobuf >= 3.0 on Windows you can use
design:

find_package(protobuf CONFIG)

These new features were created with my participation. I tried to create a 
configuration compatible with the all of us known module. Here is a template 
script compatibility for the module:

https://github.com/google/protobuf/blob/master/cmake/protobuf-module.cmake.in

Unfortunately, for platforms other than Windows, use CMake to build protobuf 
not officially planned, but carried out private studies confirm the fact that 
cmake/CMakeLists workable on other platforms.

Thus the project "protobuf" already cmake/CMakeLists.txt and is open to 
modifications and development for the benefit of the CMake community.

While we will continue to work as follows:

find_package(Protobuf [MODULE])

But over time, I hope to do just so:

find_package(protobuf CONFIG)

All suggestions and comments as always are welcome.

And for publicity :-)

You can try pre-built protobuf me 3.0 for Windows (MSVC2013) from Dad's Project 
(installers "testing"):

http://dad.podsvirov.pro/house/installers

(sorry for possible mistakes in text)

09.02.2016, 00:39, "Brad King" <brad.k...@kitware.com>:
> On 02/08/2016 04:24 PM, Antonio Pérez Barrero wrote:
>> Yes, it is possible, but currently it's not looking for the debug
>> library with a different name, just in a different path that is 
>> unlikely to exist in a Unix system.
>
> The fact that a separate find_library is called for it and the result
> is stored in a separate (user-settable) cache entry means that it is
> possible to get two different values. This convention is well established
> find in several modules.
>
>> Having the variable PROTOBUF_LIBRARIES getting the afore mentioned
>> value messes up the client code using `find_package(Protobuf)` on Unix.
>
> The only supported use for PROTOBUF_LIBRARIES is to pass it to
> target_link_libraries, and that interprets the 'optimized' and 'debug'
> keywords. This is shown in the module documentation example:
>
> target_link_libraries(bar ${PROTOBUF_LIBRARIES})
>
> The documentation makes no other guarantees about the variable value.
>
> -Brad
>
> --
>
> 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

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

Re: [CMake] CMake 3.5.0-rc1 install is missing dependencies

[Konstantin Podsvirov]

Meet the fresh update online installers (CMake3.5.3.5.20160203):

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

and

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used them previously, then just update via "CMake Maintenance Tool".

These installers were collected and razvernut using AppVeyor:

https://ci.appveyor.com/project/podsvirov/cmake/build/3.5-26

03.02.2016, 21:36, "Brad King" <brad.k...@kitware.com>:
> On 02/03/2016 11:19 AM, Thompson, KT wrote:
>> The Windows installation doesn't appear to provide all the
>> required dependencies. ‘cmake-gui’ will not launch and provides
>> the error “Qt5Widgets.dll is missing form your computer.”
>
> Ugh, after months of working correctly on the nightly binary builds
> something happened to go wrong on the packaging machine specifically
> for this release build due to an environment change. I've fixed it
> and replaced the binary on the download site for the Windows build.
> Please download and try again.
>
> -Brad

I tried the installer:

https://cmake.org/files/v3.5/cmake-3.5.0-rc1-win32-x86.msi

He asked me to install CMake on your way:

C:\Program Files (x86)\Canon\Easy-WebPrint EX\

:-) (something and somewhere went wrong...)

I changed to:

C:\Program Files (x86)\CMake\

And installed as usual.

In the Start menu I have a folder of CMake (although the old NSIS installer 
would create a folder CMake 3.5.0-rc1)

I then used just installed cmake to create installers based on IFW generator.

I built these offline installers:

http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-rc1-win32-x86.exe

and

http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-rc1-win64-x64.exe

In all cases I was using MSVC2013 and Qt5.5.1 for cmake-gui.
For me everything works fine.

I ask all those interested. To test the results and to share lessons learned.

Together we will make CMake better!!!

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

[cmake-developers] [DaD] New and Updated Modules and New Installers

[Konstantin Podsvirov]

Hello, dear developers!

Once again, I apologize for using your lists, but my project still don't have 
your list :-)

Time passes and Dad's Project develops. I have over 2 years building and share 
a few, I think interesting modules.

Let me remind you that the official Dad's House on the Internet:

http://dad.podsvirov.pro

I have prepared and laid out the releases for 2014 and 2015. Here are the 
special installers:

http://download.podsvirov.pro/installers/dad-0.2.0-windows-vc12x86-2014.exe
http://download.podsvirov.pro/installers/dad-0.2.0-windows-vc12x64-2014.exe

and

http://download.podsvirov.pro/installers/dad-0.3.0-windows-vc12x86-2015.exe
http://download.podsvirov.pro/installers/dad-0.3.0-windows-vc12x64-2015.exe

Versions of modules in these installers frozen and will not change if not 
necessary.

On the website you can compare the components and the versions of relevant 
modules for installers (links Details).

Installers stable/testing/unstable continue to evolve.

As always, questions and suggestions are welcome.

The project is in Beta stage. For errors I would be grateful.

If you use my installers and proved to be helpful in your project, then write 
about their experiences.

(sorry for possible mistakes in text)

--
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

Re: [cmake-developers] Git for windows patch

[Konstantin Podsvirov]

Hi, Shawn!

I am using CMake and Git on the Windows. As an IDE I use Qt Creator.

My experience is that on Windows you need to use:

"C:\Program Files [(x86)]\Git\cmd\git.exe"

If you use your proposed way, I'm having problems
work with Git in my project.

It seems to me that this decision is necessary to discuss here.

Dear list, does anyone have experience and recommendations?

15.01.2016, 02:49, "Shawn Waldon" <shawn.wal...@kitware.com>:
> Hi,
>
> Recently I had to build a project on windows whose required build git. And 
> even though I had installed git from here [1] in the default location, I had 
> to tell CMake where to find it every time I did a build in a clean build 
> tree. So here is a patch that tells CMake to look in the default install 
> location for Git for Windows [2] when asked for git. I have tested it on my 
> windows machine and it works there.
>
> Shawn
>
> [1]: https://git-for-windows.github.io/
> [2]: C:\Program Files\Git\bin\git.exe ('Program Files (x86)' for older 
> versions or 32 bit systems)
> ,--
>
> 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


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

[CMake] [Re] How to select components by default using CPack ?

[Konstantin Podsvirov]

Hi David!

I found your letter here:

http://public.kitware.com/pipermail/cmake/2015-December/062188.html

Earlier I was not subscribed to the CMake Users.

I see that you try to use IFW generator.

Can offer you the following variant of the script:

cmake_minimum_required(VERSION 3.2)
project(test)

set(CPACK_PACKAGE_NAME Hello)
set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "Hello world using IFW")
set(CPACK_PACKAGE_VERSION "1.0.0")
set(CPACK_GENERATOR "IFW")
set(CPACK_COMPONENTS_GROUPING "IGNORE")

set(PLUGINS one two)

foreach (plugin ${PLUGINS})
 install(
 FILES ${plugin}.js
 COMPONENT plugin_${plugin}
 DESTINATION plugins
 )

 list(APPEND CPACK_COMPONENTS_ALL plugin_${plugin})
endforeach ()

include(CPack)
include(CPackIFW)

cpack_add_component_group(plugins)

foreach (plugin ${PLUGINS})
 cpack_add_component(
 plugin_${plugin}
 DISPLAY_NAME "${plugin}"
 DESCRIPTION "Install ${plugin}.js"
 GROUP plugins
 )
endforeach ()

(not tested, but should work :-)

In this embodiment do not need to create a dummy group.
Also all the plugins are selected by default. If you want you can
to indicate return putting in DISABLED when the component is added.

If you have more questions, ask. I'll try to answer.

--
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

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.1 available for download

[Konstantin Podsvirov]

02.12.2015, 22:55, "Robert Maynard" <robert.mayn...@kitware.com>:
> We are pleased to announce that CMake 3.4.1 is now available for download.
>
> Please use the latest release from our download page:
>   https://cmake.org/download/
>
> Thanks for your support!

Good job! Thank you!

I could not miss this event. This is a good occasion to remind about
the existence of CPack "IFW" generator :-)

https://cmake.org/cmake/help/v3.4/module/CPackIFW.html

Here is a fresh not official offline installers for CMake 3.4.1 on Windows:

http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.1-win32-x86.exe

and

http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.1-win64-x64.exe

But I want to assure you that they are honestly built me personally of the 
official code of branch 'release' recently :-)

I'll be glad if somebody test these installers for themselves and to share 
their comments and suggestions.

Good luck to everyone!

--
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

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.1 available for download

[Konstantin Podsvirov]

Meet the fresh update online installers (CMake3.4.20151203):

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

and

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used them previously, then just update via "CMake Maintenance Tool".

02.12.2015, 23:55, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> 02.12.2015, 22:55, "Robert Maynard" <robert.mayn...@kitware.com>:
>>  We are pleased to announce that CMake 3.4.1 is now available for download.
>>
>>  Please use the latest release from our download page:
>>    https://cmake.org/download/
>>
>>  Thanks for your support!
>
> Good job! Thank you!
>
> I could not miss this event. This is a good occasion to remind about
> the existence of CPack "IFW" generator :-)
>
> https://cmake.org/cmake/help/v3.4/module/CPackIFW.html
>
> Here is a fresh not official offline installers for CMake 3.4.1 on Windows:
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.1-win32-x86.exe
>
> and
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.1-win64-x64.exe
>
> But I want to assure you that they are honestly built me personally of the 
> official code of branch 'release' recently :-)
>
> I'll be glad if somebody test these installers for themselves and to share 
> their comments and suggestions.
>
> Good luck to everyone!
>
> --
> 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

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

Re: [cmake-developers] Visual Studio 2013 with CMake GUI on Windows

[Konstantin Podsvirov]

What's the noise?..

QtDialog (cmake-gui) has long been going with Qt5 and the deployment in Windows 
was solved also.

Here is the latest announce CMake 3.4.0 (MSVC2013 and Qt 5.5.1):

http://public.kitware.com/pipermail/cmake-developers/2015-November/026931.html

13.11.2015, 19:53, "Brad King" <brad.k...@kitware.com>:
> On 11/13/2015 11:42 AM, Robert Dailey wrote:
>> CMake requires Qt4, which is incompatible with VS 2013 officially. I
>> do not want to apply patches to get it working.
>>
>> Is it possible to get CMake to use Qt5?
>
> CMake already supports being built with Qt5 on Windows.
>
> Configure with containing CMAKE_PREFIX_PATH to the path to
> msvc2013_64_opengl and it should be found automatically.
> Ensure Qt5Widgets_DIR points to
>
> msvc2013_64_opengl/lib/cmake/Qt5Widgets
>
> -Brad

--
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

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

[Konstantin Podsvirov]

12.11.2015, 21:57, "Robert Maynard" <robert.mayn...@kitware.com>:
> I am proud to announce that CMake 3.4.0 is now available for download at:
> https://cmake.org/download/
>
> Documentation is available at:
> https://cmake.org/cmake/help/v3.4
>
> Release notes appear below and are also published at
> https://cmake.org/cmake/help/v3.4/release/3.4.html

Good job! Thank you!

I could not miss this event. This is a good occasion to remind about
the existence of CPack "IFW" generator :-)

https://cmake.org/cmake/help/v3.4/module/CPackIFW.html

Here is a fresh not official offline installers for CMake 3.4.0 on Windows:

http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win32-x86.exe

and

http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win64-x64.exe

But I want to assure you that they are honestly built me personally of the 
official code of branch 'release' recently :-)

I'll be glad if somebody test these installers for themselves and to share 
their comments and suggestions.

Good luck to everyone!

--
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

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

[Konstantin Podsvirov]

Meet the fresh update online installers (CMake3.4.20151113):

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

and

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used them previously, then just update via "CMake Maintenance Tool".

12.11.2015, 23:55, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> 12.11.2015, 21:57, "Robert Maynard" <robert.mayn...@kitware.com>:
>> I am proud to announce that CMake 3.4.0 is now available for download at:
>> https://cmake.org/download/
>>
>> Documentation is available at:
>> https://cmake.org/cmake/help/v3.4
>>
>> Release notes appear below and are also published at
>> https://cmake.org/cmake/help/v3.4/release/3.4.html
>
> Good job! Thank you!
>
> I could not miss this event. This is a good occasion to remind about
> the existence of CPack "IFW" generator :-)
>
> https://cmake.org/cmake/help/v3.4/module/CPackIFW.html
>
> Here is a fresh not official offline installers for 3.4.0 CMake on Windows:
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win32-x86.exe
>
> and
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win64-x64.exe
>
> But I want to assure you that they are honestly built me personally of the 
> official code of branch 'release' recently :-)
>
> I'll be glad if somebody test these installers for themselves and to share 
> their comments and suggestions.
>
> Good luck to everyone!

--
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

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

[Konstantin Podsvirov]

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" <konstan...@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.filli...@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
>> 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'

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

[Konstantin Podsvirov]

Hi all! Modern master alive! :-)

It's been almost a month and it's time to upgrade:

3.3.20150901 CMake => CMake 3.3.20151001

Dear friends, I have a question and call for help.

With my assistance the project has an option for component installation project:

CMake_INSTALL_COMPONENTS

Unfortunately not all files found your component.
The files to be installed without specifying a component fall into 
'Unspecified' component.
Need to parse them out and assign them to the component context.

Now have the components:

- cmake;
- ctest;
- cpack;
- cmake-gui;
- sphinx-man;
- sphinx-html;
- sphinx singlehtml;
- sphinx-qthelp

and General for everything else

Is Unspecified;

A list of unaccounted for 'Unspecified' of files to install on the Window is 
attached.

Links to the installers were specified earlier (see below).


On 28.07.2015, 17:49, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hi dear CMake developers!
>
> 27.07.2015, 18:52, "Brad King" <brad.k...@kitware.com>:
>> On 07/24/2015 03:46 AM, Konstantin Podsvirov wrote:
>>> To solve the problem you run cmake-gui is now possible with the
>>> the following changes:
>>
>> Applied as two separate commits with minor tweaks:
>>
>> cmake-gui: Install Qt5 Windows platform plugin
>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f0155b
>>
>> CMake: Add option CMake_INSTALL_DEPENDENCIES
>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=068e7962
>
> Code now in 'master' branch.
>
> Thanks, Brad!
>
> Meet/install/CMake built modern update on MSVC2015 c QtDialog based on Qt 5.5 
> from today :-)
>
> Windows 32bit:
>
> http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
>
> Windows 64bit:
>
> http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
>
> cmake-gui should work now, but if not, then update your system and install
>
> Visual C++ Redistributable for Visual Studio 2015 from the link below:
>
> http://www.microsoft.com/en-us/download/details.aspx?id=48145
>
> As always, questions and suggestions are welcome.

--
Regards,
Konstantin Podsvirov.:
bin/
doc/
share/
tree.txt

./bin:
cmcldeps.exe*
msvcp140.dll*
vcruntime140.dll*

./doc:
cmake-3.3/

./doc/cmake-3.3:
Copyright.txt
cmake.org.html
cmcompress/
cmcurl/
cmexpat/
cmlibarchive/
cmliblzma/
cmsys/
cmzlib/

./doc/cmake-3.3/cmcompress:
Copyright.txt

./doc/cmake-3.3/cmcurl:
COPYING

./doc/cmake-3.3/cmexpat:
COPYING

./doc/cmake-3.3/cmlibarchive:
COPYING

./doc/cmake-3.3/cmliblzma:
COPYING

./doc/cmake-3.3/cmsys:
Copyright.txt

./doc/cmake-3.3/cmzlib:
Copyright.txt

./share:
aclocal/
cmake-3.3/

./share/aclocal:
cmake.m4

./share/cmake-3.3:
Help/
Modules/
Templates/
completions/
editors/
include/

./share/cmake-3.3/Help:
command/
generator/
include/
index.rst
manual/
module/
policy/
prop_cache/
prop_dir/
prop_gbl/
prop_inst/
prop_sf/
prop_test/
prop_tgt/
release/
variable/

./share/cmake-3.3/Help/command:
FIND_XXX.txt
FIND_XXX_ORDER.txt
FIND_XXX_ROOT.txt
add_compile_options.rst
add_custom_command.rst
add_custom_target.rst
add_definitions.rst
add_dependencies.rst
add_executable.rst
add_library.rst
add_subdirectory.rst
add_test.rst
aux_source_directory.rst
break.rst
build_command.rst
build_name.rst
cmake_host_system_information.rst
cmake_minimum_required.rst
cmake_policy.rst
configure_file.rst
continue.rst
create_test_sourcelist.rst
ctest_build.rst
ctest_configure.rst
ctest_coverage.rst
ctest_empty_binary_directory.rst
ctest_memcheck.rst
ctest_read_custom_files.rst
ctest_run_script.rst
ctest_sleep.rst
ctest_start.rst
ctest_submit.rst
ctest_test.rst
ctest_update.rst
ctest_upload.rst
define_property.rst
else.rst
elseif.rst
enable_language.rst
enable_testing.rst
endforeach.rst
endfunction.rst
endif.rst
endmacro.rst
endwhile.rst
exec_program.rst
execute_process.rst
export.rst
export_library_dependencies.rst
file.rst
find_file.rst
find_library.rst
find_package.rst
find_path.rst
find_program.rst
fltk_wrap_ui.rst
foreach.rst
function.rst
get_cmake_property.rst
get_directory_property.rst
get_filename_component.rst
get_property.rst
get_source_file_property.rst
get_target_property.rst
get_test_property.rst
if.rst
include.rst
include_directories.rst
include_external_msproject.rst
include_regular_expression.rst
install.rst
install_files.rst
install_programs.rst
install_targets.rst
link_directories.rst
link_libraries.rst
list.rst
load_cache.rst
load_command.rst
macro.rst
make_directory.rst
mark_as_advanced.rst
math.rst
message.rst
option.rst
output_required_files.rst
project.rst
qt_wrap_cpp.rst
qt_wrap_ui.rst
remove.rst
remove_definitions.rst
return.rst
separate_arguments.rst
set.rst
set_directory_properties.rst
set_property.rst
set_source_files_properties.rst
set_target_properties.rst
set_tests_properties.rst
site_name.rst
source_group.rst
string.rst
subdir_depends.rst
subdirs.rst
target_compile

Re: [cmake-developers] [PATCH] FindOpenSSL: Imported Targets Release Note

[Konstantin Podsvirov]

Hi, Brad!

29.09.2015, 22:56, "Brad King" <brad.k...@kitware.com>:
> On 9/29/2015 1:19 AM, Konstantin Podsvirov wrote:
>> reflect this in the release notes.
>
> Good catch. Applied, thanks:
>
> Help: Add notes for topic 'FindOpenSSL-imported-targets'
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0429c384
>
> -Brad

Had to do it immediately. I understand it now.
For my contributions on the topic CPackIFW you made notes.
Now I have learned and try to follow the changes notes.

Done before freeze :-)

--
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

[cmake-developers] [PATCH] FindOpenSSL: Imported Targets Release Note

[Konstantin Podsvirov]

Hello, dear developers!

With this commit the module provides :
http://cmake.org/gitweb?p=cmake.git;a=commit;h=a0dab7b774d5b7a619fd26926c2faf11f9d70309

Then I forgot to reflect this in the release notes.

Patch attached.

--
Regards,
Konstantin PodsvirovFrom 12762e88f9961785c0f5484b01afb957c43ff798 Mon Sep 17 00:00:00 2001
From: Konstantin Podsvirov <konstan...@podsvirov.pro>
Date: Tue, 29 Sep 2015 08:11:04 +0300
Subject: [PATCH] FindOpenSSL: Imported Targets Release Note

---
 Help/release/dev/FindOpenSSL-imported-targets.rst | 4 
 1 file changed, 4 insertions(+)
 create mode 100644 Help/release/dev/FindOpenSSL-imported-targets.rst

diff --git a/Help/release/dev/FindOpenSSL-imported-targets.rst b/Help/release/dev/FindOpenSSL-imported-targets.rst
new file mode 100644
index 000..0c4767a
--- /dev/null
+++ b/Help/release/dev/FindOpenSSL-imported-targets.rst
@@ -0,0 +1,4 @@
+FindOpenSSL-imported-targets
+
+
+* The :module:`FindOpenSSL` module now provides imported targets.
-- 
2.5.0.windows.1

-- 

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

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

[Konstantin Podsvirov]

The first 100 views!
The interest is there (though not great), but where are the questions and 
suggestions?

09.09.2015, 21:12, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
> Hi, Dear Developers!
>
> Want to advertise a development environment that I am developing.
> The emergence of this environment would be impossible without two fundamental 
> technologies incorporated in it.
>
> Firstly is CMake, which you can use to build very much!
> Secondly - this is a new set of tools for creating cross-platform installers 
> for desktop QtIFW.
>
> Not without my contribution to their ligament - CPack IFW generator.
>
> I am developing this project for about one year and I want to share my 
> results, and in return get valuable feedback from users.
>
> I started with Windows, which sometimes are lacking in a good open solutions. 
> But the technology can be extended to other desktops.
>
> Project status I appreciate Betta, but quite stable and very functional.
>
> Official website of the project:
>
> http://dad.podsvirov.pro
>
> If the project is gaining popularity, then I'll accept links to new mirrors 
> for removing the load from my server.
>
> rsync//download.podsvirov.pro
>
> Main module - main :-)
>
> I write it in a list for developers that would first obtain a qualified 
> appraisal.
>
> Looking forward to your answers, questions and suggestions.
>
> Happy programming!
>
> --
> Regards,
> Konstantin Podsvirov

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

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

[Konstantin Podsvirov]

10.09.2015, 16:06, "Curtis Mitch" <mitch.cur...@theqtcompany.com>:
>  What is it, really?
>
>  Personally I read the email and had no idea, and it didn't make me want to 
> follow the link to find out.

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 linking and headers of any of the participating 
modules.

This is a quick start for the development of the project on the basis of 
submitted modules:

* Curses
* ZLib
* LibPNG
* Jpeg
* Libxml2
* LibTIFF
* Perl
* OpenSSL
* LibSSH2
* cURL
* PCRE
* PROJ
* Expat
* FreeType
* SQLite
* GEOS
* GDAL
* Boost
* Qt
* QtIFW
* CMake
* KDSoap
* OSG
* osgEarth
* osgQtQuick
* PostgreSQL
* The Apache.Apr
* The Apache.AprUtil
* The Apache.Httpd
* Protobuf
* gRPC
* MapServer

Now this is only for Windows (MSVC2013) but can be extended.

There is a notion of stability, as in Debian: stable, testing, unstable.

Stable modules were assembled about a year ago.
Testing is very fresh.
Unstable installers can now not be considered.

>  > - Original Message-
>>  From: development-bounces+mitch.curtis=theqtcompany@qt-project.org
>>  [mailto:development-bounces+mitch.curtis=theqtcompany....@qt-project.org]
>>  On Behalf Of Konstantin Podsvirov
>>  Sent: Thursday, 10 September 2015 3:02 PM
>>  To: CMake Developers <cmake-developers@cmake.org>; development@qt
>>  project.org
>>  Subject: Re: [Development] [ANNOUNCE] Dad's House! (Beta)
>>
>>  The first 100 views!
>>  The interest is there (though not great), but where are the questions and
>>  suggestions?
>>
>>  09.09.2015, 21:12, "Konstantin Podsvirov" <konstan...@podsvirov.pro>:
>>  > Hi, Dear Developers!
>>  >
>>  > Want to advertise a development environment that I am developing.
>>  > ...
>>  > Happy programming!

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

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

[Konstantin Podsvirov]

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

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

[Konstantin Podsvirov]

It is set of modules (now tools and libraries) for development and deployment.23:11, 10 сентября 2015 г., Alexander Neundorf <neund...@kde.org>:On Thursday, September 10, 2015 16:02:23 Konstantin Podsvirov wrote: The first 100 views! The interest is there (though not great), but where are the questions and suggestions?the web page is quite short on details...It's not an IDE, is it a set of scripts ?Alex
-- 

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

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

[Konstantin Podsvirov]

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.filli...@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.

I know how well to build projects of their own and others :-)

To sign application I haven't learned.
We are talking about signing themselves installers or applications 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 and versions 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
> 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 managed by family CMake 
scripts. Some provide package configurations to import. Some can be found with 
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, say from 
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
> <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:
>&g

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

[Konstantin Podsvirov]

Hi, Dear Developers!

Want to advertise a development environment that I am developing.
The emergence of this environment would be impossible without two fundamental 
technologies incorporated in it.

Firstly is CMake, which you can use to build very much!
Secondly - this is a new set of tools for creating cross-platform installers 
for desktop QtIFW.

Not without my contribution to their ligament - CPack IFW generator.

I am developing this project for about one year and I want to share my results, 
and in return get valuable feedback from users.

I started with Windows, which sometimes are lacking in a good open solutions. 
But the technology can be extended to other desktops.

Project status I appreciate Betta, but quite stable and very functional.

Official website of the project:

http://dad.podsvirov.pro

If the project is gaining popularity, then I'll accept links to new mirrors for 
removing the load from my server.

rsync//download.podsvirov.pro

Main module - main :-)

I write it in a list for developers that would first obtain a qualified 
appraisal.

Looking forward to your answers, questions and suggestions.

Happy programming!

--
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

[cmake-developers] [FEATURE REQUEST] ExternalProject disable all GIT_SUBMODULES

[Konstantin Podsvirov]

In the next CMake we obtain the following useful thing: http://www.cmake.org/cmake/help/git-master/release/dev/ExternalProject_init_selected_submodules.html But how to disable the initialization and loading of git submodules? --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

Re: [cmake-developers] [PATCH] Imported OpenSSL

[Konstantin Podsvirov]

Hello, Brad!

Again OpenSSL :-)

Topic branch (for reference)
http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-imported-openssl

11.08.2015, 22:35, Gregor Jasny gja...@googlemail.com:
 On 07/08/15 13:22, Konstantin Podsvirov wrote:
 Hi developers and experts OpenSSL!

 I added a little boring and dense of code at the end FindOpenSSL.cmake 
 module.
 I just want to have imported the OpenSSL library for creating relocatable 
 packages.

 I created a theme topic-imported-openssl on my server:
 http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-imported-openssl

 Now I have a single commit:
 http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=b47293f212f270844dcd32e36cff2a8668080c46

 Two comments:
 + INTERFACE_LINK_LIBRARIES OpenSSL::Crypto
 + IMPORTED_LINK_INTERFACE_LIBRARIES OpenSSL::Crypto
 + IMPORTED_LINK_INTERFACE_LIBRARIES_DEBUG OpenSSL::Crypto
 + IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE OpenSSL::Crypto)

 IMHO the last three are superfluous. Also documentation states that
 IMPORTED_LINK_INTERFACE_LIBRARIES is deprecated.

Fixed:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=273183ff776e153410c04e2f564addfde62558a4

 +# This module defines :prop_tgt:`IMPORTED` target `OpenSSL::SSL` and
 +# `OpenSSL::Crypto`, if OPENSSL_SSL_LIBRARY and OPENSSL_CRYPTO_LIBRARY
 +# has been found.

 ^^^
 have been

Fixed:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=2d695eba249eec20eafdc32873d150342f3ee926

 Thanks,
 Gregor

11.08.2015, 16:05, Brad King brad.k...@kitware.com:
 On 08/07/2015 07:22 AM, Konstantin Podsvirov wrote:
 I created a theme topic-imported-openssl on my server:
 http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-imported-openssl

 Thanks. Please revise the patch to add the IMPORTED_CONFIGURATIONS
 target property listing the configurations that exist. See the
 FindQt4, FindGSL, and FindGTK2 modules for examples.

Fixed:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=33c2ea3908cdb196dfc88266480497106ea28649

 Also please add a test. Grep in the Tests directory for FindGSL
 to see the structure of how we're testing find modules.

Fixed:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=a50228237f9dfffd856362fd68b61260520c0848
http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=56ceb2dc3414246665510802e938ad9f1c60ed46

I checked the test c for Windows options:
-DCMake_TEST_FindOpenSSL=ON -DOPENSSL_ROOT_DIR=path

For me it works.

 Thanks,
 -Brad

Brad, please consider the changes and the possibility of their application.

--
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

[cmake-developers] [PATCH] Imported OpenSSL

[Konstantin Podsvirov]

Hi developers and experts OpenSSL!

I added a little boring and dense of code at the end FindOpenSSL.cmake module.
I just want to have imported the OpenSSL library for creating relocatable 
packages.

I created a theme topic-imported-openssl on my server:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/topic-imported-openssl

Now I have a single commit:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=b47293f212f270844dcd32e36cff2a8668080c46

If I did everything correctly, then please apply my changes or to help with 
advice or deed :-)

--
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

[cmake-developers] The naming convention SHARED and STATIC

[Konstantin Podsvirov]

Encourage best practices. For example, I want to export one and the same library in one package in debug and release configurations. What do you name CMake targets and how to name files?
-- 

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

Re: [cmake-developers] The naming convention SHARED and STATIC

[Konstantin Podsvirov]

Addition: SHARED and STATIC too (mylibstatic and mylibshared?)16:39, 5 августа 2015 г., Konstantin Podsvirov konstan...@podsvirov.pro:Encourage best practices. For example, I want to export one and the same library in one package in debug and release configurations. What do you name CMake targets and how to name files? 
-- 

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

Re: [cmake-developers] [REVIEW REQUEST] find_package(Protobuf CONFIG)

[Konstantin Podsvirov]

Hi, Brad!

03.08.2015, 23:26, Brad King brad.k...@kitware.com:
 On 08/02/2015 03:31 PM, Konstantin Podsvirov wrote:
 https://github.com/google/protobuf/pull/673

 [snip]
 I try to make find_package(Protobuf [MODULE|CONFIG]) compatible.

 Thanks for working on this. Thanks for the FindProtobuf module
 compatibility layer. I tried your changes locally as of commit
 5500b069 on Linux and Windows. The basic build and install works
 and I'm able to find_package(Protobuf CONFIG) from a test project.

Great! I myself have not tried Linux. Now the header files
only installs on Windows. Of course I am interested in the solution
this question and think in the near future I'll figure it out.

 The structure of the produced files looks correct at a glance.

Learning without practice is not effective, practice without training - 
destructive :-)

 The protobuf-config-version.cmake should be taught to actually
 check the version number to see if it is compatible with that
 requested. Doing so requires understanding of protbuf's
 version scheme and compatibility requirements.

Yes, I know about it. But decided to postpone until better times.

 -Brad

Brad thank you for taking the time and effort.

We hope our efforts will be useful and appreciated by other developers.

--
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

[cmake-developers] [REVIEW REQUEST] find_package(Protobuf CONFIG)

[Konstantin Podsvirov]

Since may of this year, Google's Protocol Buffers are supplied with a CMake 
project to build with the MCVS by the compiler.

Related issues:

CMake issue:
http://public.kitware.com/Bug/view.php?id=14833

Protobuf issue:
https://github.com/google/protobuf/issues/578

The other day I opened a pull request:

https://github.com/google/protobuf/pull/673

I am working on this in the topic 'topic-cmake-install' here:

https://github.com/podsvirov/protobuf/tree/topic-cmake-install

or here:

http://git.podsvirov.pro/?p=google/protobuf.git;a=shortlog;h=refs/heads/topic-cmake-install

I try to make find_package(Protobuf [MODULE|CONFIG]) compatible.

I'm partial with minor modifications copied FindProtobuf.cmake
porting functions protobuf_generate_cpp.

All interested please see the code and make suggestions or to join the work.

--
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

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

[Konstantin Podsvirov]

Hi dear CMake developers!

27.07.2015, 18:52, Brad King brad.k...@kitware.com:
 On 07/24/2015 03:46 AM, Konstantin Podsvirov wrote:
  To solve the problem you run cmake-gui is now possible with the
  following changes:

 Applied as two separate commits with minor tweaks:

  cmake-gui: Install Qt5 Windows platform plugin
  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f0155b

  CMake: Add CMake_INSTALL_DEPENDENCIES option
  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=068e7962


Code now in 'master' branch.

Thanks, Brad!

Meet/install/update modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 
from today :-)

Windows 32bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

Windows 64bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

cmake-gui should work now, but if not, then update your system and install

Visual C++ Redistributable for Visual Studio 2015 from the link below:

http://www.microsoft.com/en-us/download/details.aspx?id=48145

As always, questions and suggestions are welcome.

--
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

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

[Konstantin Podsvirov]

Hi dear CMake developers!

Modern CMake requires modern platform!

To solve the problem you run cmake-gui is now possible with the following 
changes:

[PATCH]

CMake: Added option CMake_INSTALL_DEPENDENCIES

By default this option is ON
Turn OFF to disable installing runtime 3th dependencie

Addition QtDialog now installing on Windows platform plugin for Qt5

http://git.podsvirov.pro/?p=kitware/cmake.git;a=commitdiff;h=e955bd6783abdc1bf30a9e7c3d88bac3eb0acd60

Dear Brad, please consider the possibility of applying these changes.

Check out the work of these changes can on earlier installers.

cmake-gui should work now, but if not, then update your system and install

Visual C++ Redistributable for Visual Studio 2015 from the link below:

 http://www.microsoft.com/en-us/download/details.aspx?id=48145

23.07.2015, 16:47, Konstantin Podsvirov konstan...@podsvirov.pro:
 Hi Ruslan and other developers!

 23.07.2015, 16:12, Ruslan Baratov ruslan_bara...@yahoo.com:
 On 23-Jul-15 12:32, Konstantin Podsvirov wrote:
 Hi dear CMake developers!

 Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today 
 :-)

 Windows 32bit:

 http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

 Windows 64bit:

 http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

 As always, questions and suggestions are welcome.

 --
 Regards,
 Konstantin Podsvirov

 Both versions can't start because dll is missing:
 api-ms-win-crt-runtime-l1-1-0.dll
 Win 7 x64

 Ruslan

 To solve the problem quickly, you need to install Visual C++ Redistributable 
 for Visual Studio 2015 from the link below:

 http://www.microsoft.com/en-us/download/details.aspx?id=48145

 Now more interesting :-)

 Outdoor platforms may not be Universal CRT:

 http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx

 CMake uses the module InstallRequiredSystemLibraries to install 
 dependencies.
 Who is in charge here on this module? Should this module to install Universal 
 CRT
 (api-ms-win-crt-runtime-xxx.dll library) for MSVC14 ?

 --
 Regards,
 Konstantin Podsvirov

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

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

[Konstantin Podsvirov]

Hi Ruslan and other developers!

23.07.2015, 16:12, Ruslan Baratov ruslan_bara...@yahoo.com:
 On 23-Jul-15 12:32, Konstantin Podsvirov wrote:
 Hi dear CMake developers!

 Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today :-)

 Windows 32bit:

 http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

 Windows 64bit:

 http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

 As always, questions and suggestions are welcome.

 --
 Regards,
 Konstantin Podsvirov

 Both versions can't start because dll is missing:
 api-ms-win-crt-runtime-l1-1-0.dll
 Win 7 x64

 Ruslan

To solve the problem quickly, you need to install Visual C++ Redistributable 
for Visual Studio 2015 from the link below:

http://www.microsoft.com/en-us/download/details.aspx?id=48145

Now more interesting :-)

Outdoor platforms may not be Universal CRT:

http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx

CMake uses the module InstallRequiredSystemLibraries to install dependencies.
Who is in charge here on this module? Should this module to install Universal 
CRT
(api-ms-win-crt-runtime-xxx.dll library) for MSVC14 ?

--
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

[cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

[Konstantin Podsvirov]

Hi dear CMake developers!

Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today :-)

Windows 32bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

Windows 64bit:

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

As always, questions and suggestions are welcome.

--
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

Re: [cmake-developers] [PREVIEW] Meet CMake components-based cross-platform GUI installer

[Konstantin Podsvirov]

Meet fresh CMake 3.3.20150710 from branch 'master'!

08.07.2015, 22:42, Konstantin Podsvirov konstan...@podsvirov.pro:
 All kind time of day!

 This is not the official installer, but who might someday become.

 Straight to the point - here online installers

 Debian 8:

 http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

 Windows 7:

 http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

 If you have them before, you can just be updated from cmake-maintenance.

 Version for 32 bit will update the other day.

Two installer builded in Debian 8:

http://ifw.podsvirov.pro/cmake/cmake-master-i386-online.run

http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

And two installer builded in Windows 7:

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

The other day we introduced and tested a small hotfix for CPack IFW generator.
Changes in branch master and should soon get into the next release.

If some kind person can build installer under MacOS it will be possible to 
please
and lovers of apples.

If you have any questions, feel free to ask them.

--
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

[cmake-developers] [PATCH] CPackIFW: Variable CPACK_IFW_FRAMEWORK_VERSION cheking

[Konstantin Podsvirov]

Hi, Brad!

A very small patch single commit from multiple rows in a topic branch 
'cpack-ifw-generator' on my server:

http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/cpack-ifw-generator

Here is the commit itself:

CPackIFW: Variable CPACK_IFW_FRAMEWORK_VERSION cheking

http://git.podsvirov.pro/?p=kitware/cmake.git;a=commit;h=2d8a3bd27b2f2be911a3c8c30dd667460281beaf

I found that CPack IFW generator does not work on the basis QtIFW 2.0 and above 
for projects which include
CPackIFW.cmake module... This hotfix corrects this chip :-)

Will be asked to contribute, what would this change was brought in release 3.3.

--
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

Re: [cmake-developers] [PATCH] Option CMAKE_INSTALL_COMPONENTS and IFW installer

[Konstantin Podsvirov]

06.07.2015, 21:01, Brad King brad.k...@kitware.com:
 On 07/03/2015 09:09 AM, Konstantin Podsvirov wrote:
 About 6 months ago I started a topic cmake-install-components.
 Today I am ready to share the results.

 Great, thanks! The changes look good except for comments below.

 So as not to disturb those who do not need it I have added the
 option CMAKE_INSTALL_COMPONENTS, which by default is set to OFF.

 Please rename this to CMake_INSTALL_COMPONENTS. We've started
 a convention of using CMake_ options for affecting the build
 of CMake itself and CMAKE_ for general CMake-defined options
 that could be used by any project.

Done! It's just. When I was choosing a name for the option in SPHINX 
documentation I have not found
of such recommendations.
In QtDialog variable CMake_GUI_DISTRIBUTE_WITH_Qt_LGPl to install the license.
I have considered this option in the installer, but it is not declared as 
optional in the framework of the CMake project.

 In this hunk:

 -install(TARGETS cmake cpack ctest DESTINATION bin)
 +# Install tools
 +
 +set(_tools cmake cpack ctest)
 +
 if(APPLE)
 - install(TARGETS cmakexbuild DESTINATION bin)
 + list(APPEND _tools cmakexbuild)
 endif()

 +foreach(_tool in ${_tools})
 + install(TARGETS ${_tool} DESTINATION bin COMPONENT ${_tool})
 +endforeach()

 The cmakexbuild tool is an implementation detail of cmake/ctest/cpack
 that must be installed along with them. Whatever that enforces those
 three components are required should cover cmakexbuild too.

Done! I added cmakexbuild component in the group of Tools like cmake, ctest, 
and cpack.
This should work for APPLE, but I have no way to check it out.
Maybe someone can collect IFW installer on the APPLE platform?

 Thanks,
 -Brad

The project has many minor installation instructions. They are all now 
accounted for and installed as Unspecified component that hide from the user's 
eyes. It is not excluded that eventually they will find the name of the 
component and the location of the installation tree.

I used rebase. The last 8 commits in a branch on my server contain change of 
topic:

http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/cmake-install-components

I hope now will be able to apply the changes.

--
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

Re: [cmake-developers] [PATCH] Option CMAKE_INSTALL_COMPONENTS and IFW installer

[Konstantin Podsvirov]

Hi, Brad!

07.07.2015, 16:21, Brad King brad.k...@kitware.com:
 On 07/07/2015 02:43 AM, Konstantin Podsvirov wrote:
 I used rebase. The last 8 commits in a branch on my server contain change of 
 topic:

 I hope now will be able to apply the changes.

 Thanks! I've applied the changes with minor tweaks to the history...

Glad to hear :-) I Apologize for the macro CMAKE_OPTIONAL_COMPONENT...

With these changes IFW installer will become even more beautiful!

Once the code gets merged into the master, I will present an online update for
wanting to look, but not wanting to build.

By the way, nothing wrong that I build and put on public display
code branch master using IFW installer?

I don't see malicious intent. If someone doesn't like it, please let me know.

--
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

[cmake-developers] [PATCH] Option CMAKE_INSTALL_COMPONENTS and IFW installer

[Konstantin Podsvirov]

Hi, Brad!

A long time ago...
About 6 months ago I started a topic cmake-install-components.
Today I am ready to share the results.

The basic idea is to use the COMPONENT option in the install command inside the 
CMake.

So as not to disturb those who do not need it I have added the option 
CMAKE_INSTALL_COMPONENTS,
which by default is set to OFF.

CMake IFW installer recognizes this option.

In the attachment to the letter patch file and screenshots of what I did.

Also these changes are reflected in the branch on my server:
http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/cmake-install-components

I have tested in Windows and Debian for QtIFW 2.0.

Please consider my code and apply it.

Changes quite a lot and I'm ready for the discussion.

Have a nice weekend, and I'm waiting for an answer.

--
Regards,
Konstantin Podsvirovdiff --git a/CMakeCPack.cmake b/CMakeCPack.cmake
index 22ca8cf..de84bd6 100644
--- a/CMakeCPack.cmake
+++ b/CMakeCPack.cmake
@@ -65,6 +65,58 @@ if(EXISTS ${CMAKE_ROOT}/Modules/CPack.cmake)
 endif()
   endif()
 
+  # Components
+  if(CMAKE_INSTALL_COMPONENTS)
+set(_CPACK_IFW_COMPONENTS_ALL cmake ctest cpack)
+if(CMAKE_INSTALL_DEFAULT_COMPONENT_NAME)
+  set(_CPACK_IFW_COMPONENT_UNSPECIFIED_NAME
+${CMAKE_INSTALL_DEFAULT_COMPONENT_NAME})
+else()
+  set(_CPACK_IFW_COMPONENT_UNSPECIFIED_NAME Unspecified)
+endif()
+list(APPEND _CPACK_IFW_COMPONENTS_ALL ${_CPACK_IFW_COMPONENT_UNSPECIFIED_NAME})
+string(TOUPPER ${_CPACK_IFW_COMPONENT_UNSPECIFIED_NAME}
+  _CPACK_IFW_COMPONENT_UNSPECIFIED_UNAME)
+if(BUILD_CursesDialog)
+  list(APPEND _CPACK_IFW_COMPONENTS_ALL ccmake)
+endif()
+if(BUILD_QtDialog)
+  list(APPEND _CPACK_IFW_COMPONENTS_ALL cmake-gui)
+  set(_CPACK_IFW_COMPONENT_CMAKE-GUI_LICENSES set(CPACK_IFW_COMPONENT_CMAKE-GUI_LICENSES
+\LGPLv2.1\ \${CMake_SOURCE_DIR}/Licenses/LGPLv2.1.txt\))
+endif()
+if(SPHINX_MAN)
+  list(APPEND _CPACK_IFW_COMPONENTS_ALL sphinx-man)
+endif()
+if(SPHINX_HTML)
+  list(APPEND _CPACK_IFW_COMPONENTS_ALL sphinx-html)
+endif()
+if(SPHINX_SINGLEHTML)
+  list(APPEND _CPACK_IFW_COMPONENTS_ALL sphinx-singlehtml)
+endif()
+if(SPHINX_QTHELP)
+  list(APPEND _CPACK_IFW_COMPONENTS_ALL sphinx-qthelp)
+endif()
+set(_CPACK_IFW_COMPONENTS_CONFIGURATION 
+  # Components
+  set(CPACK_COMPONENTS_ALL \${_CPACK_IFW_COMPONENTS_ALL}\)
+  set(CPACK_COMPONENTS_GROUPING IGNORE)
+)
+  else()
+if(BUILD_QtDialog AND CMake_GUI_DISTRIBUTE_WITH_Qt_LGPL)
+  set(_CPACK_IFW_ADDITIONAL_LICENSES
+\LGPLv2.1\ \${CMake_SOURCE_DIR}/Licenses/LGPLv2.1.txt\)
+endif()
+  endif()
+
+  # Components scripts configuration
+  foreach(_script
+CMake
+CMake.Documentation.SphinxHTML)
+configure_file(${CMake_SOURCE_DIR}/Source/QtIFW/${_script}.qs.in
+  ${CMake_BINARY_DIR}/${_script}.qs @ONLY)
+  endforeach()
+
   if(${CMAKE_SYSTEM_NAME} MATCHES Windows)
 set(_CPACK_IFW_PACKAGE_ICON
 set(CPACK_IFW_PACKAGE_ICON \${CMake_SOURCE_DIR}/Source/QtDialog/CMakeSetup.ico\))
@@ -78,9 +130,13 @@ if(EXISTS ${CMAKE_ROOT}/Modules/CPack.cmake)
   ${CMake_BINARY_DIR}/installscript.qs @ONLY
 )
 install(FILES ${CMake_SOURCE_DIR}/Source/QtIFW/cmake.org.html
-  DESTINATION .
+  DESTINATION ${CMAKE_DOC_DIR}
 )
-set(_CPACK_IFW_PACKAGE_SCRIPT set(CPACK_IFW_COMPONENT_GROUP_CMAKE_SCRIPT \${CMake_BINARY_DIR}/installscript.qs\))
+if(CMAKE_INSTALL_COMPONENTS)
+  set(_CPACK_IFW_PACKAGE_SCRIPT ${CMake_BINARY_DIR}/CMake.qs)
+else()
+  set(_CPACK_IFW_PACKAGE_SCRIPT ${CMake_BINARY_DIR}/installscript.qs)
+endif()
   endif()
 
   if(${CMAKE_SYSTEM_NAME} MATCHES Linux)
diff --git a/CMakeCPackOptions.cmake.in b/CMakeCPackOptions.cmake.in
index 6003565..7beda8c 100644
--- a/CMakeCPackOptions.cmake.in
+++ b/CMakeCPackOptions.cmake.in
@@ -32,6 +32,7 @@ endif()
 include(@QT_DIALOG_CPACK_OPTIONS_FILE@ OPTIONAL)
 
 if(CPACK_GENERATOR MATCHES IFW)
+
   # Installer configuration
   set(CPACK_IFW_PACKAGE_TITLE CMake Build Tool)
   set(CPACK_IFW_PRODUCT_URL http://www.cmake.org;)
@@ -40,21 +41,123 @@ if(CPACK_GENERATOR MATCHES IFW)
 @CMake_SOURCE_DIR@/Source/QtDialog/CMakeSetup128.png)
   set(CPACK_IFW_PACKAGE_CONTROL_SCRIPT
 @CMake_SOURCE_DIR@/Source/QtIFW/controlscript.qs)
+
   # Uninstaller configuration
   set(CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_NAME cmake-maintenance)
+  @_CPACK_IFW_COMPONENTS_CONFIGURATION@
+  # Unspecified
+  set(CPACK_IFW_COMPONENT_@_CPACK_IFW_COMPONENT_UNSPECIFIED_UNAME@_VERSION
+@_CPACK_IFW_PACKAGE_VERSION@)
+
   # Package configuration group
   set(CPACK_IFW_PACKAGE_GROUP CMake)
+
   # Group configuration
+
+  # CMake
   set(CPACK_COMPONENT_GROUP_CMAKE_DISPLAY_NAME
 @CPACK_PACKAGE_NAME@)
   set(CPACK_COMPONENT_GROUP_CMAKE_DESCRIPTION
 @CPACK_PACKAGE_DESCRIPTION_SUMMARY@)
-  # IFW group configuration
   set(CPACK_IFW_COMPONENT_GROUP_CMAKE_VERSION
 

Re: [cmake-developers] [ANNOUNCE] CMake 3.3.0-rc3 is now ready!

[Konstantin Podsvirov]

Hi, Robert!
Dear CMake developers Hello!

26.06.2015, 21:36, Robert Maynard robert.mayn...@kitware.com:
 I am proud to announce the third CMake 3.3 release candidate.
...
 CPack
 -

 * The cpack(1) IFW generator and the CPackIFW module learned
 to support Qt Framework Installer 2.0 tools.

I will add that now CMake can not only create an installer for your project 
based
on QtIFW 2.0, but your own.

But you wouldn't believe it :-) suggest believe it!

Debian 8:
http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-Linux-i686.run
http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-Linux-x86_64.run

Windows7:
http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-win32-x86.exe
http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-win64-x64.exe

This offline installer, but very easy to do online installer with the 
possibility of further
update:

Debian 8:
http://ifw.podsvirov.pro/cmake/cmake-master-i386-online.run
http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

Windows 7:
http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

I urge everyone to try.

Want to hear the opinion of Robert about these installers. Maybe someday CMake
will also be distributed through QtIFW.

--
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

[cmake-developers] [CPackIFW] Adding QtIFW 2.0 Support (Technical Preview)

[Konstantin Podsvirov]

Online repository updated! Meet CMake 3.2.20150529 :-)

Online installers for Linux and Windows are available at the links below.

 On 29.04.2015, 16:57, Konstantin Podsvirov konstan...@podsvirov.pro:
 Two installer collected in Debian 8:

 http://ifw.podsvirov.pro/cmake/cmake-master-i386-online.run

 http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run

 Installer And two collected in Windows 7:

 http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

 http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

 The presented version of CMake (CPackIFW) already know how to work with 
 QtIFW 2.0 but not in full.
 I would like to know from users CPackIFW and QtIFW what functionality 
 demanded in the first place.
 Suggest we discuss the quality of the generated configuration files.

 Also available documentation:

 http://ifw.podsvirov.pro/cmake/doc/sphinx

 http://ifw.podsvirov.pro/cmake/doc/doxygen

Code was included in master branch and will be officially presented in CMake 3.3

cpack-ifw-updates:
http://www.cmake.org/cmake/help/git-master/release/dev/cpack-ifw-updates.html?highlight=ifw

[cmake-developers] CMake 3.3 feature freeze on 2015-06-01:
http://public.kitware.com/pipermail/cmake-developers/2015-May/025310.html

All anyone wants to try, but are too lazy to collect can use the development 
versions:
http://www.cmake.org/files/dev

Or try/be updated with the above installers :-)

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

[cmake-developers] [PATCH] CPackIFW: Added QtIFW 2.0 Support

[Konstantin Podsvirov]

Hi, Brad!

More than a month ago was be announced QtIFW 2.0:

http://blog.qt.io/blog/2015/04/07/qt-installer-framework-2-0-released

Unfortunately, version 2.0 is incompatible with version 1.x from the point of 
view of the command line interface.

Current version CPackIFW can't handle QtIFW 2.0 - it's time to fix it!

I have tried to be as careful and to keep compatibility with QtIFW 1.x.

I also a series of manual tests, and provided for everyone to evaluate CMake 
online installer:

http://public.kitware.com/pipermail/cmake-developers/2015-May/025245.html

Here's a list of my changes:

--
CPackIFW: Added QtIFW 2.0 support

Added variables (see sphinx doc):

- CPACK_IFW_VERBOSE
- CPACK_IFW_FRAMEWORK_VERSION
- CPACK_IFW_PACKAGE_START_MENU_DIRECTORY
- CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_NAME
- CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_INI_FILE
- CPACK_IFW_PACKAGE_ALLOW_NON_ASCII_CHARACTERS
- CPACK_IFW_PACKAGE_ALLOW_SPACE_IN_PATH
- CPACK_IFW_PACKAGE_CONTROL_SCRIPT

Updated himself IFW installer for QtIFW 2.0:

- Uninstaller renamed to CMake Maintenance Tool
--

Brad, please accept my changes :-)

From my public repository (branch cpakc-ifw-updates):

http://git.podsvirov.pro/?p=kitware/cmake.git;a=shortlog;h=refs/heads/cpack-ifw-updates

Or...

I tried to create .patch file based on the dir diff (I never did):

File added as an attachment.

(I'm learning git rebase - I think that all should come without problems)

Regards,
Konstantin Podsvirovdiff --git a/CMakeCPackOptions.cmake.in b/CMakeCPackOptions.cmake.in
index 5600b35..6003565 100644
--- a/CMakeCPackOptions.cmake.in
+++ b/CMakeCPackOptions.cmake.in
@@ -38,6 +38,10 @@ if(CPACK_GENERATOR MATCHES IFW)
   @_CPACK_IFW_PACKAGE_ICON@
   set(CPACK_IFW_PACKAGE_WINDOW_ICON
 @CMake_SOURCE_DIR@/Source/QtDialog/CMakeSetup128.png)
+  set(CPACK_IFW_PACKAGE_CONTROL_SCRIPT
+@CMake_SOURCE_DIR@/Source/QtIFW/controlscript.qs)
+  # Uninstaller configuration
+  set(CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_NAME cmake-maintenance)
   # Package configuration group
   set(CPACK_IFW_PACKAGE_GROUP CMake)
   # Group configuration
diff --git a/Modules/CPackIFW.cmake b/Modules/CPackIFW.cmake
index e5b7601..6649933 100644
--- a/Modules/CPackIFW.cmake
+++ b/Modules/CPackIFW.cmake
@@ -2,7 +2,7 @@
 # CPackIFW
 # 
 #
-# .. _QtIFW: http://qt-project.org/doc/qtinstallerframework/index.html
+# .. _QtIFW: http://doc.qt.io/qtinstallerframework/index.html
 #
 # This module looks for the location of the command line utilities supplied with
 # the Qt Installer Framework (QtIFW_).
@@ -33,18 +33,26 @@
 #
 # You can use the following variables to change behavior of CPack ``IFW`` generator.
 #
+# Debug
+# 
+#
+# .. variable:: CPACK_IFW_VERBOSE
+#
+#  Set to ``ON`` to enable addition debug output.
+#  By default is ``OFF``.
+#
 # Package
 # 
 #
 # .. variable:: CPACK_IFW_PACKAGE_TITLE
 #
 #  Name of the installer as displayed on the title bar.
-#  By default used :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY`
+#  By default used :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY`.
 #
 # .. variable:: CPACK_IFW_PACKAGE_PUBLISHER
 #
 #  Publisher of the software (as shown in the Windows Control Panel).
-#  By default used :variable:`CPACK_PACKAGE_VENDOR`
+#  By default used :variable:`CPACK_PACKAGE_VENDOR`.
 #
 # .. variable:: CPACK_IFW_PRODUCT_URL
 #
@@ -63,6 +71,12 @@
 #
 #  Filename for a logo is used as QWizard::LogoPixmap.
 #
+# .. variable:: CPACK_IFW_PACKAGE_START_MENU_DIRECTORY
+#
+#  Name of the default program group for the product in the Windows Start menu.
+#
+#  By default used :variable:`CPACK_IFW_PACKAGE_NAME`.
+#
 # .. variable:: CPACK_IFW_TARGET_DIRECTORY
 #
 #  Default target directory for installation.
@@ -85,6 +99,35 @@
 #  The root package name, which will be used if configuration group is not
 #  specified
 #
+# .. variable:: CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_NAME
+#
+#  Filename of the generated maintenance tool.
+#  The platform-specific executable file extension is appended.
+#
+#  By default used QtIFW_ defaults (``maintenancetool``).
+#
+# .. variable:: CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_INI_FILE
+#
+#  Filename for the configuration of the generated maintenance tool.
+#
+#  By default used QtIFW_ defaults (``maintenancetool.ini``).
+#
+# .. variable:: CPACK_IFW_PACKAGE_ALLOW_NON_ASCII_CHARACTERS
+#
+#  Set to ``ON`` if the installation path can contain non-ASCII characters.
+#
+#  Is ``ON`` for QtIFW_ less 2.0 tools.
+#
+# .. variable:: CPACK_IFW_PACKAGE_ALLOW_SPACE_IN_PATH
+#
+#  Set to ``OFF`` if the installation path cannot contain space characters.
+#
+#  Is ``ON`` for QtIFW_ less 2.0 tools.
+#
+# .. variable:: CPACK_IFW_PACKAGE_CONTROL_SCRIPT
+#
+#  Filename for a custom installer control script.
+#
 # .. variable:: CPACK_IFW_REPOSITORIES_ALL
 #
 #  The list of remote repositories.
@@ -113,6 +156,10 @@
 # Tools
 # 
 #
+# .. variable:: CPACK_IFW_FRAMEWORK_VERSION
+#
+#  The version of used