Hi Brad,
Thanks for the quick and helpful response!
I've had a quick education on CMake variable scoping, and now realise that the
cached PYTHON_LIBRARY variable, which contains either the user-specified
library or the found release library, becomes eclipsed by a local
PYTHON_LIBRARY variable,
> I just tried, it seems to do the trick. An example source setup that was
> breaking the RPM building before, is now functioning seemingly correctly. The
> produced RPM gets the symlink, pointing at the location outside of the
> package.
>
> I would actually prefer if the code printed a warning
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=16043
==
Reported By:Zachary Turner
Assigned To:
Hi,
I just needed 'run as root' and default run arguments. I have just had a look
at adding multiple targets to a xcscheme and it looks no more complicated.
I was just generating the "BlueprintIdentifier" at random with "string(RANDOM
LENGTH 24 ALPHABET "0123456789ABCDEF" MACOSX_SCHEME_BLUEPRIN
Hello,
On 31/03/16 16:30, Harry Mallon wrote:
> This became an annoyance in our Cmake build system so here is a barebones
> xcscheme creator.
> https://github.com/hm1992/CMake/commit/5345881861a4b510d3a3283825584ec90f8d2061
>
> Current situation:
> * It seems to work for the executable targets w
On 31-Mar-16 20:37, Brad King wrote:
On 03/29/2016 11:24 AM, Ruslan Baratov wrote:
OTOH many such switches are
so specific that they should not be abstracted and can instead be
added to COMPILE_OPTIONS with a $ genex guard.
What about generating nothing for such cases?
Yes, that makes sense.
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=16042
==
Reported By:Daniele E. Domenichelli
Assigned To:
>> General warning-id's:
>>
>>* ALL
>>* DEFAULT
>>* LEVEL
>
>And `NONE`.
I'm less interested in all warnings and more interested in a clear level that
is the highest warning level that does not provide false positives is. After
setting the warning level precisely, the next step is se
Hello all,
This became an annoyance in our Cmake build system so here is a barebones
xcscheme creator.
https://github.com/hm1992/CMake/commit/5345881861a4b510d3a3283825584ec90f8d2061
Current situation:
* It seems to work for the executable targets we use in the office.
* It only supports command
On 03/31/2016 05:12 AM, Patrik Lehmann wrote:
> Please recognize attached patch.
Thanks! Applied and merged to 'next' for testing with some
formatting tweaks:
Eclipse: Implement traversal of nested source groups (#15701)
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4828a78c
-Brad
--
On 03/31/2016 07:26 AM, Yves Frederix wrote:
>> If anyone is interested in trying to implement generator expressions
>> for custom command outputs, I can provide more details to get started.
>
> I am interested in having a go at this. I recently ran into this issue
> at work as well and actually t
Hi Richard,
> The attached patch fixes this nesting issue.
Thanks for working on this. Please look at revising this to avoid
exposing the _ANYCONFIG variable. Use a "_Python_..." internal
variable that is unset, or find another way to do it without the
variable, such as `(PYTHON_RELEASE_LIBRARY
On 03/29/2016 11:24 AM, Ruslan Baratov wrote:
>> OTOH many such switches are
>> so specific that they should not be abstracted and can instead be
>> added to COMPILE_OPTIONS with a $ genex guard.
> What about generating nothing for such cases?
Yes, that makes sense. I was just discussing alternat
Hi Brad,
>
> If anyone is interested in trying to implement generator expressions
> for custom command outputs, I can provide more details to get started.
I am interested in having a go at this. I recently ran into this issue
at work as well and actually tried some things already. However, I
real
Hi,
On 28 March 2016 at 15:05, Brad King wrote:
> On 03/27/2016 06:11 AM, Dan Liew wrote:
>> OUTPUT does not accept generator expressions, why?
>
> It hasn't been implemented. At least at one time it would have been
> very hard to implement. I'm not sure now because there has been a lot
> of re
Hi all,
I also came across these FindTBB modules while in need for one. As the more
recent one from the OGRE project did not support MSVS 2015 yet, and also does
not create import targets for a more convenient and “modern” CMake use of the
TBB library targets, I wrote my own module.
Features:
Hi.
I fixed the bug [CMake 0015701] in the Eclipse Generator. The handling of
Source Groups was not correct.
Please recognize attached patch.
Kind Regards,
Patrik Lehmann
0001-CMake-0015701-Fixed-handling-of-sourceGroups-trees.patch~
Description: application/trash
--
Powered by www.kitware.
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=16041
==
Reported By:keksa
Assigned To:
18 matches
Mail list logo