[CMake] Support for colored makefile output with tmux

2016-03-25 Thread Mike Lui
When I use tmux and set my TERM to either 'tmux' or 'tmux-256color', I
don't get colorized output of from cmake generated Makefiles.

Is this a known issue?

On 4.4.5-1-ARCH w/  CMake 3.5.0
-- 

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_SIZEOF_VOID_P is unset when building libgit2 on Windows

2016-03-25 Thread Gregor Jasny via CMake
On 25/03/16 22:11, Sebastian Schuberth wrote:
> I also just realized CMAKE_C_ABI_COMPILER is set to FALSE in
> CMakeCCompiler.cmake. Looking at CMakeError.log was a good hint. I
> found:
> 
> ---8<---
> Building C object CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj
> 
> C:/Ruby-DevKit/mingw/bin/gcc.exe-fPIC-o
> CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj   -c "C:/Program
> Files (x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c"
> 
> /usr/bin/sh: -c: line 0: syntax error near unexpected token `('
> /usr/bin/sh: -c: line 0: `C:/Ruby-DevKit/mingw/bin/gcc.exe-fPIC
> -o CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj   -c \C:/Program
> Files (x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c\'
> CMakeFiles/cmTC_c0166.dir/build.make:65: recipe for target
> 'CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj' failed
> ---8<---

To unblock you until the problem is sorted out you might want to install
a 64bit version of cmake which should not have the problematic (x86) in
the path (or you choose a custom install location).

http://ifw.podsvirov.pro/cmake/files/v3.5/

Hope that helps,
Gregor

-- 

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_SIZEOF_VOID_P is unset when building libgit2 on Windows

2016-03-25 Thread Sebastian Schuberth

On 3/24/2016 16:53, Brad King wrote:


Configuring libgit2 fails as CMake does not set CMAKE_SIZEOF_VOID_P
(nor CMAKE_C_SIZEOF_DATA_PTR), see the attached CMakeCCompiler.cmake file.

I tried to search CMake's source code to find out how the value of
@CMAKE_C_SIZEOF_DATA_PTR@ is determined in CMakeCCompiler.cmake.in,
but I failed. Does anyone have suggestions on how to debug this further,
or what the possible root causes might be?


It is supposed to be done here:

  
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeDetermineCompilerABI.cmake;hb=v3.5.0#l23
  
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeCCompilerABI.c;hb=v3.5.0

The try_compile produces a binary file that encodes strings with the
information.  Then we use file(STRINGS) to parse the strings right out
of the binary.  The INFO:sizeof_dptr[...] string contains the size of
data pointer types.

Check CMakeFiles/CMake{Output,Error}.log to see if anything went wrong
with that step that was logged.  Otherwise you can add debugging code.


I also just realized CMAKE_C_ABI_COMPILER is set to FALSE in
CMakeCCompiler.cmake. Looking at CMakeError.log was a good hint. I
found:

---8<---
Building C object CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj

C:/Ruby-DevKit/mingw/bin/gcc.exe-fPIC-o
CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj   -c "C:/Program
Files (x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c"

/usr/bin/sh: -c: line 0: syntax error near unexpected token `('
/usr/bin/sh: -c: line 0: `C:/Ruby-DevKit/mingw/bin/gcc.exe-fPIC
-o CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj   -c \C:/Program
Files (x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c\'
CMakeFiles/cmTC_c0166.dir/build.make:65: recipe for target
'CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj' failed
---8<---

There seems to be some problem in escaping the non-alphanumeric chars
in the path to "CMakeCCompilerABI.c". Any hint how to debug this
further?

Regards,
Sebastian


--

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] Fortran submodule cannot be built

2016-03-25 Thread Brad King
On 03/24/2016 03:32 PM, Brad King wrote:
> CMake's approximate Fortran parser will need to be
> updated to account for submodule syntax.

I don't know if/when I'll have time to look at this myself.
If anyone is interested in working on it, please come to the
[developer list](https://cmake.org/mailman/listinfo/cmake-developers)
to discuss more details.  For reference, submodules are summarized
[here](http://fortranwiki.org/fortran/show/Submodules).

The parser is in Source/cmFortranParser.y in the CMake source tree.
There are a few problems currently:

* Submodules introduce a new syntax

module function point_dist(a, b) result(distance)

  Currently CMake parses the "module function" part and thinks
  there is a module called "function".  We cannot simply exclude
  this name because it is valid to define such a module normally.
  The parser may have to learn more about the structure of Fortran
  sources to distinguish true module definitions from these new
  "module function" and "module procedure" definitions within a
  module.  At least it may need to track the opening/closing of
  modules (module foo ... end).

* The submodule syntax

submodule (points) points_a

  can be used to define the "points" module with no explicit
  "module points", as shown on the fortranwiki page.  CMake will
  need to learn this syntax.

* It needs to be determined whether there are cases that CMake's
  dependency scanning needs to be aware of the ".smod" files.

-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


Re: [CMake] Delete CDash project

2016-03-25 Thread Aaron Boxer
Never mind - you can do this using the not very obvious "unsubscribe"
option in manage subscription.

On Fri, Mar 25, 2016 at 10:43 AM, Aaron Boxer  wrote:

> Does anyone know how to delete a CDash project? There doesn't seem to be
> any way to do this on the website.
>
> Thanks!
> Aaron
>
-- 

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] Delete CDash project

2016-03-25 Thread Aaron Boxer
Does anyone know how to delete a CDash project? There doesn't seem to be
any way to do this on the website.

Thanks!
Aaron
-- 

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] Visual Studio + Ninja?

2016-03-25 Thread Robert Dailey
Thanks for the feedback. I know for sure that you can create
"Makefile" projects in Visual Studio, that do nothing but run
commands. You can even still have files in the project itself, to
allow you to edit those files (even though they won't actually build).

I think CMake can use this functionality already, it just isn't setup
to treat Visual Studio as an extra generator like most other IDEs.

On Mon, Mar 7, 2016 at 3:18 AM, Nagy-Egri Máté Ferenc
 wrote:
> Short version: no.
>
>
>
> Long version: Visual Studio is heavily built around MSBuild as the back-end
> of execution of various tasks. While theoretically it could be done that
> MSBuild only acts as a relay and calls into Ninja scripts, you would lose
> the entire feature set of Solution Explorer, which is quite a large portion
> of the IDE. (Using CMake does preclude using most of it though.) MS is
> looking into deeper CMake integration into their IDE, but the exec back-end
> will most likely be MSBuild.
>
>
>
> Should you really want to achieve this, you would need support from both
> CMake side and VS side. You would need to develop an Add-In with a custom
> project type (CMake+Ninja) and hook up most Solution Explorer entries to
> generate not MSBuild but Ninja script portions. And from CMake you would
> need a generator for this mixed generator type. It could be done, but it’s a
> lot of effort. Given the performance of MSBuild (which is not that bad
> compared to Ninja), the benefits would only be substantial in enourmous
> projects. MS generally looks into increasing build throughput by integrating
> IncrediBuild into their IDE.
>
>
>
>
>
>
>
> Feladó: Robert Dailey
> Elküldve: 2016. március 2., szerda 21:45
> Címzett: CMake
> Tárgy: [CMake] Visual Studio + Ninja?
>
>
>
> Right now I am using a toolchain file to setup cmake to build my C++
>
> code against Android NDK. I also have several custom targets for
>
> running 'ant' commands for the java portions.
>
>
>
> I can use the Ninja generator to generate the build scripts to make my
>
> builds work fine. However, I'd love to be able to use Visual Studio on
>
> Windows as my IDE. However, there is no "Visual Studio - Ninja"
>
> generator that I can see. Is there a way to make Visual Studio wrap
>
> the Ninja scripts and simply execute them? that way I can use it to
>
> edit code and invoke builds.
>
>
>
> Thanks in advance.
>
> --
>
>
>
> 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_RPM_PACKAGE_AUTOPROV' doesn't work when pack existing binaries with CPack

2016-03-25 Thread Domen Vrankar
> Does someone know why this "CPACK_RPM_PACKAGE_AUTOPROV" option doesn't take
> effect? how can I make it auto generates these 'PROVIDES' information in the
> RPM?  thanks for your time and it will be very appreciated if you can
> provide some hints.

CPackRPM relies on rpmbuild and other rpm tools to correctly create
the package and rpm is not the most automation friendly beast because
of its macro system.

In cmake tests: Tests/RunCMake/CPack/RPM/DEPENDENCIES-specifics.cmake
there is a comment

# FIXME auto autoprov is not tested at the moment as Ubuntu 15.04 rpmbuild
# does not use them correctly: https://bugs.launchpad.net/rpm/+bug/1475755

I'm guessing that this is environment related (missing packages,
failing/missing rpm macros, ...) as for the same version of rpmbuild
installed on different Linux distros (each through their own package
repository that came with the distro) it either worked or not and
never told that it failed (you could see that only after inspecting
the content of rpm package after it has already been created). I
haven't looked deeper into it but perhaps you've stumbled across this
as well.

You could try to make the package on a different distro and see if it
works there.

Regards,
Domen
-- 

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] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack existing binaries with CPack

2016-03-25 Thread Wang, Peng 1. (Nokia - CN/Hangzhou)
Hi,

In my project, I use cmake to construct the building system, I need to build an 
external project(here, I take zeromq for example) with ExternalProject_add, 
then pack the compiled binaries in a RPM package, but I need the generated RPM 
to have correct "PROVIDES" information to tell which libraries it provides, 
just like below

libzmq.so.5()(64bit)
zeromq = 4.1.2-1.el7
zeromq(x86-64) = 4.1.2-1.el7

But somehow, with setting CPACK_RPM_PACKAGE_AUTOPROV to 1, the built RPM still 
doesn't have correct 'PROVIDES' information, I will get 'PROVIDES' information 
below, without the provided libraries information

zeromq = 4.1.2-1
zeromq(x86-64) = 4.1.2-1

the CMakeLists.txt(just some key content) for this is

cmake_minimum_required (VERSION 3.4.0 FATAL_ERROR)
set(COMP zeromq)
set(CompVersion 4.1.2)
set(CompURL http://download.zeromq.org/zeromq-${CompVersion}.tar.gz)
set(CompMD5 159c0c56a895472f02668e692d122685)

project(${COMP}  VERSION ${CompVersion})
include(ExternalProject)

ExternalProject_add(${COMP}
  PREFIX${COMP}
  URL   ${CompURL}
  URL_MD5   ${CompMD5}
  CONFIGURE_COMMAND /configure --without-libsodium 
--prefix=${CMAKE_INSTALL_PREFIX})

install(FILES ${CMAKE_INSTALL_PREFIX}/lib/libzmq.so.5
  ${CMAKE_INSTALL_PREFIX}/lib/libzmq.so
  ${CMAKE_INSTALL_PREFIX}/lib/libzmq.so.5.0.0
DESTINATION lib64)

string(REPLACE "." ";" VERSION_LIST ${PROJECT_VERSION})
list(LENGTH VERSION_LIST VERSION_LIST_LENGTH)
list(GET VERSION_LIST 0 CPACK_PACKAGE_VERSION_MAJOR)
list(GET VERSION_LIST 1 CPACK_PACKAGE_VERSION_MINOR)
if(VERSION_LIST_LENGTH GREATER 2)
  list(GET VERSION_LIST 2 CPACK_PACKAGE_VERSION_PATCH)
endif()


set(CPACK_GENERATOR "RPM")
set(CPACK_PACKAGE_VENDOR "Test")
set(CPACK_RPM_PACKAGE_GROUP "3rd-party-software")
set(CPACK_RPM_PACKAGE_AUTOPROV 1)
set(CPACK_RPM_PACKAGE_AUTOREQ 0)

set(CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST_ADDITION
  /usr/lib
  /usr/lib64)
set(CPACK_RPM_COMPONENT_INSTALL OFF)

include(CPack)

Does someone know why this "CPACK_RPM_PACKAGE_AUTOPROV" option doesn't take 
effect? how can I make it auto generates these 'PROVIDES' information in the 
RPM?  thanks for your time and it will be very appreciated if you can provide 
some hints.

Wang Peng (Rex)



-- 

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