Hi,
Is there a way to declare a target property to be transitive and accumulate
into a list? Similar to how COMPILE_DEFINITIONS works, but for custom
properties? I know about COMPATIBLE_INTERFACE_STRING etc, which create a
transitive property, but the values don't accumulate into a list.
As a
On Wed, Dec 16, 2015 at 2:29 PM, Layus wrote:
> Hi,
>
> I am looking for a way to share an archive of a partially compiled project
> to speedup compilation time and configuration hassle for the users.
>
> I have a project that works in two steps.
> First a source generator is built (based on clan
On Thu, Nov 19, 2015 at 11:04 PM, Tamás Kenéz wrote:
> > set(foobarSRCS foo.c bar.c)
> > set(foobarLIBS ${externalLibFound})
> >
> > which is what the FAQ entry seems to suggest. However, this variable is
> not visible to goo.c. Okay, so as an alternative, I can do this:
> >
> > set(foobarSRCS fo
On Tue, Nov 10, 2015 at 9:22 AM, Nils Gladitz wrote:
> On 11/09/2015 08:29 PM, Mark Stijnman wrote:
>
> I think there should be a change in the CMake/CPack behavior here,
> regardless of whether the WiX generator will be extended to support this
> use case. For generators that s
Hi Nils,
thanks for the reply.
On Mon, Nov 9, 2015 at 4:09 PM, Nils Gladitz wrote:
> CMake does not implement any diagnostics that would prevent you from doing
> so but installing distinct files (or even the same file multiple times) to
> the same destination path is ill defined irregardless of
I'm using CPack with WIX to create multi-component installers, and I'm
having issues with components (or WIX features) that share files. A common
use case would be two executables which require the same DLLs. To reproduce
the issue, you can use following minimal CMakeLists.txt with three text
files
On Tue, Nov 5, 2013 at 12:11 PM, Alexander Broekhuis
wrote:
> Hi all,
>
> I have a CMake project for which I want to generate a RPM and/or ZIP file.
> But instead of including all components/groups I want to control this.
>
> I do know I can create a CPack configuration file to create a package fo
On Mon, Oct 28, 2013 at 9:03 AM, Mark Stijnman wrote:
> Dear all,
>
> I need to add some options to my NSIS installer, and noticed in the
> NSIS.template.in there is a variable CPACK_NSIS_DEFINES that looked
> suitable. Even though it doesn't appear to be documented, I'v
On Tue, Oct 22, 2013 at 7:45 PM, Bill Hoffman wrote:
> Hi,
>
> I have thought about CMake doing something automatically here, however, it
> could get tricky pretty fast, and it is pretty easy to fix in the CMake file
> of the project.
You'd have to detect whether the main function will be in the
Dear all,
I need to add some options to my NSIS installer, and noticed in the
NSIS.template.in there is a variable CPACK_NSIS_DEFINES that looked
suitable. Even though it doesn't appear to be documented, I've found
mentions online of users who have used this variable for similar purposes
(for exam
Hi all,
I'm trying to do some build-time configuration, for things like getting
revision information into header files, packaging scripts, etc. So I'm
using add_custom_command to run cmake scripts that use configure_file to
create new files. However, I'm running into an issue that I'm not sure is
11 matches
Mail list logo
