Picking a message randomly, to respond to - Can someone tell me what this
comment is referring to?
# FIXME: This should be part of Qt5 CMake scripts, but unfortunatelly
# Qt5 Mac support is missing there.
AFAIR it is about installing correct app bundle PlugIns. Qt provides half-baked
On Fri, Oct 10, 2014 at 17:59:07 +0400, Ruslan Baratov via cmake-developers
wrote:
Behavior when there's a lock that still exists (by bug/mistake) after
CMake is done running is going to be strange and possibly
hard-to-diagnose / hard-to-understand.
That's *exactly* the problem I have and
On 10/10/2014 07:45 AM, Ruslan Baratov wrote:
file(TRY_LOCK /path/to/file result) # try to lock and return TRUE on
success (needed?)
file(LOCK ...) # lock until unlock (unlock by further code (what if
exit/crashed?) or by deamon)
The LOCK signature should have a timeout after which it
On 10/13/2014 10:34 AM, Ben Boeckel wrote:
Maybe we need something like the 'trap' shell builtin which runs code on
various triggers
That would first require an 'eval' equivalent in CMake, e.g. cmake_eval().
This has been requested a few times.
-Brad
--
Powered by www.kitware.com
Please
Following the topic branch to separately maintain each type of search path,
I'm working on adding a feature for cross-compiling to separately control
how each type of search path gets re-rooted. Currently, the options
CMAKE_FIND_ROOT_PATH_MODE_{INCLUDE_LIBRARY_PROGRAM} can be set to ONLY,
NEVER,
On 10/13/2014 05:54 AM, Adam Strzelecki wrote:
Qt provides half-baked CMake support
Side note: this is not a fair characterization of Qt's support for CMake.
Qt5 is an outstanding example of how an upstream can make it easy to use
a project with CMake even when the upstream itself does not use
On 10/09/2014 04:58 PM, Eric Noulard wrote:
Hi everybody,
This message is an open request to find volunteer maintainers for
CPackRPM and CPackDeb
which were my main contributions to CPack (CPackDeb was initially
contributed by Mathieu).
I have 21 Mantis tickets
On 10/13/2014 01:36 PM, Micha Hergarden wrote:
With this mail I would like to help out maintaining these modules.
Wonderful, thanks!
To others: this does not close the call. We can have more than
one maintainer with overlapping responsibilities.
Micha, please start by taking a look at the
Hi Brad,(Sorry for the late answer (again).)I addressed your comments in the files attached to this email (please see the remarks below). I have not yet addressed your comment about “MATLAB_ADDITIONAL_VERSIONS” but I think it is a better proposition, so I will do it next.I updated the
Hello,
I have been talking with Eric for the past few days now and would also like
to help out with maintaining these two modules.
I am a CMake user for about six years now and have also been using CPackRPM
but for now I haven no experience with CPackDeb.
As suggested by Eric I'll start with
On 10/13/2014 03:51 PM, Domen Vrankar wrote:
would also like to help out with maintaining these two modules.
Thanks for volunteering too!
As suggested by Eric I'll start with issue tracker:
http://public.kitware.com/Bug/view.php?id=13176
Sounds good!
Thanks,
-Brad
--
Powered by
Side note: this is not a fair characterization of Qt's support for CMake.
(…)
Furthermore, all the CMake-related files come with Qt5 and are maintained
there rather than in CMake. This is much easier than Qt4, where FindQt4
in CMake has needed maintenance with every new upstream version.
Of
Adam Strzelecki wrote:
But to be fair, Qt team is really welcoming and open for improvements, I
am sure complete support will arrive sooner or later.
As the person who wrote what Qt ships, I can say that it won't be 'complete'
sooner or later unless someone with enough interest
Hi,
I extended the proposed patch for ticket 13176 with:
- documentation section
- CPACK_RPM_component_PACKAGE_DESCRIPTION fallback to
CPACK_COMPONENT_compName_DESCRIPTION
- handling of cases when one component sets its variable and the other
doesn't
Regards,
Domen
--
Powered by
14 matches
Mail list logo
