Re: [CMake] CPack: Create debian packge for each sub-project

[DKLind]

Domen,

Thanks for the reply to my question. I was aware of the Debian packaging
generator page and I also was already setting the component value to
uppercase.

As documented, I had to use PARENT_SCOPE when setting
CPACK_DEBIAN__PACKAGE_XXX values from sub-projects'
CMakeLists.txt.

Also, curious why CPACK_*COMPONENT*__DESCRIPTION is different
from the other CPACK_*DEBIAN*__PACKAGE_XXX?

With your help, I have individual packaging working now, except for unique
version. I also realize that I would like to be able to set the contributor
for some packages to be unique.

I would like to contribute to CMake. I see the page
https://cmake.org/gitweb?p=cmake.git;a=blob_plain;f=CONTRIBUTING.rst;hb=master.
It mentions submitting contributions in patch form. Are pull requests also
accepted?



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CPack-Create-debian-packge-for-each-sub-project-tp7595889p7595895.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

[CMake] Boost is planning to switch from bjam to CMake!

[Robert Dailey]

Very exciting news... hopefully it works out! Congratulations to CMake
for this; this is huge support for CMake and shows it is becoming way
more popular (not that it wasn't already!)

https://lists.boost.org/boost-interest/2017/07/0162.php?utm_content=buffera6a82&utm_medium=social&utm_source=plus.google.com&utm_campaign=buffer
-- 

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: Create debian packge for each sub-project

[DKLind]

I forgot, I also have a question about "make package". How do I build and
package just an individual sub-project. As expected, "make "
works to build, but there isn't a default target to package an individual
sub-project.



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CPack-Create-debian-packge-for-each-sub-project-tp7595889p7595897.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: Create debian packge for each sub-project

[Domen Vrankar]

2017-07-23 17:19 GMT+02:00 DKLind :

> Also, curious why CPACK_*COMPONENT*__DESCRIPTION is different
> from the other CPACK_*DEBIAN*__PACKAGE_XXX?
>

Most variables are debian package specific/allow to override general CPack
variables specifically for debian packages. For e.g. package description is
set to:
  if CPACK_DEBIAN_PACKAGE_DESCRIPTION # debian specific override
  else if CPACK_PACKAGE_DESCRIPTION_SUMMARY # general package description

There is no particular reason why per component version can't be overridden
by a debian packager specific variable - you would usually want to have a
single description for the same component no matter the package format
(deb, rpm, ...).

With your help, I have individual packaging working now, except for unique
> version. I also realize that I would like to be able to set the contributor
> for some packages to be unique.
>

Per component variable for these variables was not introduced since


> I would like to contribute to CMake. I see the page
> https://cmake.org/gitweb?p=cmake.git;a=blob_plain;f=
> CONTRIBUTING.rst;hb=master.
> It mentions submitting contributions in patch form. Are pull requests also
> accepted?
>

As described in the link that you've provided create a gitlab account here:
https://gitlab.kitware.com/cmake/cmake
and create a merge request (gitlab equivalent to pull request on github).

2017-07-23 17:37 GMT+02:00 DKLind :

> I forgot, I also have a question about "make package". How do I build and
> package just an individual sub-project. As expected, "make "
> works to build, but there isn't a default target to package an individual
> sub-project.
>

You can set CPACK_COMPONENTS_ALL variable to contain only the components
that you wish to package:

set(CPACK_COMPONENTS_ALL applications libraries headers)

By default it's set by CPack to contain all components.

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

Re: [CMake] CPack: Create debian packge for each sub-project

[Gonzalo Garramuño]

El 23/07/17 a las 12:37, DKLind escribió:

I forgot, I also have a question about "make package". How do I build and
package just an individual sub-project. As expected, "make "
works to build, but there isn't a default target to package an individual
sub-project.
AFAIK, it is not possible. I would also like to know this for separate 
packager generators. How to call "make package" on just one package 
generator (like build just DEB and not RPM).


--
Gonzalo Garramuño

--

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: Create debian packge for each sub-project

[Craig Scott]

On Mon, Jul 24, 2017 at 6:13 AM, Gonzalo Garramuño 
wrote:

>
>
> El 23/07/17 a las 12:37, DKLind escribió:
>
>> I forgot, I also have a question about "make package". How do I build and
>> package just an individual sub-project. As expected, "make "
>> works to build, but there isn't a default target to package an individual
>> sub-project.
>>
> AFAIK, it is not possible. I would also like to know this for separate
> packager generators. How to call "make package" on just one package
> generator (like build just DEB and not RPM).
>
>
If you want to pick the package generator, run cpack directly rather than
"make package". You'd need to manually run just "make" first to ensure the
packaged targets are built. You may want/need other options too when using
some CMake generators (e.g. -C for the build configuration with Xcode or
Visual Studio most likely).

make
cpack -G RPM



-- 
Craig Scott
Melbourne, Australia
https://crascit.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

[CMake] Exception handling warning on windows

[Aaron Boxer]

Hello,

I am getting the following warning when building my project on Visual
Studio 14:

warning C4530: C++ exception handler used, but unwind semantics are not
enabled. Specify /EHsc

Is there a cmake option to enable unwind semantics on windows ?

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] Exception handling warning on windows

[Aaron Boxer]

Never mind, figured it out :)

IF(MSVC)
SET(CMAKE_CXX_FLAGS "/EHsc")
ENDIF(MSVC)

On Sun, Jul 23, 2017 at 8:35 PM, Aaron Boxer  wrote:

> Hello,
>
> I am getting the following warning when building my project on Visual
> Studio 14:
>
> warning C4530: C++ exception handler used, but unwind semantics are not
> enabled. Specify /EHsc
>
> Is there a cmake option to enable unwind semantics on windows ?
>
> 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] Append to property COMPILE_DEFINITIONS

[Florian Lindner]

Am 22.07.2017 um 15:36 schrieb Craig Scott:
> 
> On Tue, Jul 18, 2017 at 8:50 PM, Florian Lindner  > wrote:
> 
> #Works, but I would prefer to have it just once for all targets and at 
> the top of the file
> set_property(TARGET testprecice APPEND
>   PROPERTY COMPILE_DEFINITIONS "FOO")
> 
> > BTW, you don't include the -D when adding to COMPILE_DEFINITIONS, just 
> put FOO, not -DFOO. Have a read of the docs, they may give you other clues 
> for this property (e.g. using the ..._CONFIG variant of it).
> 
> Yeah, I found out that I don't have to add -D. The docs say that 
> generator expressions are preferable to using _CONFIG
> variant.
> 
> 
> So just to be crystal clear, this is what I would have expected to work if 
> you wanted the symbol FOO to be defined for
> Debug builds for all targets in the current directory and below:
> 
> set_property(DIRECTORY APPEND PROPERTY COMPILE_DEFINITIONS 
> $<$:FOO>)

Put that in my CMakeLists.txt. Works, but only when I build in the same 
directory where the CMakeLists.txt file is
located, i.e. in source builds. That way:

set_property(DIRECTORY ${CMAKE_SOURCE_DIR} APPEND PROPERTY COMPILE_DEFINITIONS  
$<$:FOO>)

it works also out of tree.

Still, I don't undertand what is wrong with:

set_property(GLOBAL APPEND PROPERTY COMPILE_DEFINITIONS $<$:-FOO>)

?

Best,
Florian


> 
> Note that this directory property is NOT used to initialise the corresponding 
> target property. Rather, BOTH are combined
> to give the final set of command line compile definitions. It does not matter 
> whether this directory property is set
> before or after you call add_executable() within the same CMakeLists.txt file 
> (or more accurately, within the same
> directory scope).
> 
> 
> 
> >
> >
> > On Tue, Jul 18, 2017 at 1:21 PM, Florian Lindner    >> wrote:
> >
> > Am 18.07.2017 um 10:59 schrieb Craig Scott:
> > > You appear to be setting a GLOBAL property where you probably 
> meant DIRECTORY. You could also consider setting the
> > > target property instead rather than applying it to all targets 
> (unless that's what you want).
> >
> > I tried to set the property on all targets, therefore I thought 
> GLOBAL is the right thing.
> >
> > However,
> >
> > set_property(DIRECTORY "${CMAKE_SOURCE_DIR}/src" APPEND
> >   PROPERTY COMPILE_DEFINITIONS "-DFOO")
> >
> > hasn't had any effect either.
> >
> > set_property(TARGET testprecice APPEND
> >   PROPERTY COMPILE_DEFINITIONS "FOO")
> >
> > works. But setting it on all targets is exactly what I want. How 
> can I do that?
> >
> > Best,
> > Florian
> >
> > >
> > >
> > > On Tue, Jul 18, 2017 at 12:56 PM, Florian Lindner 
> mailto:mailingli...@xgm.de>  >
> >  
>  > >
> > > Hello,
> > >
> > > I want to add compile definitions. Since I want to use 
> generator expressions, I can't use add_definitions, but
> > have to
> > > use the COMPILE_DEFINITIONS property, but neither:
> > >
> > > set_property(GLOBAL APPEND
> > >   PROPERTY COMPILE_DEFINITIONS "-DFOO")
> > >
> > > for testing
> > >
> > > or
> > >
> > > set_property(GLOBAL APPEND
> > >   PROPERTY COMPILE_DEFINITIONS $<$:-DDebug>)
> > >
> > > which should be final result, produces any -DFOO compiler 
> switches.
> > >
> > > I also tried placing it before and after the add_executable 
> call.
> > >
> > > What is wrong with that call?
> > >
> > > Thanks,
> > > Florian
> 
>  
> -- 
> Craig Scott
> Melbourne, Australia
> https://crascit.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] Boost is planning to switch from bjam to CMake!

[Bo Zhou]

Good news !

Hopefully the bcp would also work with CMake so only requires component
would be installed.
-- 

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