The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15588
==
Reported By:Valerii Kanunik
Assigned To:
On 05/26/2015 05:28 PM, Stephen Kelly wrote:
Here are four bug reports which could be good starting points in approximate
order of difficulty, and in different areas:
http://public.kitware.com/Bug/view.php?id=15587
http://public.kitware.com/Bug/view.php?id=14669
On 05/26/2015 05:14 PM, Stephen Kelly wrote:
This would amount to a separate task of making IMPORTED_LOCATION
an error on an INTERFACE library.
Actually this is already an error case because IMPORTED_LOCATION is not
whitelisted, so nothing more to do.
Great.
+ property value\n
On 05/27/2015 01:33 PM, Nagy-Egri MC!tC) Ferenc via cmake-developers wrote:
like to see the NMake generator finally support multicore builds by
adding Batch Mode support to the generated makefiles.
For reference, Batch-Mode Rules are documented here:
On 5/27/2015 2:13 PM, Brad King wrote:
One can achieve multi-core builds without third-party tools by using
the VS IDE generators. It is still possible to build from the command
line with these.
http://www.kitware.com/blog/home/post/434
-Bill
--
Powered by www.kitware.com
Please keep
Brad King wrote:
It seems that the meaning of INTERFACE libraries is being overloaded
with the opposite of their meaning.
The meaning of INTERFACE is that it specifies usage requirements
without itself building anything.
In this, it is the same as IMPORTED libraries.
A key distinction is
Dear CMake devs,
I have a feature that I really wish someone would implement, but because I see
that nobody really wishes to act upon it, I decided I’d try myself. I would
very much like to see the NMake generator finally support multicore builds by
adding Batch Mode support to the generated
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15589
==
Reported By:Martyn Gigg
Assigned To:
On 05/27/2015 02:40 PM, Stephen Kelly wrote:
By current 'design language' it is not a 'usage requirement', just like
IMPORTED_LOCATION, LOCATION, $TARGET_FILE and others are not 'usage
requirements'.
Sure, but it does tell CMake what to do when a client consumes the
interface.
I still
Hi, this is my first post to this list.
When generating a dependency graph of a large project with many external
libraries, there are so many external libs that one doesn't see the
important dependencies any more. On top of that they have also the full
absolute path in the graph.
So with this
Brad King wrote:
On 05/27/2015 02:40 PM, Stephen Kelly wrote:
By current 'design language' it is not a 'usage requirement', just like
IMPORTED_LOCATION, LOCATION, $TARGET_FILE and others are not 'usage
requirements'.
Sure, but it does tell CMake what to do when a client consumes the
11 matches
Mail list logo
