[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    Re: [Wireshark-dev] Changing names of excutable files using CMake?
From:       Graham Bloice <graham.bloice () trihedral ! com>
Date:       2016-01-14 15:43:59
Message-ID: CALcKHKqT1sqwm=4g-qTmFDG2g+acFP_sDAoD+Y2XmsLgogwiew () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 13 January 2016 at 23:06, Alex Lindberg <alindber@yahoo.com> wrote:

> I am using CMake to build a customized version of Wireshark that needs to
> be installed at the beside the default Wireshark libraries and run-time
> files.
>
> To do this with previous version of Wireshark (<2) I created a SED script
> to do global search and replace functions to change file names, etc. The
> result of this script, that after a build, custom named libraries,
> directories and executable files where created. This approach worked, but
> did not allow for easy migration to newer code bases.
>
> So now I am trying to do it the 'smart way' (if there is one) by migrating
> to CMake (using Jetbrains' Clion) for the build environment.  The default
> build works just fine (Based on Debian's testing version of WS).
>
> Any ideas on how to proceed?  I can imagine that my request will meet some
> resistance.
>
> As always, thank you for your help.
>
>
>
The executables and libraries are named in CMake by the add_executable()
and add_library() commands respectively, and can be modified after the fact
by subsequent calls to set_target_properties(target PROPERTY OUTPUT_NAME
newname).

It might be possible to add a collection of set_target_property() calls in
CMakeCustomLists.txt which can be used to add custom CMake modifications.
Currently a custom file is permitted at the top-level and in asn1, epan and
ui\gtk.

Dealing with directories is much harder, most of them are hard-coded in the
CMake scripts.

-- 
Graham Bloice

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 13 \
January 2016 at 23:06, Alex Lindberg <span dir="ltr">&lt;<a \
href="mailto:alindber@yahoo.com" target="_blank">alindber@yahoo.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div><div \
style="color:#000;background-color:#fff;font-family:Courier \
New,courier,monaco,monospace,sans-serif;font-size:13px"><div><div><div \
style="color:#000;background-color:#fff;font-family:Courier \
New,courier,monaco,monospace,sans-serif;font-size:13px"><div>I am using CMake to \
build a customized version of Wireshark that needs to be installed at the beside the \
default Wireshark libraries and run-time files.</div><div><br></div><div dir="ltr">To \
do this with previous version of Wireshark (&lt;2) I created a SED script to do \
global search and replace functions to change file names, etc. The result of this \
script, that after a build, custom named libraries, directories and executable files \
where created. This approach worked, but did not allow for easy migration to newer \
code bases.</div><div dir="ltr"><br></div><div dir="ltr">So now I am trying to do it \
the &#39;smart way&#39; (if there is one) by migrating to CMake (using Jetbrains&#39; \
Clion) for the build environment.   The default build works just fine (Based on \
Debian&#39;s testing version of WS).</div><div dir="ltr"><br></div><div dir="ltr">Any \
ideas on how to proceed?   I can imagine that my request will meet some \
resistance.</div><div dir="ltr"><br></div><div dir="ltr">As always, thank you for \
your help.</div><span class="HOEnZb"><font color="#888888"><div \
dir="ltr"><br></div><div \
dir="ltr"><br></div></font></span></div></div></div></div></div></blockquote><div><br></div><div>The \
executables and libraries are named in CMake by the add_executable() and \
add_library() commands respectively, and can be modified after the fact by subsequent \
calls to set_target_properties(target PROPERTY OUTPUT_NAME \
newname).</div><div><br></div><div>It might be possible to add a collection of \
set_target_property() calls in CMakeCustomLists.txt which can be used to add custom \
CMake modifications.   Currently a custom file is permitted at the top-level and in \
asn1, epan and ui\gtk.</div><div><br></div><div>Dealing with directories is much \
harder, most of them are hard-coded in the CMake \
scripts.</div></div><div><br></div>-- <br><div class="gmail_signature"><div \
dir="ltr"><div>Graham Bloice</div></div></div> </div></div>



___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe

[prev in list] [next in list] [prev in thread] [next in thread]