2010/8/23 Clinton Stimpson :
> On 08/22/2010 10:47 AM, Eric Noulard wrote:
>>
>> 2010/8/22 Eric Noulard:
>>
>>>
>>> 2010/8/21 Clinton Stimpson:
>>>
I wondered if one would typically use groups if their project contained
sub projects, and the sub projects had different conventions for
On Monday 23 Aug 2010 7:57:28 pm Clinton Stimpson wrote:
> On 08/22/2010 10:47 AM, Eric Noulard wrote:
> > 2010/8/22 Eric Noulard:
> >> 2010/8/21 Clinton Stimpson:
> >>> I wondered if one would typically use groups if their project contained
> >>> sub projects, and the sub projects had different co
On 08/22/2010 10:47 AM, Eric Noulard wrote:
2010/8/22 Eric Noulard:
2010/8/21 Clinton Stimpson:
I wondered if one would typically use groups if their project contained sub
projects, and the sub projects had different conventions for the component
names.
I do not usually wor
On Sunday 22 August 2010, Eric Noulard wrote:
...
> CPack is not aware **AT ALL** of subprojects :-(
>
> It's even worse, since CPack is not meant to be included more than once
> in the same tree.
> In fact you already know that because you are the reporter of this:
> http://public.kitware.com/Bug/
2010/8/22 Eric Noulard :
> 2010/8/21 Clinton Stimpson :
>>
>> I wondered if one would typically use groups if their project contained sub
>> projects, and the sub projects had different conventions for the component
>> names.
>
> I do not usually work with sub-project and I must admit I don't eve
2010/8/22 Eric Noulard :
> 2010/8/22 Rolf Eike Beer :
>> Am Saturday 21 August 2010 schrieb Eric Noulard:
>>
>>> They change the number and the contents of the generated packages:
>>> 3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
>>> means you want to get a single package whose co
2010/8/21 Clinton Stimpson :
>
> I wondered if one would typically use groups if their project contained sub
> projects, and the sub projects had different conventions for the component
> names.
I do not usually work with sub-project and I must admit I don't even know
how CPack behave for projec
2010/8/22 Rolf Eike Beer :
> Am Saturday 21 August 2010 schrieb Eric Noulard:
>
>> They change the number and the contents of the generated packages:
>> 3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
>> means you want to get a single package whose content
>> is the merge
Am Saturday 21 August 2010 schrieb Eric Noulard:
> They change the number and the contents of the generated packages:
> 3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
> means you want to get a single package whose content
> is the merge of all components GROUPS
>
>
On Aug 21, 2010, at 6:21 AM, Eric Noulard wrote:
> 2010/8/21 Eric Noulard :
> [...]
>> They change the number and the contents of the generated packages:
>>3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
>> means you want to get a single package whose content
>> is the mer
2010/8/21 Eric Noulard :
[...]
> They change the number and the contents of the generated packages:
> 3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
> means you want to get a single package whose content
> is the merge of all components GROUPS
>
> 3.b) CPACK_COMPONENTS_AL
Hi All,
I finally rebased my previous work on component support for Archive Generators
(i.e. STGZ TBZ2 TGZ TZZIP)
(see also ML discussions:
http://www.cmake.org/pipermail/cmake/2010-July/038575.html
http://www.cmake.org/pipermail/cmake/2010-August/038663.html
http://www.cmake.org/pi
12 matches
Mail list logo