>
> cause cpack does not "rebuild" the software again, it uses the compiled
> software and just starts the "install" into its _CPack_Packages
> subdirectories
>
Just running `cpack` does not. However, CMake does generate a "package"
make target that is tied into your dependencies, so if instead o
again, it uses the compiled software and just starts the
"install" into its _CPack_Packages subdirectories
Thank for your patience :-)
-Ursprüngliche Nachricht-
Von:Chuck Atkins
Gesendet: Fr 21.07.2017 21:32
Betreff: Re: [CMake] CPack Multicore Usage
An:
> > In calls to cpack only one core is used if Makefiles are used. Is there
> any option to enable multicore?
>
It depends on what your trying to achieve. Typically the bottleneck for
CPack is in the compression step of the resulting tar (or rpm, etc.). In
that case, CMake is limited by the liba
20.07.2017, 11:22, "Jörg Kreuzberger" :
> Hi
>
> My Project is compiling multicore without any problems using Unix makefiles
> or ninja.
>
> In calls to cpack only one core is used if Makefiles are used. Is there any
> option to enable multicore?
Yes, you should run make -jN, where N is a numb
Hi
My Project is compiling multicore without any problems using Unix makefiles or
ninja.
In calls to cpack only one core is used if Makefiles are used. Is there any
option to enable multicore?
If i use ninja in cpack builds, the cpack build is broken, cause there seems no
dependencies consider
