Wireshark · Wireshark-dev: Re: [Wireshark-dev] RPM generation

[Anders Broman <a.broman58@xxxxxxxxx>]

Den tis 10 apr. 2018 21:15Dario Lombardo <dario.lombardo.ml@xxxxxxxxx> skrev:

Update on building the RPM on centos:

- asciidoctor pkg is called rubygem-asciidoctor.noarch

I think we should add this name in Findasciidoctor.cmake

- ninja is called ninja-build both in pkg name (as in debian/ubuntu) and in executable (differs from debian/ubuntu)

- the build script calls directly ninja, then the build fails. I've fixed this by adding a symlink from ninja-build to ninja

Did you build with ninja rather than with "Unix makefiles"?

Except from the manual actions above, the rpm build succeeded. I can try to fix some of them, but there are some issues still pending I can't figure out myself:

Is the rpm build platform expected to be one? If yes, which one? If no, do we want to support all the flavors? It seems that different flavors require different package names (link in asciidoctor). I can be hard to be portable in this way.

I did not find an rpm with asciidoctor for suse12.2 so I downloaded the gem files as descriptions from the asciidoctor site. I have not figured out how to make cmake find it. Not sure if it's related to rpm- package failing.

On Tue, Apr 10, 2018 at 11:46 AM, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:

Hi,

What I did:

On SuSe 12.2 git clone Wireshark

Create a build dir

In the Build dir run:

cmake -G "Unix Makefiles" ../wireshark

 

run:

make rpm-build

 

Currently I have the following patch:

@ -58,7 +58,12 @@ BuildRequires:       perl

BuildRequires: flex

BuildRequires: bison

# HTML guides

+%if 0%{?suse_version}

+#BuildRequires:  asciidoctor.ruby2.1

+#BuildRequires:  rubygem(asciidoctor)

+%else

BuildRequires: asciidoctor

+%endif

 BuildRequires: glib2-devel >= @GLIB2_MIN_VERSION@

Requires:      glib2 >= @GLIB2_MIN_VERSION@

 

But the main problem is that it fails building the RPM, it seems to me that cmake is called with the wrong path at %cmake, but I have no idea why ☹

 

Reards

Anders

 

From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Dario Lombardo
Sent: den 10 april 2018 11:38
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: [Wireshark-dev] RPM generation

 

I've read in previous messages that some issues about rpm generation are still pending, and this is blocking autotools removal. Can those issues be listed here? I'd like to help to solve them, and maybe others can do the same as well.

I'd like to have detailed instructions on how to generate rpm as well, since I've never done it before.

Dario.

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

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