I got nmake working again - it was the clashing link.exe, which IIRC was
mentioned in the old developer guide (which is why I wanted to see it
again).
I think I am in as good a place as I can get for now - thanks for the help.
Robert
On 30 March 2016 at 20:53, Graham Bloice
returning this to -dev
On 30 March 2016 at 17:00, Robert Cragie
wrote:
> Also, can you put back in the build instructions for nmake back into the
> online docs somewhere even if it is deprecated?
>
> This is causing me a lot of headaches at the moment and I will
returning this to -dev
On 30 March 2016 at 16:53, Robert Cragie
wrote:
> It seems to be picking up the Windows installation of Python (which is in
> the path). Removing this from the path will mess up a lot of things for me
> as most of the time I do not want to use
On 3/30/16 8:44 AM, Graham Bloice wrote:
>
> There seems to be something wrong with the python installation in Cygwin.
> To build the docbook stuff we use the Cygwin a2x utility that depends on
> the Cywin python. There's quite a bit of juggling that goes on here to
> keep things straight. I'm
On 30 March 2016 at 16:12, Robert Cragie
wrote:
> 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
>
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
On 30 March 2016 at 14:01, Robert Cragie
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 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
On 30 March 2016 at 12:05, Robert Cragie
wrote:
> I do have cygwin on the path. I needed this for nmake build and it hasn't
> caused problems before. I have removed cygwin from the path and now I get
> errors with CMake:
>
>
The errors now are because you have the
I do have cygwin on the path. I needed this for nmake build and it hasn't
caused problems before. I have removed cygwin from the path and now I get
errors with CMake:
-- Generating build using CMake 3.5.1
-- Building for win64 using Visual Studio 12 2013 Win64
Working in
Comments in-line:
On 30 March 2016 at 10:08, Robert Cragie
wrote:
> I updated cygwin and included asciidoc and the CMake output now doesn't
> show asciidoc as missing optional. Here is the output from CMake (I removed
> :
>
> cmake -G "Visual Studio 12 Win64"
I updated cygwin and included asciidoc and the CMake output now doesn't
show asciidoc as missing optional. Here is the output from CMake (I removed
:
cmake -G "Visual Studio 12 Win64" ..\wireshark
-- The C compiler identification is MSVC 18.0.40629.0
-- The CXX compiler identification is MSVC
On 29 March 2016 at 15:04, Robert Cragie
wrote:
> I did the following:
>
> 1) Merged my fork with the latest upstream
> 2) Downloaded and installed Qt
>
> I tried to rebuild using CMake but it still failed. Note the same code
> builds fine using nmake and GTK only.
I did the following:
1) Merged my fork with the latest upstream
2) Downloaded and installed Qt
I tried to rebuild using CMake but it still failed. Note the same code
builds fine using nmake and GTK only. Here are the lines with FAILED and
error in from the output of the build:
91>Done
It's a fork from 3771a79 with some custom changes. We tend to use the GTK
version as it used to be more stable than the Qt version. I am not sure if
that still is the case and I know GTK will be deprecated - is it at the
point now where Qt version is better maintained, i.e. from the point of
view
Hello,
On Fri, Mar 25, 2016 at 02:46:35AM +, Robert Cragie wrote:
> Following the announcement about deprecating nmake (which I have been using
> successfully for years), I thought I would try using CMake. I deliberately
> only want to build the GTK version so I use the following options with
On 25 March 2016 at 02:46, Robert Cragie
wrote:
> Following the announcement about deprecating nmake (which I have been
> using successfully for years), I thought I would try using CMake. I
> deliberately only want to build the GTK version so I use the following
>
Following the announcement about deprecating nmake (which I have been using
successfully for years), I thought I would try using CMake. I deliberately
only want to build the GTK version so I use the following options with
CMake:
cmake -DENABLE_CHM_GUIDES=on -DBUILD_wireshark=off -G "Visual Studio
18 matches
Mail list logo