Re: Can't build GTK only using CMake on Windows7

[Robert Cragie <robert.cragie () gridmerge com>]

I installed the latest Git (x64 version) and cleaned up my path, removing
all GNU/Linux like paths on there. This now seems to build OK with one
error on building:

CustomBuild:
  Building Custom Rule
C:/Users/robcra01/Documents/WiresharkBitbucket/wireshark/docbook/CMakeLists.txt
  CMake does not need to re-run because
C:\Users\robcra01\Documents\WiresharkBitbucket\wsbuild\docbook\CMakeFiles\generate.stamp
is up-to-date.
  Generating ws.css
  Generating release-notes.html
  running a2x with args --format=xhtml
--destination-dir=/cygdrive/c/Users/robcra01/Documents/WiresharkBitbucket/wsbuild/docbook
--asciidoc-opts= --fop --stylesheet=ws.css release-notes.asciidoc
  Traceback (most recent call last):
    File "/lib/python2.7/site.py", line 563, in <module>
      main()
    File "/lib/python2.7/site.py", line 545, in main
      known_paths = addusersitepackages(known_paths)
    File "/lib/python2.7/site.py", line 278, in addusersitepackages
      user_site = getusersitepackages()
    File "/lib/python2.7/site.py", line 253, in getusersitepackages
      user_base = getuserbase() # this will also set USER_BASE
    File "/lib/python2.7/site.py", line 243, in getuserbase
      USER_BASE = get_config_var('userbase')
    File "/lib/python2.7/sysconfig.py", line 521, in get_config_var
      return get_config_vars().get(name)
    File "/lib/python2.7/sysconfig.py", line 420, in get_config_vars
      _init_posix(_CONFIG_VARS)
    File "/lib/python2.7/sysconfig.py", line 288, in _init_posix
      raise IOError(msg)
  IOError: invalid Python installation: unable to open
//lib/python2.7/config/Makefile (No such file or directory)
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5):
error MSB6006: "cmd.exe" exited with code 1.
[C:\Users\robcra01\Documents\WiresharkBitbucket\wsbuild\docbook\release_notes_html.vcxproj]
Done Building Project
"C:\Users\robcra01\Documents\WiresharkBitbucket\wsbuild\docbook\release_notes_html.vcxproj"
(default targets) -- FAILED.
Done Building Project
"C:\Users\robcra01\Documents\WiresharkBitbucket\wsbuild\docbook\release_notes_html.vcxproj.metaproj"
(default targets) -- FAILED.

There are also quite a few warnings. However, there is a exe in the
run/RelWithDebInfo folder which seems to work. What is annoying is that it
has now lost the Git information in the name, so it now just says Version
2.1.0-<Custom> (where <custom> is my custom name), whereas before it would
say something like Version 2.1.0-<Custom> (v2.1.0rc0-2571-g2066c85 from
master). This is critically important when we are doing incremental
releases. Can this be put back in?


Robert

On 30 March 2016 at 14:35, Graham Bloice <graham.bloice () trihedral com>
wrote:

> On 30 March 2016 at 14:01, Robert Cragie <robert.cragie () gridmerge com>
> wrote:
>
> > I have always had issues with trying to have both cygwin and git (or any
> > other pseudo-GNU/Linux environments) coexist on Windows. It is normally a
> > case of juggling paths until it just works. This is probably why (I can't
> > remember exactly why) I had to put the cygwin path ahead of the git path
> > for nmake, as then it "just works".
> The rules I have always used for Wireshark builds, and urged others to
> use, are; a) don't put Cygwin on your path and b) only put git\cmd on the
> path.  If you can do this then things should "just work".
>
> If you need Cygwin or other aspects of Git on the path for other work,
> then consider creating a VM of some flavour for running the Wireshark build
> so you can keep the Wireshark setup isolated.
>
>
> > It sounds like it needs cygwin for some things and non-cygwin for others,
> > where the same executable exists in both environments. I don't know how to
> > resolve this. In the meantime, please do not get rid of using nmake for the
> > forseeable future as it will totally break things for me unless a
> > satisfactory solution can be found.
>
> The plan is that nmake will be left in the 2.0 branch, but removed from
> master and 2.2.
>
> If anyone wishes to retain nmake builds then they can locally create a
> branch from the last master revision before the deletion of nmake and then
> keep that branch in sync with master, amending the nmake bits as required.
>
>
>
> --
> Graham Bloice
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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