[CMake] cmake-gui on windows and qt5 dlls

[Craig Scott]

On Fri, Aug 18, 2017 at 6:23 AM, Craig Scott <craig.scott at crascit.com>
wrote:

>
>
> On Fri, Aug 18, 2017 at 5:05 AM, Konstantin Podsvirov <
> konstantin at podsvirov.pro> wrote:
>
>> Hello Clément Gregoire!
>>
>> 17.08.2017, 21:55, "Clément Gregoire" <lectem at gmail.com>:
>> > So the following worked for me:
>> >
>> > move cmake-gui.exe, all dlls and qt.conf to a "cmkae/bin/gui" subfolder
>> >
>> > create a batch file named
>> >
>> > cmake-gui.bat
>> >
>> > with the following content
>> >
>> > @echo off
>> > start "" /B "%~dp0\gui\cmake-gui.exe" %*
>> >
>> > And modify qt.conf so that the plugin directory is correct :
>> >
>> > from      Plugins = ../plugins     to    Plugins = ../../plugins
>> >
>> > I'm not (yet) on the dev mailing list, so feel free to transfer the
>> solution there.
>>
>> Please review dev mailing list archive too:
>> http://public.kitware.com/pipermail/cmake-developers/2017-Au
>> gust/030228.html
>> (may be I forgot /B option)
>>
>
> Side note: really weird, but that email you've linked to never made it to
> my inbox (can't explain it, checked my trash and spam folders too), so I
> never saw your request to ask to test!
>
> In the past, one problem I've run into with using simple batch files as
> launcher scripts is that they can flash up a console window briefly before
> starting the real app. This can look suspicious and distracting to the
> user, so it is something to avoid. I think at one past employer we ended up
> using something like wscript instead, which allowed us to avoid that
> problem and it worked on all Windows versions without any extra software
> dependencies. Maybe we just didn't have good enough batch-file-fu, maybe
> things work differently now, I don't know. Been a number of years since
> I've looked at that specific problem. Some context, but only basic extra
> info:
>
> https://stackoverflow.com/a/9062764/1938798
>

Let me clarify the above (sorry, recalling more of the original problem we
had years back). The flashing up of a console window would occur if you ran
the launcher from somewhere other than an existing console window. For
example, if you double-clicked the launcher in Windows Explorer or via a
menu shortcut. In our case, we were using the script to set some
environment variables before launching the real app, so you always wanted
to use the launcher. In the discussion here about cmake-gui, you don't
really need that, you just want a way to forward the call to start the app
so you can avoid putting the real app and its DLLs on the PATH. So I guess
a batch file would be okay in this instance, since we would only be
expecting people to use it from a console window anyway (menu shortcuts,
etc. could still invoke the real cmake-gui app directly).


-- 
Craig Scott
Melbourne, Australia
https://crascit.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20170818/7f2fd0fd/attachment.html>