On Thu, Jun 28, 2012 at 9:05 PM, Eric Noulard <eric.noul...@gmail.com>wrote:
> 2012/6/28 hce <jupiter....@gmail.com>:
> >
> > m.hergarden wrote
> >>
> >> The unspecified may come from an Install statement that does not have a
> >> component specified.
> >>
> >> Micha
> >>
> >
> > I actually double checked, there are only two install statements which
> all
> > have component specified. Could it be the bug?
>
> Yes it could but did you start over from a pristine build tree?
>
> Could you try:
> $ find . -name "cmake_install.cmake" -exec grep -Hn "Unspecified" {}
> \;vi ./Source/kwsys/cmake_install.cmake
>
> and see if any "cmake_install.cmake" file is containing teh handling
> of "Unspecified" ?
>
> Whatever the result you can always specify the CPACK_COMPONENTS_ALL
> yourself in the CMakeListst.txt (before including CPack) and not let
> CPack set it on his own:
>
> So you can:
> set(CPACK_COMPONENTS_ALL yourcomp1 yourcomp2)
> ...
> include(CPack)
>
>
Thanks Eric, that did the trick.
> and CPack (when used in component mode) will only install the
> specified components
>
>
> --
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
>
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
