The problem is that Wireshark is launched by a script settings paths and doing whatnot and finally starting Wireshark from some (hidden?!) subfolder.
I have been using DDD with other automake built projects and had no such problems there. That's why I believe that DDD's problem have something to do with how Wireshark is set up and launched.
> From: guy@xxxxxxxxxxxx
> Date: Wed, 26 Jan 2011 00:39:39 -0800
> To: wireshark-dev@xxxxxxxxxxxxx
> Subject: Re: [Wireshark-dev] Eclipse project for Wireshark
>
>
> On Jan 26, 2011, at 12:27 AM, Dietfrid Mali wrote:
>
> > I know what DDD is.
>
> I was just quoting the full section, which included the comment.
>
> The key point is that it's just a front-end to gdb, and if gdb can find source files that DDD can't, that's something wrong with DDD, *NOT* with Wireshark or the Wireshark build mechanism, and one's frustration should be directed at DDD's developers, not Wireshark's developers (or automake's developers, given that the standard Wireshark build mechanism is largely automake-based).
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|
