[cmake-developers] OpenWatcom wMake and VERBOSE=1

2014-09-24 Thread J Decker
VERBOSE=1 only triggers the first level to be verbose in a make... any
subsequent call to wmake passes '-s' option and not VERBOSE=1
continuously...

I'm not sure where the '-s' option on wmake is coming from, browsed the
code a little... but it'd be kind of nice if this feature worked.
-- 

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] Integrate fixdep for kconfig

2014-09-24 Thread Sam H.
Hi,

I would like to use kconfig from Linux for my project settings.
So I integrate fixdep tools into CMake for parsing CONFIG_xxx key words
and set proper dependency of files that are generated by kconfig.
My scratch is attached.

However, here come some issues.
1. The codes from fixdep is declared as GPL. But CMake use BSD.
2. fixed use mmap(). But this API is not support well on Windows.

So could any expert in CMake development give me some recommendations?

Thanks,
Sam


cmake_kconfig.diff.gz
Description: GNU Zip compressed data
-- 

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] stage/compact-status-log

2014-09-24 Thread Adam Strzelecki
FYI stage/compact-status-log was updated with more elegant C++ implementation 
introducing new cmStdoutFilter  cmThread utility classes enabled when certain 
headers are present in the system, so in cmakemain.cxx we simply put:

  cmStdoutFilter stdoutFilter(-- );


--Adam
-- 

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] [OSX CMake.dmg] Replace 10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Adam Strzelecki
Not an big issue but official DMG bundles are 40 MB where my manually built one 
is 21 MB (half of it).

So any reason for:
* providing universal FAT binaries instead of 64-bit only for =10.6 Darwin64 
build, as anyway there is 32-bit build for these who have 32-bit only CPU?
* using DMG zlib compression instead bzip2 for all builds which is available 
for 10.4+ and provides much better compression ratio?

--Adam

-- 

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] Windows shader compile options

2014-09-24 Thread Christopher Maughan
I've been playing with the Windows shader options.  I can see that it's now
possible to set the following:

set_property(SOURCE ${PIXELSHADER_FILES} PROPERTY VS_SHADER_TYPE Pixel)
set_property(SOURCE ${VERTEXSHADER_FILES} PROPERTY VS_SHADER_TYPE Vertex)

Which is cool, but I can't see if there's a way to specify the other
options to the shader compiler, such as output header file, shader model,
etc.  Is there a way to do that, or is it a TODO?
-- 

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] stage/compact-status-log

2014-09-24 Thread Brad King
On 09/24/2014 08:02 AM, Adam Strzelecki wrote:
 cmThread utility class

Introducing threads is exactly the too much infrastructure
to which I was referring in my previous response.  I'm sorry
to reject all the effort you put into the threads approach so
far, but I did say this earlier.

 cmake emits simply too much (redundant) information.

IIRC the original reason for having separate

   -- Looking for iconv.h
   -- Looking for iconv.h - Found

lines is that the first one prints what is about to be
done in case something happens (e.g. crash) that prevents
the second output from ever showing up.  That helps a lot
in tracking down the problem.  If another thread buffers
the first message then it might not show up at all.  The
terminal escape codes approach does not have that problem.

The same de-dup you do in the threaded filter could be done
with a shell alias that pipes 'cmake' output through a sed
script or something to de-dup it.  That would handle local
interactive terminal use of cmake without any upstream
changes.

-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


Re: [cmake-developers] [PATCH] stage/compact-status-log

2014-09-24 Thread Chuck Atkins
I like the idea of reducing the extra-verbose output, and maybe I'm missing
something here but could this possibly be done with a much simpler
approach?  It seems the way these double messages happen is with the
following CMake code:

message(STATUS Doing something)
# Do some stuff
message(STATUS Doing something - Result)

Couldn't the same thing be achieved in a platform agnostic way by adding a
NOENDL option (or something similar) to the message command?  Then you
could achieve the same result with:

message(STATUS Doing something NOENDL)
# Do some stuff
message(STATUS  - Result)

Just a bit of logic to add the NOENDL option and then another to omit the
message prefix if the previous call used NOENDL.  It seems this could
achieve the compact log result, do it in a platform agnostic way, and also
provide the useful feature to the message command for users.  It would be a
two-step process: first, enhance the message command, second, update the
various .cmake files in Sources/Modules to leverage the new syntax.

Just my 2 cents.

- Chuck

On Wed, Sep 24, 2014 at 8:36 AM, Brad King brad.k...@kitware.com wrote:

 On 09/24/2014 08:02 AM, Adam Strzelecki wrote:
  cmThread utility class

 Introducing threads is exactly the too much infrastructure
 to which I was referring in my previous response.  I'm sorry
 to reject all the effort you put into the threads approach so
 far, but I did say this earlier.

  cmake emits simply too much (redundant) information.

 IIRC the original reason for having separate

-- Looking for iconv.h
-- Looking for iconv.h - Found

 lines is that the first one prints what is about to be
 done in case something happens (e.g. crash) that prevents
 the second output from ever showing up.  That helps a lot
 in tracking down the problem.  If another thread buffers
 the first message then it might not show up at all.  The
 terminal escape codes approach does not have that problem.

 The same de-dup you do in the threaded filter could be done
 with a shell alias that pipes 'cmake' output through a sed
 script or something to de-dup it.  That would handle local
 interactive terminal use of cmake without any upstream
 changes.

 -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

-- 

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] stage/compact-status-log

2014-09-24 Thread Brad King
On 09/24/2014 09:44 AM, Chuck Atkins wrote:
 message(STATUS Doing something NOENDL)
 # Do some stuff
 message(STATUS  - Result)

What happens if something else occurs in between that prints
a message?  Do we tolerate

 -- Doing something-- Unrelated Message
 - Result

instead of

 -- Doing something
 -- Unrelated Message
 -- Doing something - Result

? Also the approach needs to work in ccmake where only one
status line is shown at a time.

-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


Re: [cmake-developers] Extracting target metadata, IDE integration

2014-09-24 Thread Brad King
On 09/22/2014 07:15 PM, Aleix Pol wrote:
 {
 version: 1.0,
 targets: [...]
 }

Yes.  The version number could either be maintained as its own
thing, or just the CMake version number could be used.  Either way
the Help/variable/CMAKE_OUTPUT_PROJECT_TARGETS.rst documentation
should specify the format of each version.

BTW, the phrase output project targets is not particularly
clear without knowing the feature already.  Perhaps some other
name like CMAKE_EXPORT_IDE_METADATA would be better?

 I've never worked with those, but it sounds like it would make sense. What 
 about:
 
 {
 version: ..
 configurations: {
 { name: Debug, targets: [...] },
 { name: Release, targets: [...] }
 }
 }

Yes, something like that.  I think you meant to use [] rather than
{} around the list of configurations.  In the case that there is
only one configuration for the generator we should still use a
list but have only one entry.

-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


Re: [cmake-developers] [OSX CMake.dmg] Replace 10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Robert Maynard
I believe that the reason for both of these behaviors is that the
DragNDrop generator was written when a significant number of  10.6
machines existed in the wild.

I don't see any reason why we shouldn't update the default for
CPACK_DMG_FORMAT to be UDBZ instead of UDZO

On Wed, Sep 24, 2014 at 8:26 AM, Adam Strzelecki o...@java.pl wrote:
 Not an big issue but official DMG bundles are 40 MB where my manually built 
 one is 21 MB (half of it).

 So any reason for:
 * providing universal FAT binaries instead of 64-bit only for =10.6 Darwin64 
 build, as anyway there is 32-bit build for these who have 32-bit only CPU?
 * using DMG zlib compression instead bzip2 for all builds which is available 
 for 10.4+ and provides much better compression ratio?

 --Adam

 --

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

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] stage/compact-status-log

2014-09-24 Thread Chuck Atkins

 What happens if something else occurs in between that prints
 a message?  Do we tolerate

  -- Doing something-- Unrelated Message
  - Result

 instead of

  -- Doing something
  -- Unrelated Message
  -- Doing something - Result


Sure, why not?  There's no requirement to use the NOENDL, it would just be
an additional option.   The places where this happens is most in the
Modules/* code for system introspection.  If the code path allows for
extensive messaging in between status messages, then just don't use the
NOENDL option.  It would be entirely optional and up to whomever is writing
the CMake code whether or not to use it.  We could easily use it in most of
the system introspection modules without worry though.



 Also the approach needs to work in ccmake where only one
 status line is shown at a time.


Sure it would.  Nothing monumental would need to change though.  It
currently output's every message separately, but it could just output the
current message append to the previous message and then when an endline is
found then clear the append message buffer.

I'm not saying it should be done this way, just offering an alternate
approach that might be more flexible.  The details and tests would still
need to be worked out.
-- 

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] FindCUDA: Wrap keyword in if() string comparison

2014-09-24 Thread Brad King
On 09/22/2014 10:07 AM, Brad King wrote:
 Or, one could add the explicit PUSH/POP in modules, e.g.
 
  cmake_policy(PUSH)
  cmake_policy(SET CMP0054 NEW)
  ... module code ...
  cmake_policy(POP)

Until such time as someone wishes to port a module explicitly
with the above approach we can use the explicit dereference
approach Adam first posted.  I've applied his patch here:

 FindCUDA: Avoid if() auto-dereference in string comparisons
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=84e3fde9

-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


Re: [cmake-developers] [OSX CMake.dmg] Replace 10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Brad King
On 09/24/2014 10:07 AM, Robert Maynard wrote:
 I believe that the reason for both of these behaviors is that the
 DragNDrop generator was written when a significant number of  10.6
 machines existed in the wild.
 
 I don't see any reason why we shouldn't update the default for
 CPACK_DMG_FORMAT to be UDBZ instead of UDZO

IIUC Adam was talking about the CMake binary distribution itself,
not CPack defaults.  I don't think we should change the defaults
in a minor release, but we can change the way our official binary
is built.

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


Re: [cmake-developers] [OSX CMake.dmg] Replace 10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Robert Maynard
Okay I have just merged into next a topic that switches over the
official release to be built with UDBZ.

Once the dashboards are happy I will update the x86_64 release to not
be universal binaries.

On Wed, Sep 24, 2014 at 10:15 AM, Brad King brad.k...@kitware.com wrote:
 On 09/24/2014 10:07 AM, Robert Maynard wrote:
 I believe that the reason for both of these behaviors is that the
 DragNDrop generator was written when a significant number of  10.6
 machines existed in the wild.

 I don't see any reason why we shouldn't update the default for
 CPACK_DMG_FORMAT to be UDBZ instead of UDZO

 IIUC Adam was talking about the CMake binary distribution itself,
 not CPack defaults.  I don't think we should change the defaults
 in a minor release, but we can change the way our official binary
 is built.

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


Re: [cmake-developers] [PATCH] stage/compact-status-log

2014-09-24 Thread Adam Strzelecki
 What happens if something else occurs in between that prints
 a message?

That's why my solution is completely automatic, does not require any changes in 
existing modules, and it works as desired so only:


  -- Doing something
  -- Doing something - Result

That arrive to stdout are compacted to:

  -- Doing something - Result

When anything comes in between both to stdout and stderr then compaction does 
not occur.

Also the preliminary message -- Doing something is of course emitted, but 
cursor waits on end of line instead new line, just in case we get 2nd matching 
Result line.

If next line is anything else then new line gets appended and rest goes as 
usual.


Please try to build this stage branch and try to run cmake agains cmake :) (FYI 
fixed bug preventing compiling on Linux)

--Adam

-- 

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] stage/compact-status-log

2014-09-24 Thread Brad King
On 09/24/2014 10:29 AM, Adam Strzelecki wrote:
 Please try to build this stage branch and try to run cmake

In case I was not clear the last two times:

We will *NOT* be introducing use of *THREADS* in CMake just
to filter our own output.

-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


Re: [cmake-developers] [PATCH] stage/compact-status-log

2014-09-24 Thread Adam Strzelecki
 We will *NOT* be introducing use of *THREADS* in CMake just
 to filter our own output.

Yeah, got it. Are subprocess allowed then?

 (…) just to filter our own output.

Please note that such solution that filters stdout low level is superior to 
doing it as CMake owns level because cmake may be launching some external 
program, library or whatever that also pushes something to stdout/stderr and if 
we don't take this into account then output will get likely broken.

--Adam
-- 

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] FindCUDA: Wrap keyword in if() string comparison

2014-09-24 Thread Adam Strzelecki
Again, shouldn't we consider having CMP0011 always NEW for internal modules / 
or do implicit pushpop for include when CMP0011 is NEW *OR* when included 
module is part of CMake own modules?

--Adam
-- 

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] stage/compact-status-log

2014-09-24 Thread Brad King
On 09/24/2014 10:47 AM, Adam Strzelecki wrote:
 Are subprocess allowed then?
 
 (…) just to filter our own output.
 
 Please note that such solution that filters stdout low level

Yes, but I do not think we should have to do any filtering
at all.  The output should just be written to match what
we want in the first place.

I think the delayed-\n approach is the simplest.  In the
case that the output is interrupted by other content it
almost certainly means something is going wrong anyway.

-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


Re: [cmake-developers] [PATCH] FindCUDA: Wrap keyword in if() string comparison

2014-09-24 Thread Brad King
On 09/24/2014 10:49 AM, Adam Strzelecki wrote:
 do implicit pushpop for include when CMP0011 is NEW *OR*
 when included module is part of CMake own modules

I think this would be okay, as long as NO_POLICY_SCOPE
is still honored when given explicitly to include() and
find_package().  The only reason for the pre-CMP0011
behavior and NO_POLICY_SCOPE is in case the purpose of
a module is to set policies.  None of the builtin modules
do that.

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


Re: [cmake-developers] Extracting target metadata, IDE integration

2014-09-24 Thread Aleix Pol
On Wed, Sep 24, 2014 at 3:55 PM, Brad King brad.k...@kitware.com wrote:

 On 09/22/2014 07:15 PM, Aleix Pol wrote:
  {
  version: 1.0,
  targets: [...]
  }

 Yes.  The version number could either be maintained as its own
 thing, or just the CMake version number could be used.  Either way
 the Help/variable/CMAKE_OUTPUT_PROJECT_TARGETS.rst documentation
 should specify the format of each version.

 BTW, the phrase output project targets is not particularly
 clear without knowing the feature already.  Perhaps some other
 name like CMAKE_EXPORT_IDE_METADATA would be better?

  I've never worked with those, but it sounds like it would make sense.
 What about:
 
  {
  version: ..
  configurations: {
  { name: Debug, targets: [...] },
  { name: Release, targets: [...] }
  }
  }

 Yes, something like that.  I think you meant to use [] rather than
 {} around the list of configurations.  In the case that there is
 only one configuration for the generator we should still use a
 list but have only one entry.

Sure :)



 -Brad


Hi,
Here's another iteration of the patch [1].

Basically adopts the possibility to move some information to depend on the
configuration. Currently it's only showing the I source files, I guess
location, directory and installed should be moved as well. Correct?

Aleix

[1]
New patch:
http://proli.net/meu/kdevelop/0001-cmake-Add-option-to-generate-target-metadata-for-IDE.patch
New output: http://proli.net/meu/kdevelop/ProjectTargets.json
-- 

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] Windows shader compile options

2014-09-24 Thread Gilles Khouzam
Hi Christopher,

We added the support for shaders but have only added the basic support to 
include shaders. Let me check what can be done to add the other properties.


Gilles Khouzam
Senior Development Lead
Microsoft OSG

From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of 
Christopher Maughan
Sent: Wednesday, September 24, 2014 05:29
To: cmake-developers@cmake.org
Subject: [cmake-developers] Windows shader compile options

I've been playing with the Windows shader options.  I can see that it's now 
possible to set the following:

set_property(SOURCE ${PIXELSHADER_FILES} PROPERTY VS_SHADER_TYPE Pixel)
set_property(SOURCE ${VERTEXSHADER_FILES} PROPERTY VS_SHADER_TYPE Vertex)

Which is cool, but I can't see if there's a way to specify the other options to 
the shader compiler, such as output header file, shader model, etc.  Is there a 
way to do that, or is it a TODO?
-- 

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] vs-nsight-tegra-generator topic

2014-09-24 Thread Brad King
On 09/20/2014 12:09 PM, Mourad Boufarguine wrote:
 On 09/19/2014 10:28 AM, Brad King wrote:
 Interesting.  I started with an IDE-generated project file to
 see what the generator needs to produce.  What version of
 Nsight Tegra are you using?

 I'm using Nsight Tegra 1.6.

I used 1.5.1 originally.  It looks like the use of JCompile
is new in 1.6.  I've added a mapping:

 VS: Map Nsight Tegra file types in .vcxproj files
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1167882a

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


Re: [CMake] CMAKE_INSTALL_PREFIX problem

2014-09-24 Thread Petr Kmoch
Hi Jeremy.

Does ${BUILD_BIN} perhaps start with a slash? If so, it would be
interpreted as an absolute path, which of course ignores
CMAKE_INSTALL_PREFIX.

Petr

On Wed, Sep 24, 2014 at 7:58 AM, Jeremy Ardley jeremy.ard...@gmail.com
wrote:

  I am using cmake 2.8.9 on debian wheezy. I'm fairly new to using cmake.

 My CMakelists.txt file starts with

 cmake_minimum_required(VERSION 2.6)
 SET(CMAKE_INSTALL_PREFIX /home/jeremy/Projects/local/)
 project(myproject)

 

 Finishing with

 INSTALL ( PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/@APPLICATION_NAME@ DESTINATION 
 @${BUILD_BIN} )

 which installs in my target directory, but under a tree prefixed by the
 '@' character. i.e. /home/jeremy/Projects/local/@/sbin and equivalent.

 I'm guessing that this is a result of the fragment

 @${BUILD_BIN}

 The problem is that if I remove the '@' the INSTALL ignores the
 CMAKE_INSTALL_PREFIX

 I've experimented with different variations on the INSTALL lines to no
 success.

 Any advice on how to get my INSTALLS ending up in
 /home/jeremy/Projects/local/sbin and equivalent?

 Thanks

 --
  Jeremy Ardley

 --

 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

Re: [CMake] CMAKE_INSTALL_PREFIX problem

2014-09-24 Thread Petr Kmoch
I don't know why @ was inserted, but here's why it overrides the absolute
path: because it has no special meaning. The path then becomes @/sbin,
which is not an absolute path (doesn't start with '/'), so the install
prefix is prepended normally. Bear in mind that Unix directory and file
names can contain any characters except '/' and NUL.

About variable substitution:

${var} is the normal way to expand variables.

@var@ is primarily intended for use with configure_file(). I believe it
works during normal CMake runs as well, but don't use it like that, it will
only add confusion.

Petr

P.S. Please keep the list in copy when replying.

On Wed, Sep 24, 2014 at 8:45 AM, Jeremy Ardley jeremy.ard...@gmail.com
wrote:

  It was

 set (BUILD_BIN /sbin)

 Removing that fixed the problem. Thanks!

 Curious why my IDE inserted the '@' (kdevelop 3) And more so why it
 overrides the absolute path?

 I need to discover more about value substitution :=(

 @somekey@ vs ${somekey}


 On 24/09/14 14:39, Petr Kmoch wrote:

  Hi Jeremy.

  Does ${BUILD_BIN} perhaps start with a slash? If so, it would be
 interpreted as an absolute path, which of course ignores
 CMAKE_INSTALL_PREFIX.

 Petr

 On Wed, Sep 24, 2014 at 7:58 AM, Jeremy Ardley jeremy.ard...@gmail.com
 wrote:

  I am using cmake 2.8.9 on debian wheezy. I'm fairly new to using cmake.

 My CMakelists.txt file starts with

 cmake_minimum_required(VERSION 2.6)
 SET(CMAKE_INSTALL_PREFIX /home/jeremy/Projects/local/)
 project(myproject)

 

 Finishing with

 INSTALL ( PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/@APPLICATION_NAME@ 
 DESTINATION @${BUILD_BIN} )

 which installs in my target directory, but under a tree prefixed by the
 '@' character. i.e. /home/jeremy/Projects/local/@/sbin and equivalent.

 I'm guessing that this is a result of the fragment

 @${BUILD_BIN}

 The problem is that if I remove the '@' the INSTALL ignores the
 CMAKE_INSTALL_PREFIX

 I've experimented with different variations on the INSTALL lines to no
 success.

 Any advice on how to get my INSTALLS ending up in
 /home/jeremy/Projects/local/sbin and equivalent?

 Thanks

 --
  Jeremy Ardley

 --

 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




 --
  Jeremy Ardley

-- 

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] CMAKE_INSTALL_PREFIX problem

2014-09-24 Thread Jeremy Ardley
Thanks for assistance. I forgot 'reply all'. Will be better next time :-)

On 24/09/14 14:58, Petr Kmoch wrote:
 I don't know why @ was inserted, but here's why it overrides the
 absolute path: because it has no special meaning. The path then
 becomes @/sbin, which is not an absolute path (doesn't start with
 '/'), so the install prefix is prepended normally. Bear in mind that
 Unix directory and file names can contain any characters except '/'
 and NUL.

 About variable substitution:

 ${var} is the normal way to expand variables.

 @var@ is primarily intended for use with configure_file(). I believe
 it works during normal CMake runs as well, but don't use it like that,
 it will only add confusion.

 Petr

 P.S. Please keep the list in copy when replying.

 On Wed, Sep 24, 2014 at 8:45 AM, Jeremy Ardley
 jeremy.ard...@gmail.com mailto:jeremy.ard...@gmail.com wrote:

 It was

 set (BUILD_BIN /sbin)

 Removing that fixed the problem. Thanks!

 Curious why my IDE inserted the '@' (kdevelop 3) And more so why
 it overrides the absolute path?

 I need to discover more about value substitution :=(

 @somekey@ vs ${somekey}


 On 24/09/14 14:39, Petr Kmoch wrote:
 Hi Jeremy.

 Does ${BUILD_BIN} perhaps start with a slash? If so, it would be
 interpreted as an absolute path, which of course ignores
 CMAKE_INSTALL_PREFIX.

 Petr

 On Wed, Sep 24, 2014 at 7:58 AM, Jeremy Ardley
 jeremy.ard...@gmail.com mailto:jeremy.ard...@gmail.com wrote:

 I am using cmake 2.8.9 on debian wheezy. I'm fairly new to
 using cmake.

 My CMakelists.txt file starts with

 cmake_minimum_required(VERSION 2.6)
 SET(CMAKE_INSTALL_PREFIX /home/jeremy/Projects/local/)
 project(myproject)

 

 Finishing with

 INSTALL ( PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/@APPLICATION_NAME@ 
 DESTINATION @${BUILD_BIN} )

 which installs in my target directory, but under a tree
 prefixed by the '@' character. i.e.
 /home/jeremy/Projects/local/@/sbin and equivalent.

 I'm guessing that this is a result of the fragment

 @${BUILD_BIN}

 The problem is that if I remove the '@' the INSTALL ignores
 the CMAKE_INSTALL_PREFIX

 I've experimented with different variations on the INSTALL
 lines to no success.

 Any advice on how to get my INSTALLS ending up in
 /home/jeremy/Projects/local/sbin and equivalent?

 Thanks

 -- 
 Jeremy Ardley

 --

 Powered by www.kitware.com http://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




 -- 
 Jeremy Ardley




-- 
Jeremy Ardley
-- 

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] CPack WIX examples

2014-09-24 Thread Nils Gladitz

On 24.09.2014 02:40, jmerkow wrote:

It seems the best way to do this would be to override the template with a
number of configurable entries?
So I could add something like (there's about 15 of em):
Registry Id='regid7' Root='HKLM' Key='Software\@proj_name@\@proj_name@
@proj_FULL_VERSION@' Name='HomeDir' Action='write' Type='string'
Value='[INSTALL_ROOT]@home_path@' /

I wanted to check to see if there was a way to handle this directly from
CMake.



The Registry elements will require a Component parent and that 
component needs to be referenced by an existing feature.
I've used CPACK_WIX_PATCH_FILE (e.g. the fragment_injection example) to 
insert similar content into existing components.

The patch file could also be configured by configure_file().

If you need this to be an independent Component I suppose you could 
use your own template,
add the Component (and its Registry childen) to the Product 
element and add a reference

to it from within the existing FeatureRef Id=ProductFeature/ element.

Nils


--

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] How to get custom commands to build in parallel ?

2014-09-24 Thread Glenn Coombs
I am already using /MP and the equivalent to the /maxcpucount.  It is the
/MP one that is important in this context as I am only concerned with
improving the speed of a single project out of the many in my solution.  I
believe the problem is with cmake rather than with Visual Studio as I can
select any of the other projects in the same solution and build them in
isolation and they will build their object files in parallel.  For some
reason cmake isn't seeing the custom commands as something it can run in
parallel.

--
Glenn

On 23 September 2014 16:20, Robert Maynard robert.mayn...@kitware.com
wrote:

 If you are using VS2013 you should look at the /maxcpucount flag which
 allows msbuild to build multiple projects at the same time. You will
 have to manually balance /MP and /maxcpucount as they cause a P*C
 number of processes to execute.

 On Tue, Sep 23, 2014 at 11:05 AM, Glenn Coombs glenn.coo...@gmail.com
 wrote:
  I have the following code in one of my CMakeLists.txt files:
 
  set(feature_files_h)
  set(feature_files_cpp)
 
  macro(create_feature_files NAME)
  add_custom_command(
  OUTPUT ${FEATURES_OUTPUT_DIR}/${NAME}.cpp
  ${FEATURES_OUTPUT_DIR}/${NAME}.h
  DEPENDS ${FEATURES_INPUT_DIR}/${NAME}.txt
  WORKING_DIRECTORY ${SIM_ROOT}/tools/features
  COMMAND perl ${FEATURES_PERL_PATH} -s${FEATURES_INPUT_DIR}
  -d${FEATURES_OUTPUT_DIR} -f${NAME}
  )
  list(APPEND feature_files_h   ${FEATURES_OUTPUT_DIR}/${NAME}.h)
  list(APPEND feature_files_cpp ${FEATURES_OUTPUT_DIR}/${NAME}.cpp)
  endmacro()
 
  create_feature_files(example_features)
  create_feature_files(fme_core_features)
  create_feature_files(fme_features)
  create_feature_files(front_end_features)
  create_feature_files(inloop_filter_features)
 
  add_library(${PROJECT_NAME} STATIC ${feature_files_cpp}
 ${feature_files_h}
  ${SIM_ROOT}/tools/features/cpp-code/cfeatures.cpp)
 
  which creates a library from an existing source file called cfeatures.cpp
  and from a bunch of auto-generated .cpp and .h files.  The whole thing
 works
  fine and runs the perl script to create each of the auto-generated files
  before creating the library.  The only problem I have with it is that it
 is
  quite slow and I would like to speed it up by having it run the perl
  commands to create the auto-generated files in parallel.  Currently,
 each of
  the auto-generated cpp files is generated sequentially, then they are all
  compiled in parallel and the library created in the final step.
 
  I'm using cmake 3.0.0 with Visual Studio 2013 Express Edition.  And I've
  added the /MP option so that Visual Studio will do parallel builds.  I've
  also set the Projects and Solutions=Build and Run=maximum number of
  parallel project builds option to 4.  This works well with all the
 normal
  cpp files in other projects and I easily see all 4 cpu cores maxxed out.
  But when building this project only 1 cpu core is used.
 
  Can anybody tell me how to change it so that the auto-geneated files are
  created in parallel as well ?
 
  --
  Glenn
 
 
  --
 
  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

Re: [CMake] Ninja generator fail for QNX on Windows

2014-09-24 Thread Cristian Adam
Hendrik Sattler post@... writes:

 On 23. September 2014 16:22:40 MESZ, Cristian Adam 
  QCC compiler generates for this project dependency files which look
 like:
 
  c:\projects\my_proj\include\/a.h \
  c:\projects\my_proj\src\/a.cpp \
  c:\projects\my_proj\other\..\/include/b.h \
  c:\projects\my_proj\other\..\/src/b.cpp \
 
 To me it looks more like a bug in qcc.
 Does qcc generates the same broken files when not used in context of 
 CMake or ninja?

 It should only use one kind of separator for directories.
 
 HS
 

It might be a bug in qcc.

I've tried to compile CMake with ninja and here are a few dependency files: 

[c:\Projects\cmake-2.8.12.2-build\Source\kwsys\CMakeFiles\cmsys.dir\
Base64.c.o.d]

Source\kwsys\CMakeFiles\cmsys.dir\Base64.c.o: \
 C:\Projects\cmake-2.8.12.2\Source\kwsys\Base64.c \
 C:\Projects\cmake-2.8.12.2\Source\kwsys\/kwsysPrivate.h \
 Source/cmsys/Base64.h Source/cmsys/Configure.h

[c:\Projects\cmake-2.8.12.2-build\Utilities\KWIML\test\CMakeFiles\
cmIML_test.dir\test_ABI_C.c.o.d]

Utilities\KWIML\test\CMakeFiles\cmIML_test.dir\test_ABI_C.c.o: \
 C:\Projects\cmake-2.8.12.2\Utilities\KWIML\test\test_ABI_C.c \
 C:\Projects\cmake-2.8.12.2\Utilities\KWIML\test\/test.h \
 Utilities/cmIML/ABI.h Utilities\KWIML\test/test_ABI_endian.h


The following patch to ninja fixed my problem with the \/ pair:

diff -Naur ninja-master-orig/src/depfile_parser.in.cc
ninja-master/src/depfile_parser.in.cc
--- ninja-master-orig/src/depfile_parser.in.cc  2014-09-17
22:00:32.0 +0200
+++ ninja-master/src/depfile_parser.in.cc   2014-09-24
08:29:03.869714200 +0200
@@ -67,6 +67,11 @@
 *out++ = '$';
 continue;
   }
+  '\\/' {
+// QCC case on Windows where in some cases \/ were generated.
+*out++ = '\\';
+continue;
+  }
   '\\' [^\000\r\n] {
 // Let backslash before other characters through verbatim.
 *out++ = '\\';

Everything is fine now! ^_^

Cheers,
Cristian.

-- 

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] How to get custom commands to build in parallel ?

2014-09-24 Thread Robert Maynard
/MP flag is specifically for compiling object files in parallel so it
won't cause multiple custom commands to be run in parallel as each one
is a msbuild custom build item task. I don't know exactly how msbuild
treats custom tasks such as these, but they might be implicitly
serial.


On Wed, Sep 24, 2014 at 3:27 AM, Glenn Coombs glenn.coo...@gmail.com wrote:
 I am already using /MP and the equivalent to the /maxcpucount.  It is the
 /MP one that is important in this context as I am only concerned with
 improving the speed of a single project out of the many in my solution.  I
 believe the problem is with cmake rather than with Visual Studio as I can
 select any of the other projects in the same solution and build them in
 isolation and they will build their object files in parallel.  For some
 reason cmake isn't seeing the custom commands as something it can run in
 parallel.

 --
 Glenn

 On 23 September 2014 16:20, Robert Maynard robert.mayn...@kitware.com
 wrote:

 If you are using VS2013 you should look at the /maxcpucount flag which
 allows msbuild to build multiple projects at the same time. You will
 have to manually balance /MP and /maxcpucount as they cause a P*C
 number of processes to execute.

 On Tue, Sep 23, 2014 at 11:05 AM, Glenn Coombs glenn.coo...@gmail.com
 wrote:
  I have the following code in one of my CMakeLists.txt files:
 
  set(feature_files_h)
  set(feature_files_cpp)
 
  macro(create_feature_files NAME)
  add_custom_command(
  OUTPUT ${FEATURES_OUTPUT_DIR}/${NAME}.cpp
  ${FEATURES_OUTPUT_DIR}/${NAME}.h
  DEPENDS ${FEATURES_INPUT_DIR}/${NAME}.txt
  WORKING_DIRECTORY ${SIM_ROOT}/tools/features
  COMMAND perl ${FEATURES_PERL_PATH} -s${FEATURES_INPUT_DIR}
  -d${FEATURES_OUTPUT_DIR} -f${NAME}
  )
  list(APPEND feature_files_h   ${FEATURES_OUTPUT_DIR}/${NAME}.h)
  list(APPEND feature_files_cpp ${FEATURES_OUTPUT_DIR}/${NAME}.cpp)
  endmacro()
 
  create_feature_files(example_features)
  create_feature_files(fme_core_features)
  create_feature_files(fme_features)
  create_feature_files(front_end_features)
  create_feature_files(inloop_filter_features)
 
  add_library(${PROJECT_NAME} STATIC ${feature_files_cpp}
  ${feature_files_h}
  ${SIM_ROOT}/tools/features/cpp-code/cfeatures.cpp)
 
  which creates a library from an existing source file called
  cfeatures.cpp
  and from a bunch of auto-generated .cpp and .h files.  The whole thing
  works
  fine and runs the perl script to create each of the auto-generated files
  before creating the library.  The only problem I have with it is that it
  is
  quite slow and I would like to speed it up by having it run the perl
  commands to create the auto-generated files in parallel.  Currently,
  each of
  the auto-generated cpp files is generated sequentially, then they are
  all
  compiled in parallel and the library created in the final step.
 
  I'm using cmake 3.0.0 with Visual Studio 2013 Express Edition.  And I've
  added the /MP option so that Visual Studio will do parallel builds.
  I've
  also set the Projects and Solutions=Build and Run=maximum number of
  parallel project builds option to 4.  This works well with all the
  normal
  cpp files in other projects and I easily see all 4 cpu cores maxxed out.
  But when building this project only 1 cpu core is used.
 
  Can anybody tell me how to change it so that the auto-geneated files are
  created in parallel as well ?
 
  --
  Glenn
 
 
  --
 
  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


[CMake] I broke get_preresiquites

2014-09-24 Thread Richard Shaw
Ok, I have no idea what's going on.

I'm using configure_file to put the get_preresiquites cmake script in the
binary dir...
It's running...
It's not show any errors...

It's also not finding any dependencies...

I've double and triple checked that the variable I'm using in the message
command is the same as what I'm using in get_preresiquites.

But manually running objdump gives the correct output:

$ objdump -p src/fldigi.exe | grep DLL Name:
DLL Name: ADVAPI32.dll
DLL Name: libfltk.dll
DLL Name: libfltk_images.dll
DLL Name: libgcc_s_sjlj-1.dll
DLL Name: libintl-8.dll
DLL Name: KERNEL32.dll
DLL Name: msvcrt.dll
DLL Name: libpng16-16.dll
DLL Name: libportaudio-2.dll
DLL Name: libwinpthread-1.dll
DLL Name: libsamplerate-0.dll
DLL Name: SHELL32.DLL
DLL Name: libsndfile-1.dll
DLL Name: libstdc++-6.dll
DLL Name: USER32.dll
DLL Name: WS2_32.dll
DLL Name: WSOCK32.DLL

Thanks,
Richard
-- 

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] I broke get_preresiquites

2014-09-24 Thread David Cole via CMake
If you send some code, maybe somebody can spot something wrong with the code...

On Wed, Sep 24, 2014 at 9:57 AM, Richard Shaw hobbes1...@gmail.com wrote:
 Ok, I have no idea what's going on.

 I'm using configure_file to put the get_preresiquites cmake script in the
 binary dir...
 It's running...
 It's not show any errors...

 It's also not finding any dependencies...

 I've double and triple checked that the variable I'm using in the message
 command is the same as what I'm using in get_preresiquites.

 But manually running objdump gives the correct output:

 $ objdump -p src/fldigi.exe | grep DLL Name:
 DLL Name: ADVAPI32.dll
 DLL Name: libfltk.dll
 DLL Name: libfltk_images.dll
 DLL Name: libgcc_s_sjlj-1.dll
 DLL Name: libintl-8.dll
 DLL Name: KERNEL32.dll
 DLL Name: msvcrt.dll
 DLL Name: libpng16-16.dll
 DLL Name: libportaudio-2.dll
 DLL Name: libwinpthread-1.dll
 DLL Name: libsamplerate-0.dll
 DLL Name: SHELL32.DLL
 DLL Name: libsndfile-1.dll
 DLL Name: libstdc++-6.dll
 DLL Name: USER32.dll
 DLL Name: WS2_32.dll
 DLL Name: WSOCK32.DLL

 Thanks,
 Richard

 --

 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


Re: [CMake] CPack WIX examples

2014-09-24 Thread jmerkow
Ok I'm going the fragment injection route, but having some issues.

So I found the component id for the target that these registry values will
be needed by in files.wxs:
Component Id=CMP_ID_1 Guid=*
  File Id=FILE_ID_1 Source=C:/blah/blah/Bin/myapp.exe KeyPath=yes/
/Component
In this case its 'CMP_ID_1', using the first cmp id seemed like a safe bet
in general to have it referenced by a feature.

So a configurable patch.xml.in looks something like:
CPackWiXPatch
CPackWiXFragment Id=CMP_ID_1
Registry Id='regid1' Root='HKLM'
Key='Software\myproj\@myproj_VERSION@
@myproj_MAJOR_VERSION@.@myproj_MINOR_VERSION@' Name='InstallDir'
Action='write' Type='string' Value='[INSTALL_ROOT]' /
Registry Id='regid2' ... /
...
/CPackWiXFragment
/CPackWiXPatch

There are just a few in there to test the process.

In CMake, i configure and add it the file to CPACK_WIX_PATCH_FILE:
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/windows/registry-patch.xml.in
${TEMP_DIR}/registry-patch.xml @ONLY)
set(CPACK_WIX_PATCH_FILE ${TEMP_DIR}/registry-patch.xml)

Then I generate the msi using cpack.  However the resulting msi doesn't set
any registry entries, I also don't see any of the entries anywhere in the
resulting xml.  
I did notice that in the documentations [1] and in your example your
component id is more complex..
It looks to be something like (and I'm abusing cmake generator expressions
for brevity)
Id='CM_CP_@cmake_component@.@TARGET_FILE_DIR:tgt@.@TARGET_FILE_DIR:tgt@'.  I
tried an Id of this nature as well (i.e. CPackWiXFragment
Id=CMP_CP_CoreExecutables.Bin.myapp.exe) but this also did not work.
Am I obtaining the id wrong? The documentation is a little confusing
compared to whats being generated. so I'm not sure exactly sure if I have
the proper id. Is there a way to get the Id from the in cmake to configure
the file directly?  Maybe there is another issue entirely?

-Jameson
[1]
http://www.cmake.org/cmake/help/v3.0/module/CPackWIX.html?highlight=cpack_wix_patch
[2]
https://github.com/ngladitz/cmake-wix-testsuite/tree/master/fragment_injection



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CPack-WIX-examples-tp7588561p7588591.html
Sent from the CMake mailing list archive at Nabble.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


Re: [CMake] CPack WIX examples

2014-09-24 Thread Nils Gladitz

On 24.09.2014 21:26, jmerkow wrote:

Am I obtaining the id wrong? The documentation is a little confusing
compared to whats being generated. so I'm not sure exactly sure if I have
the proper id. Is there a way to get the Id from the in cmake to configure
the file directly?  Maybe there is another issue entirely?


After running CPack with the WIX generator you will have a 
_CPack_Packages\arch\WIX directory.
Within are all the WIX sources and everything else used to build the 
installer.


In files.wxs you can find all the component definitions and their IDs.
Here you can also find your patch fragments (if they are being 
successfully applied).


Using a non existent ID in a patch file should generate an error at 
CPack time.


If you are currently successfully generating an installer with an 
invalid ID that might indicate that the patch file isn't being used at all.
Is it possible that you are using an older CMake release or that you are 
setting CPACK_WIX_PATCH_FILE after or outside the context of your 
include(CPack)?


CPack only sees the options that make it to CPackConfig.cmake which is 
generated by include(CPack).


Nils


--

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] I broke get_preresiquites

2014-09-24 Thread Richard Shaw
I figured it out...

I'm cross-compiling MinGW on Fedora linux and it just dawned on me that the
cmake instance run by CPack probably isn't using the correct environment. I
think it would be best if this was handled automatically but for the time
being I pushed the required variables into the install script to make
GetPreresiquites work correctly, at least for the most part.

The function, get_preresiquites, has an option to exclude system libraries
but it doesn't seem to be doing that for me right now.

Thanks
Richard
-- 

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] CPack WIX examples

2014-09-24 Thread jmerkow
Ok, I've double checked everything and I'm not sure whats going on.

I was looking in files.wxs (in _CPack_Packages/win64/WIX) for the component
ID, and i've tried a few different ones.  I also dropped the config file
step and used your example patch.xml:
CPackWiXPatch
CPackWiXFragment Id=CMP_ID_1
Environment Id=MyEnvironment Action=set Name=FOOBAR Value=FooBar/
/CPackWiXFragment
/CPackWiXPatch

Still nothing added when I search file.wxs for FOOBAR or anything else that
should be added with the fragment injection. I am still curious as to why
the component id's look so different between your tests and whats being
generated in my file.wxs.

That seems to leave the older version question
Is this feature new with 3+?  I am using CMake 2.8.12.2

-Jameson



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CPack-WIX-examples-tp7588561p7588594.html
Sent from the CMake mailing list archive at Nabble.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


Re: [CMake] CPack WIX examples

2014-09-24 Thread jmerkow
I forgot to mention that I double checked that this particular code was being
executed.  I started changing the name (and adding a time stamp) to the msi
in the same section of code to double check. Here is it is (its at send of
my code for cpack):

...
if(WIN32)
if(MSVC)
set(CPACK_GENERATOR WIX)
set(CPACK_WIX_PRODUCT_GUID ---)
set(CPACK_WIX_UPGRADE_GUID ---)
SET(CPACK_PACKAGE_FILE_NAME
myproj-${myproj_FULL_VERSION}-Win-x64_${TIMESTAMP}_NewTest)
set(CPACK_WIX_PATCH_FILE 
${CMAKE_CURRENT_SOURCE_DIR}/patch.xml)
endif()
endif()

include(CPack)



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CPack-WIX-examples-tp7588561p7588595.html
Sent from the CMake mailing list archive at Nabble.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


Re: [CMake] CPack WIX examples

2014-09-24 Thread Nils Gladitz

On 24.09.2014 23:20, jmerkow wrote:

Ok, I've double checked everything and I'm not sure whats going on.

I was looking in files.wxs (in _CPack_Packages/win64/WIX) for the component
ID, and i've tried a few different ones.  I also dropped the config file
step and used your example patch.xml:
CPackWiXPatch
 CPackWiXFragment Id=CMP_ID_1
Environment Id=MyEnvironment Action=set Name=FOOBAR Value=FooBar/
 /CPackWiXFragment
/CPackWiXPatch

Still nothing added when I search file.wxs for FOOBAR or anything else that
should be added with the fragment injection. I am still curious as to why
the component id's look so different between your tests and whats being
generated in my file.wxs.

That seems to leave the older version question
Is this feature new with 3+?  I am using CMake 2.8.12.2


Yes, 2.8.12 does not have CPACK_WIX_PATCH_FILE yet:
http://www.cmake.org/cmake/help/v2.8.12/cmake.html#module:CPackWIX

You would need 3.0:
www.cmake.org/cmake/help/v3.0/module/CPackWIX.html

The WIX generator is still relatively new and hasn't had as much time as 
the other generators to settle yet.
I am still in progress of adding features as requests come in which 
means that many of the more recent additions will require a more current 
CMake version.


Nils
--

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] @ONLY and nested variables

2014-09-24 Thread Nico Schlömer
Hi all,

I would like to use CONFIGURE_PACKAGE_CONFIG_FILE() [1] instead of
CONFIGURE_FILE() for my export configurations. Unfortunately, it seems
that CONFIGURE_PACKAGE_CONFIG_FILE() only supports the @ONLY syntax. I
do use nested variables names in the export configuration, though,
e.g.,
```
SET(${PACKAGE}_LIBS ${${PACKAGE}_LIBRARIES})
```
Any idea how to translate this line into @ONLY syntax? Any other ideas?

Cheers,
Nico


[1] http://www.cmake.org/cmake/help/v3.0/module/CMakePackageConfigHelpers.html
-- 

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-commits] CMake branch, master, updated. v3.0.2-1917-gefd16ba

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  efd16ba928476bc1a576efc16d61d31f0f49 (commit)
   via  e7aeb79f08dd031f5fe3fd16d6d4b644b5b97000 (commit)
  from  e6a7abd2b69b45933abb5617a8bf5b800b2dde6f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=efd16ba928476bc1a576efc16d61d31f0f49
commit efd16ba928476bc1a576efc16d61d31f0f49
Merge: e6a7abd e7aeb79
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 09:21:48 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 09:21:48 2014 -0400

Merge topic 'vs-wince-exe-entry-point'

e7aeb79f VS, WINCE: Only set EntryPointSymbol for executables


---

Summary of changes:
 Source/cmVisualStudio10TargetGenerator.cxx |   10 --
 1 file changed, 8 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v3.0.2-1913-gbe5215c

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  be5215c4ba85942a22143894048a4f160b65a87a (commit)
   via  6120fca8e229da08fae1d58017962491fb6e03f3 (commit)
  from  6bd776eba6221d9ef68b63d1c17a988145f31fc1 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=be5215c4ba85942a22143894048a4f160b65a87a
commit be5215c4ba85942a22143894048a4f160b65a87a
Merge: 6bd776e 6120fca
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 09:21:44 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 09:21:44 2014 -0400

Merge topic 'ninja-compiler-change'

6120fca8 Ninja: Prevent compilers to be silently modified


---

Summary of changes:
 Source/cmGlobalNinjaGenerator.cxx |9 +
 Tests/RunCMake/CMakeLists.txt |2 +-
 2 files changed, 10 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v3.0.2-1915-ge6a7abd

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  e6a7abd2b69b45933abb5617a8bf5b800b2dde6f (commit)
   via  92b2c6189ddbe1293989d469c214f6f306b2ed6e (commit)
  from  be5215c4ba85942a22143894048a4f160b65a87a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e6a7abd2b69b45933abb5617a8bf5b800b2dde6f
commit e6a7abd2b69b45933abb5617a8bf5b800b2dde6f
Merge: be5215c 92b2c61
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 09:21:46 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 09:21:46 2014 -0400

Merge topic 'fix-LOCATION-slashes'

92b2c618 Remove extra slashes from LOCATION target property value


---

Summary of changes:
 Source/cmTarget.cxx |5 -
 1 file changed, 5 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v3.0.2-1919-g17a457d

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  17a457dcb02e351efe5d1dd093c9443ba206667a (commit)
   via  55a885da00985823253827e2e44f9e02f2999b71 (commit)
  from  efd16ba928476bc1a576efc16d61d31f0f49 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=17a457dcb02e351efe5d1dd093c9443ba206667a
commit 17a457dcb02e351efe5d1dd093c9443ba206667a
Merge: efd16ba 55a885d
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 09:21:50 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 09:21:50 2014 -0400

Merge topic 'fix_search_path_ios_trycompile'

55a885da Teach try_compile COPY_FILE to look for IOS app bundles.


---

Summary of changes:
 Source/cmCoreTryCompile.cxx |4 
 1 file changed, 4 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v3.0.2-5437-gda8aa48

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  da8aa48b29761f697f23995b31eeb3d6179b11c3 (commit)
   via  84e3fde94db9dfa2f3fb10a85c5db6c9a78124ab (commit)
   via  17a457dcb02e351efe5d1dd093c9443ba206667a (commit)
   via  efd16ba928476bc1a576efc16d61d31f0f49 (commit)
   via  e6a7abd2b69b45933abb5617a8bf5b800b2dde6f (commit)
   via  be5215c4ba85942a22143894048a4f160b65a87a (commit)
   via  6bd776eba6221d9ef68b63d1c17a988145f31fc1 (commit)
  from  140be4fd07c907c814ea0161db3c593463b53d74 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=da8aa48b29761f697f23995b31eeb3d6179b11c3
commit da8aa48b29761f697f23995b31eeb3d6179b11c3
Merge: 140be4f 84e3fde
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 10:11:39 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 10:11:39 2014 -0400

Merge topic 'FindCUDA-cleanup-CMP0054' into next

84e3fde9 FindCUDA: Avoid if() auto-dereference in string comparisons
17a457dc Merge topic 'fix_search_path_ios_trycompile'
efd16ba9 Merge topic 'vs-wince-exe-entry-point'
e6a7abd2 Merge topic 'fix-LOCATION-slashes'
be5215c4 Merge topic 'ninja-compiler-change'
6bd776eb CMake Nightly Date Stamp


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=84e3fde94db9dfa2f3fb10a85c5db6c9a78124ab
commit 84e3fde94db9dfa2f3fb10a85c5db6c9a78124ab
Author: Adam Strzelecki o...@java.pl
AuthorDate: Wed Sep 17 13:54:29 2014 +0200
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 24 10:10:42 2014 -0400

FindCUDA: Avoid if() auto-dereference in string comparisons

This silences possible CMP0054 warnings.

diff --git a/Modules/FindCUDA.cmake b/Modules/FindCUDA.cmake
index 9348aa5..2e2b21c 100644
--- a/Modules/FindCUDA.cmake
+++ b/Modules/FindCUDA.cmake
@@ -894,15 +894,15 @@ macro(CUDA_GET_SOURCES_AND_OPTIONS _sources 
_cmake_options _options)
   set( ${_options} )
   set( _found_options FALSE )
   foreach(arg ${ARGN})
-if(arg STREQUAL OPTIONS)
+if(x${arg} STREQUAL xOPTIONS)
   set( _found_options TRUE )
 elseif(
-arg STREQUAL WIN32 OR
-arg STREQUAL MACOSX_BUNDLE OR
-arg STREQUAL EXCLUDE_FROM_ALL OR
-arg STREQUAL STATIC OR
-arg STREQUAL SHARED OR
-arg STREQUAL MODULE
+x${arg} STREQUAL xWIN32 OR
+x${arg} STREQUAL xMACOSX_BUNDLE OR
+x${arg} STREQUAL xEXCLUDE_FROM_ALL OR
+x${arg} STREQUAL xSTATIC OR
+x${arg} STREQUAL xSHARED OR
+x${arg} STREQUAL xMODULE
 )
   list(APPEND ${_cmake_options} ${arg})
 else()
diff --git a/Modules/FindCUDA/run_nvcc.cmake b/Modules/FindCUDA/run_nvcc.cmake
index 58e0d31..abdd307 100644
--- a/Modules/FindCUDA/run_nvcc.cmake
+++ b/Modules/FindCUDA/run_nvcc.cmake
@@ -126,7 +126,7 @@ endif()
 # and other return variables are present after executing the process.
 macro(cuda_execute_process status command)
   set(_command ${command})
-  if(NOT _command STREQUAL COMMAND)
+  if(NOT x${_command} STREQUAL xCOMMAND)
 message(FATAL_ERROR Malformed call to cuda_execute_process.  Missing 
COMMAND as second argument. (command = ${command}))
   endif()
   if(verbose)

---

Summary of changes:
 Modules/FindCUDA.cmake  |   14 +++---
 Modules/FindCUDA/run_nvcc.cmake |2 +-
 Source/CMakeVersion.cmake   |2 +-
 3 files changed, 9 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v3.0.2-5439-g2040bb2

2014-09-24 Thread Robert Maynard
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  2040bb2a6f3ab2121af8b04dbc49b460384b6acd (commit)
   via  561344553eeeddb314974917334c2f82621bfe88 (commit)
  from  da8aa48b29761f697f23995b31eeb3d6179b11c3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2040bb2a6f3ab2121af8b04dbc49b460384b6acd
commit 2040bb2a6f3ab2121af8b04dbc49b460384b6acd
Merge: da8aa48 5613445
Author: Robert Maynard robert.mayn...@kitware.com
AuthorDate: Wed Sep 24 10:21:08 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 10:21:08 2014 -0400

Merge topic 'build_cmake_dmg_with_bzip' into next

56134455 CMake now using bzip2 compression for mac release bundles.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=561344553eeeddb314974917334c2f82621bfe88
commit 561344553eeeddb314974917334c2f82621bfe88
Author: Robert Maynard robert.mayn...@kitware.com
AuthorDate: Wed Sep 24 10:18:52 2014 -0400
Commit: Robert Maynard robert.mayn...@kitware.com
CommitDate: Wed Sep 24 10:18:52 2014 -0400

CMake now using bzip2 compression for mac release bundles.

Starting with OSX 10.4 dmg files offers bzip2 compression which offers
small package sizes.

diff --git a/Utilities/Release/dashmacmini5_release.cmake 
b/Utilities/Release/dashmacmini5_release.cmake
index 16a30b3..d332816 100644
--- a/Utilities/Release/dashmacmini5_release.cmake
+++ b/Utilities/Release/dashmacmini5_release.cmake
@@ -7,6 +7,7 @@ set(MAKE_PROGRAM make)
 set(MAKE ${MAKE_PROGRAM} -j5)
 set(CPACK_BINARY_GENERATORS DragNDrop TGZ TZ)
 set(CPACK_SOURCE_GENERATORS TGZ TZ)
+set(CPACK_DMG_FORMAT UDBZ) #build using bzip2 for smaller package size
 set(INITIAL_CACHE 
 CMAKE_USE_OPENSSL:BOOL=ON
 
OPENSSL_CRYPTO_LIBRARY:FILEPATH=/Users/kitware/openssl-1.0.1g-install/lib/libcrypto.a

---

Summary of changes:
 Utilities/Release/dashmacmini5_release.cmake |1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v3.0.2-5444-g2dbe247

2014-09-24 Thread Stephen Kelly
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  2dbe24798a0a72535485ca08a6a1f52835baab7a (commit)
   via  96b35db6e8335a7e9b4eda2e009521406fced4a6 (commit)
   via  41fdd4f460567021ef9e59b697788ce8403a4510 (commit)
   via  4cedd8ec569ba6c0bba1fca4df0a20dd7e23061f (commit)
   via  274df2dac740f3c80b8be8b2278824b173311a0b (commit)
  from  2040bb2a6f3ab2121af8b04dbc49b460384b6acd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2dbe24798a0a72535485ca08a6a1f52835baab7a
commit 2dbe24798a0a72535485ca08a6a1f52835baab7a
Merge: 2040bb2 96b35db
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Wed Sep 24 10:26:24 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 10:26:24 2014 -0400

Merge topic 'autorcc-depends' into next

96b35db6 Add debugging information for the autorcc_depends test.
41fdd4f4 Ensure that the initial build works.
4cedd8ec Add a glob for debugging.
274df2da Exclude this test when using the Ninja generator for now.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=96b35db6e8335a7e9b4eda2e009521406fced4a6
commit 96b35db6e8335a7e9b4eda2e009521406fced4a6
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Wed Sep 24 16:22:17 2014 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Wed Sep 24 16:25:43 2014 +0200

Add debugging information for the autorcc_depends test.

The test_res1 target should not be re-built at this point because
its dependencies have not changed. Test whether the test_res1 target
is just built every time make is run.

diff --git a/Tests/QtAutogen/CMakeLists.txt b/Tests/QtAutogen/CMakeLists.txt
index 125dcff..0f53a87 100644
--- a/Tests/QtAutogen/CMakeLists.txt
+++ b/Tests/QtAutogen/CMakeLists.txt
@@ -182,6 +182,24 @@ if (NOT CMAKE_GENERATOR STREQUAL Ninja)
   file(TIMESTAMP ${qrc_file2} file2_step2 ${timeformat})
 
   if (NOT file1_step2 STREQUAL file1_step1)
+message(file1 timestamp after second build: ${file1_step2})
+
+execute_process(COMMAND ${CMAKE_COMMAND} -E sleep 1)
+execute_process(COMMAND ${CMAKE_COMMAND} --build .
+  WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/autorcc_depends
+)
+file(TIMESTAMP ${qrc_file1} file1_step3 ${timeformat})
+
+message(file1 timestamp after third build: ${file1_step3})
+
+execute_process(COMMAND ${CMAKE_COMMAND} -E sleep 1)
+execute_process(COMMAND ${CMAKE_COMMAND} --build .
+  WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/autorcc_depends
+)
+file(TIMESTAMP ${qrc_file1} file1_step4 ${timeformat})
+
+message(file1 timestamp after fourth build: ${file1_step4})
+
 message(SEND_ERROR file1 (${qrc_file1}) should not have changed in the 
second step!)
   endif()
   if (NOT file2_step2 GREATER file2_before)

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=41fdd4f460567021ef9e59b697788ce8403a4510
commit 41fdd4f460567021ef9e59b697788ce8403a4510
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Wed Sep 24 16:19:13 2014 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Wed Sep 24 16:25:43 2014 +0200

Ensure that the initial build works.

diff --git a/Tests/QtAutogen/CMakeLists.txt b/Tests/QtAutogen/CMakeLists.txt
index 04fdafa..125dcff 100644
--- a/Tests/QtAutogen/CMakeLists.txt
+++ b/Tests/QtAutogen/CMakeLists.txt
@@ -123,6 +123,9 @@ if (NOT CMAKE_GENERATOR STREQUAL Ninja)
 CMAKE_FLAGS -DQT_QMAKE_EXECUTABLE:FILEPATH=${QT_QMAKE_EXECUTABLE} 
-DQT_TEST_VERSION=${QT_TEST_VERSION}
 OUTPUT_VARIABLE output
   )
+  if (NOT RCC_DEPENDS)
+message(SEND_ERROR Initial build of autorcc_depends failed. Output: 
${output})
+  endif()
 
   set(info_file ${CMAKE_CURRENT_BINARY_DIR}/autorcc_depends/info_file.txt)
   if (NOT EXISTS ${info_file})

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4cedd8ec569ba6c0bba1fca4df0a20dd7e23061f
commit 4cedd8ec569ba6c0bba1fca4df0a20dd7e23061f
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Wed Sep 24 16:17:51 2014 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Wed Sep 24 16:25:43 2014 +0200

Add a glob for debugging.

diff --git a/Tests/QtAutogen/CMakeLists.txt b/Tests/QtAutogen/CMakeLists.txt
index d99c787..04fdafa 100644
--- a/Tests/QtAutogen/CMakeLists.txt
+++ b/Tests/QtAutogen/CMakeLists.txt
@@ -135,6 +135,8 @@ if (NOT CMAKE_GENERATOR STREQUAL Ninja)
   endif()
 endforeach()
 if (NOT info_file)
+  file(GLOB info_files 
${CMAKE_CURRENT_BINARY_DIR}/autorcc_depends/info_file* )
+  message(info_files glob: ${info_files})
   message(SEND_ERROR No valid info_file found!)
  

[Cmake-commits] CMake branch, next, updated. v3.0.2-5446-g2f91e81

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  2f91e810f7defe668176c9e57971e16ffc610f6e (commit)
   via  7a5d9256a3a9a5070c4a98b9276fb84839d31671 (commit)
  from  2dbe24798a0a72535485ca08a6a1f52835baab7a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2f91e810f7defe668176c9e57971e16ffc610f6e
commit 2f91e810f7defe668176c9e57971e16ffc610f6e
Merge: 2dbe247 7a5d925
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 10:28:29 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 10:28:29 2014 -0400

Merge topic 'remove-old-DartLocal.conf' into next

7a5d9256 Remove unused legacy 'DartLocal.conf' file


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7a5d9256a3a9a5070c4a98b9276fb84839d31671
commit 7a5d9256a3a9a5070c4a98b9276fb84839d31671
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 10:26:04 2014 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 24 10:26:04 2014 -0400

Remove unused legacy 'DartLocal.conf' file

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 14f60ae..71850de 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -552,10 +552,6 @@ endif()
 
 # setup some Testing support (a macro defined in this file)
 CMAKE_SETUP_TESTING()
-configure_file(
-  ${CMAKE_CURRENT_SOURCE_DIR}/DartLocal.conf.in
-  ${CMAKE_CURRENT_BINARY_DIR}/DartLocal.conf
-  COPYONLY)
 
 if(NOT CMake_TEST_EXTERNAL_CMAKE)
   if(NOT CMake_VERSION_IS_RELEASE)
diff --git a/DartLocal.conf.in b/DartLocal.conf.in
deleted file mode 100644
index e28cb18..000
--- a/DartLocal.conf.in
+++ /dev/null
@@ -1,121 +0,0 @@
-ExpectedBuilds: \
-{andoria.kitware Linux-g++3.4-KDevelop} \
-{andoria.kitware Linux-g++3.4-SVN} \
-{DASH1.kitware Win32-nmake71} \
-{DASH1.kitware Win32-vs71} \
-{DASH1.kitware Win32-vs71Rel} \
-{DASH1.kitware zRel24-Win32-nmake71} \
-{DASH1.kitware zRel24-Win32-vs71} \
-{DASH11.kitware zRel24-Win32-nmake71} \
-{dash14.kitware Win32-bcc5.6} \
-{dash14.kitware Win32-cygwin} \
-{dash14.kitware Win32-mingw} \
-{dash14.kitware zRel24-Win32-bcc5.6} \
-{dash17.kitware Linux-g++4.0} \
-{dash1win64.kitware Win64-vs80} \
-{dash1win98.kitware Win32-vs60} \
-{DASH2.kitware Win32-nmake70} \
-{DASH2.kitware Win32-vs70} \
-{DASH2.kitware Win32-vs70-InPlace} \
-{DASH2.kitware zRel24-Win32-nmake70} \
-{DASH2.kitware zRel24-Win32-vs70} \
-{DASH3.kitware Win32-nmake60} \
-{DASH3.kitware Win32-vs60} \
-{DASH3.kitware zRel24-Win32-nmake60} \
-{DASH3.kitware zRel24-Win32-vs60} \
-{dash4.kitware Win32-bcc5.8} \
-{DASH5.kitware Linux-gcc332-InPlace} \
-{DASH5.kitware zRel24-Linix-gcc332} \
-{DASH6.kitware zRel24-Linix-gcc332} \
-{dash8.kitware Linux64-g++} \
-{dash8.kitware Linux64-g++332} \
-{dash8.kitware Linux64-g++341} \
-{dash8.kitware zRel24-Linux64-g++} \
-{dash8.kitware zRel24-Linux64-g++332} \
-{dashmacmini1.kitware Darwin-Tiger-Xcode21} \
-{dashmacmini1.kitware zRel24-Darwin-Tiger-g++} \
-{dashmacmini2.kitware DarwinIntel-g++} \
-{dashmacmini2.kitware DarwinIntel-Universal} \
-{dashmacmini2.kitware Darwin-Tiger-Xcode21-univ} \
-{dashmacmini3.kitware Darwin-LeopardIntel-g++} \
-{dashmacmini3.kitware Darwin-LeopardIntel-Universal} \
-{dashmacmini3.kitware Darwin-Leopard-Xcode21-univ} \
-{dashsgi1.kitware IRIX32-CC} \
-{dashsgi1.kitware IRIX64-CC} \
-{dashsun1.kitware SunOS-CC} \
-{dashsun1.kitware SunOS-CC-64} \
-{dashsun1.kitware SunOS-gcc34-64} \
-{destiny.kitware HP-UX-aCC} \
-{destiny.kitware HP-UX-aCC-gmake} \
-{devqnx.acfr.usyd.edu.au qnx-V3.3.5-gcc_ntox86} \
-{grayson.kitware Win32-nmake80} \
-{heart HP-UXia64-aCC} \
-{hythloth.kitware Linux64-bullseye-cov} \
-{hythloth.kitware Linux64-suncc-5.9} \
-{hythloth.kitware Linux-nightly-win32-release} \
-{insight.journal.kitware KWStyle} \
-{iris.elemtech IRIX64-CC64-7.4} \
-{iris.elemtech IRIX64-CC-7.4} \
-{JET.kitware Linux-valgrind2} \
-{krondor.kitware Darwin-c++} \
-{krondor.kitware zRel24-Darwin-c++} \
-{midworld.kitware DarwinG5-g++} \
-{midworld.kitware DarwinG5-XCode15} \
-{midworld.kitware zRel24-DarwinG5-g++} \
-{pre.vision.cs.rpi.edu FreeBSD-CC-gmake} \
-{pre.vision.cs.rpi.edu FreeBSD-CC-make} \
-{RogueResearch3 Mac10.5-CMake-gcc-dbg-ppc} \
-{RogueResearch3 Mac10.5-CMake-gcc-dbg-ppc64} \
-{RogueResearch3 Mac10.5-CMake-gcc-rel-ppc} \
-{RogueResearch3 Mac10.5-CMake-gcc-rel-ppc64} \
-{RogueResearch3 Mac10.5-CMake-Xcode-dbg-ppc} \
-{RogueResearch3 Mac10.5-CMake-Xcode-dbg-ppc64} \
-{RogueResearch4 Mac10.5-CMake-gcc-dbg-i386} \
-{RogueResearch4 Mac10.5-CMake-gcc-dbg-rosetta} \
-{RogueResearch4 Mac10.5-CMake-gcc-rel-i386} \
-{tick.rz.uni-augsburg.de LinuxPPC-g++3.3} \

[Cmake-commits] CMake branch, next, updated. v3.0.2-5450-gd32009a

2014-09-24 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  d32009a23a164d10e49b8f3e9508ec7c60b3fe88 (commit)
   via  1167882a4b9123096908be38027e2cb261f581c7 (commit)
   via  9a6afc89c14c29344245f38be977aae9591068d7 (commit)
   via  aa0a67bf788c787cc917334192b0c1d59decc653 (commit)
  from  2f91e810f7defe668176c9e57971e16ffc610f6e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d32009a23a164d10e49b8f3e9508ec7c60b3fe88
commit d32009a23a164d10e49b8f3e9508ec7c60b3fe88
Merge: 2f91e81 1167882
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 14:32:57 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 14:32:57 2014 -0400

Merge topic 'vs-nsight-tegra-generator' into next

1167882a VS: Map Nsight Tegra file types in .vcxproj files
9a6afc89 VS: Use case-insensitive check for hlsl,jpg,png,xml file extensions
aa0a67bf cmVisualStudio10TargetGenerator: Remove unused parameter name


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1167882a4b9123096908be38027e2cb261f581c7
commit 1167882a4b9123096908be38027e2cb261f581c7
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 14:27:18 2014 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 24 14:27:18 2014 -0400

VS: Map Nsight Tegra file types in .vcxproj files

Map .java to JCompile, .asm and .s to ClCompile, and a few
Android-specific source file names to AndroidBuild.  This allows
Nsight Tegra 1.6 and above to check up-to-dateness of such sources.

diff --git a/Source/cmVisualStudio10TargetGenerator.cxx 
b/Source/cmVisualStudio10TargetGenerator.cxx
index 4e953ad..b5b99d8 100644
--- a/Source/cmVisualStudio10TargetGenerator.cxx
+++ b/Source/cmVisualStudio10TargetGenerator.cxx
@@ -1200,6 +1200,28 @@ void 
cmVisualStudio10TargetGenerator::WriteExtraSource(cmSourceFile const* sf)
 {
 tool = XML;
 }
+  if(this-NsightTegra)
+{
+// Nsight Tegra needs specific file types to check up-to-dateness.
+std::string name =
+  cmSystemTools::LowerCase(sf-GetLocation().GetName());
+if(name == androidmanifest.xml ||
+   name == build.xml ||
+   name == proguard.cfg ||
+   name == proguard-project.txt ||
+   ext == properties)
+  {
+  tool = AndroidBuild;
+  }
+else if(ext == java)
+  {
+  tool = JCompile;
+  }
+else if(ext == asm || ext == s)
+  {
+  tool = ClCompile;
+  }
+}
 
   std::string deployContent;
   if(this-GlobalGenerator-TargetsWindowsPhone() ||

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9a6afc89c14c29344245f38be977aae9591068d7
commit 9a6afc89c14c29344245f38be977aae9591068d7
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 14:25:35 2014 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 24 14:25:35 2014 -0400

VS: Use case-insensitive check for hlsl,jpg,png,xml file extensions

These extra sources should map to the proper tool even when they
are not in lower case.

diff --git a/Source/cmVisualStudio10TargetGenerator.cxx 
b/Source/cmVisualStudio10TargetGenerator.cxx
index 1c5412b..4e953ad 100644
--- a/Source/cmVisualStudio10TargetGenerator.cxx
+++ b/Source/cmVisualStudio10TargetGenerator.cxx
@@ -1180,7 +1180,7 @@ void 
cmVisualStudio10TargetGenerator::WriteExtraSource(cmSourceFile const* sf)
   bool toolHasSettings = false;
   std::string tool = None;
   std::string shaderType;
-  std::string const ext = sf-GetExtension();
+  std::string ext = cmSystemTools::LowerCase(sf-GetExtension());
   if(ext == hlsl)
 {
 tool = FXCompile;

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa0a67bf788c787cc917334192b0c1d59decc653
commit aa0a67bf788c787cc917334192b0c1d59decc653
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 24 13:48:15 2014 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 24 13:48:15 2014 -0400

cmVisualStudio10TargetGenerator: Remove unused parameter name

diff --git a/Source/cmVisualStudio10TargetGenerator.cxx 
b/Source/cmVisualStudio10TargetGenerator.cxx
index 69b0848..1c5412b 100644
--- a/Source/cmVisualStudio10TargetGenerator.cxx
+++ b/Source/cmVisualStudio10TargetGenerator.cxx
@@ -2019,7 +2019,7 @@ 
cmVisualStudio10TargetGenerator::WriteLibOptions(std::string const config)
 
 //
 void cmVisualStudio10TargetGenerator::WriteAntBuildOptions(
-  std::string const config)
+  std::string const)
 {
   // Look through the sources for AndroidManifest.xml and use
   // its 

[Cmake-commits] CMake branch, next, updated. v3.0.2-5452-gc2768d6

2014-09-24 Thread Robert Maynard
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  c2768d6897864156f644c35caf332c945ff19685 (commit)
   via  6b25938c35ef486af2e3d9af6482948d066f27c4 (commit)
  from  d32009a23a164d10e49b8f3e9508ec7c60b3fe88 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c2768d6897864156f644c35caf332c945ff19685
commit c2768d6897864156f644c35caf332c945ff19685
Merge: d32009a 6b25938
Author: Robert Maynard robert.mayn...@kitware.com
AuthorDate: Wed Sep 24 15:38:51 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 15:38:51 2014 -0400

Merge topic 'build_cmake_dmg_with_bzip' into next

6b25938c Update mac mini 2 release to use bzip2 compression.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6b25938c35ef486af2e3d9af6482948d066f27c4
commit 6b25938c35ef486af2e3d9af6482948d066f27c4
Author: Robert Maynard robert.mayn...@kitware.com
AuthorDate: Wed Sep 24 15:38:29 2014 -0400
Commit: Robert Maynard robert.mayn...@kitware.com
CommitDate: Wed Sep 24 15:38:29 2014 -0400

Update mac mini 2 release to use bzip2 compression.

diff --git a/Utilities/Release/dashmacmini2_release.cmake 
b/Utilities/Release/dashmacmini2_release.cmake
index 6a27119..ba82aab 100644
--- a/Utilities/Release/dashmacmini2_release.cmake
+++ b/Utilities/Release/dashmacmini2_release.cmake
@@ -6,6 +6,7 @@ set(HOST dashmacmini2)
 set(MAKE_PROGRAM make)
 set(MAKE ${MAKE_PROGRAM} -j2)
 set(CPACK_BINARY_GENERATORS DragNDrop TGZ TZ)
+set(CPACK_DMG_FORMAT UDBZ) #build using bzip2 for smaller package size
 set(INITIAL_CACHE 
 CMAKE_BUILD_TYPE:STRING=Release
 CMAKE_OSX_ARCHITECTURES:STRING=ppc;i386

---

Summary of changes:
 Utilities/Release/dashmacmini2_release.cmake |1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v3.0.2-5454-g2ee6f7d

2014-09-24 Thread Robert Maynard
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  2ee6f7d43da4c5a3d466915f81c9775feb2c777e (commit)
   via  ffa5db962294b70130cf4a7401381a0fc7dc338d (commit)
  from  c2768d6897864156f644c35caf332c945ff19685 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2ee6f7d43da4c5a3d466915f81c9775feb2c777e
commit 2ee6f7d43da4c5a3d466915f81c9775feb2c777e
Merge: c2768d6 ffa5db9
Author: Robert Maynard robert.mayn...@kitware.com
AuthorDate: Wed Sep 24 15:39:23 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 24 15:39:23 2014 -0400

Merge topic 'build_cmake_dmg_with_bzip' into next

ffa5db96 CMake now using bzip2 compression for mac release bundles.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ffa5db962294b70130cf4a7401381a0fc7dc338d
commit ffa5db962294b70130cf4a7401381a0fc7dc338d
Author: Robert Maynard robert.mayn...@kitware.com
AuthorDate: Wed Sep 24 10:18:52 2014 -0400
Commit: Robert Maynard robert.mayn...@kitware.com
CommitDate: Wed Sep 24 15:39:12 2014 -0400

CMake now using bzip2 compression for mac release bundles.

Starting with OSX 10.4 dmg files offers bzip2 compression which offers
small package sizes.

diff --git a/Utilities/Release/dashmacmini2_release.cmake 
b/Utilities/Release/dashmacmini2_release.cmake
index 6a27119..ba82aab 100644
--- a/Utilities/Release/dashmacmini2_release.cmake
+++ b/Utilities/Release/dashmacmini2_release.cmake
@@ -6,6 +6,7 @@ set(HOST dashmacmini2)
 set(MAKE_PROGRAM make)
 set(MAKE ${MAKE_PROGRAM} -j2)
 set(CPACK_BINARY_GENERATORS DragNDrop TGZ TZ)
+set(CPACK_DMG_FORMAT UDBZ) #build using bzip2 for smaller package size
 set(INITIAL_CACHE 
 CMAKE_BUILD_TYPE:STRING=Release
 CMAKE_OSX_ARCHITECTURES:STRING=ppc;i386
diff --git a/Utilities/Release/dashmacmini5_release.cmake 
b/Utilities/Release/dashmacmini5_release.cmake
index 16a30b3..d332816 100644
--- a/Utilities/Release/dashmacmini5_release.cmake
+++ b/Utilities/Release/dashmacmini5_release.cmake
@@ -7,6 +7,7 @@ set(MAKE_PROGRAM make)
 set(MAKE ${MAKE_PROGRAM} -j5)
 set(CPACK_BINARY_GENERATORS DragNDrop TGZ TZ)
 set(CPACK_SOURCE_GENERATORS TGZ TZ)
+set(CPACK_DMG_FORMAT UDBZ) #build using bzip2 for smaller package size
 set(INITIAL_CACHE 
 CMAKE_USE_OPENSSL:BOOL=ON
 
OPENSSL_CRYPTO_LIBRARY:FILEPATH=/Users/kitware/openssl-1.0.1g-install/lib/libcrypto.a

---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v3.0.2-1920-g93da76d

2014-09-24 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  93da76d4d8983ccbc6116a12fabe994361b5bfa3 (commit)
  from  17a457dcb02e351efe5d1dd093c9443ba206667a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=93da76d4d8983ccbc6116a12fabe994361b5bfa3
commit 93da76d4d8983ccbc6116a12fabe994361b5bfa3
Author: Kitware Robot kwro...@kitware.com
AuthorDate: Thu Sep 25 00:01:08 2014 -0400
Commit: Kitware Robot kwro...@kitware.com
CommitDate: Thu Sep 25 00:01:08 2014 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index bf53ef4..8a906fe 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 0)
-set(CMake_VERSION_PATCH 20140924)
+set(CMake_VERSION_PATCH 20140925)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits