Hi,
after reading some stuff about integration of KDE-stuff into cmake, I
want to know your oppinion about manpages. At least on unix-based
systems it's an essential function of a build-environment to allow
installation of the docs.
My suggestion is, to add a new property like man-source-dir o
2011/6/7 Werner Mahr :
> Hi,
>
> after reading some stuff about integration of KDE-stuff into cmake, I
> want to know your oppinion about manpages. At least on unix-based
> systems it's an essential function of a build-environment to allow
> installation of the docs.
>
> My suggestion is, to add a
Eric Noulard wrote:
>> My suggestion is, to add a new property like man-source-dir or
>> somehow like that, and all pages in that dir are installed to the
>> right place if they start with the name of the corresponding
>> executable.
> Have a look at the new (in 2.8.4) GnuInstallDirs.cmake modu
On 06/07/2011 03:47 PM, Werner Mahr wrote:
> Eric Noulard wrote:
>
>>> My suggestion is, to add a new property like man-source-dir or
>>> somehow like that, and all pages in that dir are installed to the
>>> right place if they start with the name of the corresponding
>>> executable.
>
>> Have a
On 06/07/2011 10:31 AM, Michael Wild wrote:
> install(FILES cmake.1
> DESTINATION ${CMAKE_INSTALL_FULL_MANDIR}/man1 COMPONENT doc)
Actually that should be CMAKE_INSTALL_MANDIR. The documentation of
GnuInstallDirs specifies that the variables without _FULL_ are meant
for passing to install comma
Michael Wild wrote:
>> Rename from . or .. to
>>
>> install to $mandir//[.gz] or
>> $mandir///[.gz]
> install(FILES cmake.1
> DESTINATION ${CMAKE_INSTALL_FULL_MANDIR}/man1 COMPONENT doc)
>
> If you want gzipping, either leave it to the package generation system
> (e.g. dh_installman on Debia
On 06/07/2011 05:59 PM, Werner Mahr wrote:
> Michael Wild wrote:
>
>>> Rename from . or .. to
>>>
>
>>> install to $mandir//[.gz] or
>>> $mandir///[.gz]
>
>> install(FILES cmake.1
>> DESTINATION ${CMAKE_INSTALL_FULL_MANDIR}/man1 COMPONENT doc)
>>
>> If you want gzipping, either leave it to th
Michael Wild wrote:
> foreach(m amule.1 amule.de.1 locale.7)
> get_filename_component(b ${m} NAME_WE)
> get_filename_component(e ${m} EXT)
> if(e MATCHES "(([a-zA-Z_-]+)\\.)?([0-9])")
> set(l "${CMAKE_MATCH_2}")
> set(s "${CMAKE_MATCH_3}")
> else()
> message(SEND_ERROR
>
On 06/07/2011 07:40 PM, Werner Mahr wrote:
> Michael Wild wrote:
>
>> foreach(m amule.1 amule.de.1 locale.7)
>> get_filename_component(b ${m} NAME_WE)
>> get_filename_component(e ${m} EXT)
>> if(e MATCHES "(([a-zA-Z_-]+)\\.)?([0-9])")
>> set(l "${CMAKE_MATCH_2}")
>> set(s "${CMAKE_M
2011/6/7 Michael Wild :
> On 06/07/2011 07:40 PM, Werner Mahr wrote:
>> Michael Wild wrote:
[...]
>> I don't think that writing
>> stuff like this in many different projects is a good idea, that's why I
>> proposed to include it native in cmake.
>>
>> ADD_EXECUTABLE(, )
>> SET_TARGET_PROPERTIES (
10 matches
Mail list logo
