[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-dev
Subject: Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7
From: Robert Cragie <robert.cragie () gridmerge ! com>
Date: 2016-03-30 21:57:42
Message-ID: CADrU+dL23S2dUzKt1X7=BDVVot=BAhUVzCS+Sf2bAqFR98QG9w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <graham.bloice@trihedral.com>
wrote:
> returning this to -dev
>
> On 30 March 2016 at 17:00, Robert Cragie <robert.cragie@gridmerge.com>
> 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 probably
>> have to go back to a version where it all just works and restore the
>> environment I had before.
>>
>>
>>
>>
>>
> Unfortunately we don't seem to keep archives of the docs from previous
> versions, so the nmake instructions would have to be recovered from Git
> history.
>
> I don't have the time to do that personally, but if someone does want to
> submit a change to temporarily add nmake build instructions until the
> deprecation date, I suggest that the appropriate place is a README.nmake in
> the top-level of the sources.
>
> --
> 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
>
[Attachment #5 (text/html)]
<div dir="ltr">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).<div><br></div><div>I think I am in as good a place as I can get for now - \
thanks for the help.</div><div><br></div><div>Robert</div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On 30 March 2016 at 20:53, Graham \
Bloice <span dir="ltr"><<a href="mailto:graham.bloice@trihedral.com" \
target="_blank">graham.bloice@trihedral.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">returning this to -dev<span class=""><div \
class="gmail_extra"><br></div><div class="gmail_quote">On 30 March 2016 at 17:00, \
Robert Cragie <span dir="ltr"><<a href="mailto:robert.cragie@gridmerge.com" \
target="_blank">robert.cragie@gridmerge.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div \
dir="ltr">Also, can you put back in the build instructions for nmake back into the \
online docs somewhere even if it is deprecated?<div><br></div><div>This is causing me \
a lot of headaches at the moment and I will probably have to go back to a version \
where it all just works and restore the environment I had \
before.</div><span><div><br></div><font \
color="#888888"><div><br></div></font><div><br></div></span><div><br></div></div> \
</blockquote></div><div class="gmail_extra"><br></div></span><div \
class="gmail_extra">Unfortunately we don't seem to keep archives of the docs from \
previous versions, so the nmake instructions would have to be recovered from Git \
history.<br clear="all"><br>I don't have the time to do that personally, but if \
someone does want to submit a change to temporarily add nmake build instructions \
until the deprecation date, I suggest that the appropriate place is a README.nmake in \
the top-level of the sources.</div><span class="HOEnZb"><font color="#888888"><div \
class="gmail_extra"><br>-- <br></div><div><div dir="ltr"><div>Graham \
Bloice</div></div></div><div class="gmail_extra"> </div></font></span></div>
<br>___________________________________________________________________________<br>
Sent via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org">wireshark-dev@wireshark.org</a>><br>
Archives: <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-dev</a><br>
Unsubscribe: <a href="https://wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer" target="_blank">https://wireshark.org/mailman/options/wireshark-dev</a><br>
mailto:<a href="mailto:wireshark-dev-request@wireshark.org">wireshark-dev-request@wireshark.org</a>?subject=unsubscribe<br></blockquote></div><br></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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic