Re: [Mingw-users] Good GUI debugger for MinGW?

[ralph e. <ral...@gm...>]

If you had read the message i pointed out that the patchset for building 
the sources are not done yet (specifically the ones reguarding building 
the itcl/itk 3.3 sources with mingw64) i can provide the insight/gdb 
sources if you want a look, or simply get them from the msys2 project. 
as for the version, its based on the msys2 version and was intended
to be uploaded to Alex when i got work done on the old itcl/itk sources.

As for my project if you refer to my compiler suite, a good deal of the 
sources involved should be there but frankly i havent had a look in 
those sections for years mostly if something is missing its because i 
had to use blatant hacks back then that could not be transfered to a 
patch to build it at that time. Most of it is reduntdant anyway as i 
shifted to using Msys2 now and it will be removed shortly.

If you want the changes involving codeblocks or packages i do have ready 
made patches for ill be happy to upload them just ask.

Thanks.

Den 06-04-2015 kl. 08:07 skrev Keith Marshall:
> On 04/04/15 22:41, ralph engels wrote:
>> I had success in building the insight debugger for both 32 and 64 bit
>> mingw,
> Hmm.  Which version?  Development seems to have stagnated with r6.8-1;
> according to https://www.sourceware.org/insight/index.php this is almost
> six years old.  Notwithstanding ...
>
>> so far it seems to work fine, you are welcome to try it but a
>> patchset others can use to build it is probably a bit off,
> That's rather unfortunate; (see below).
>
>> you can find it here ->
>> https://sourceforge.net/projects/cbadvanced/files/Tools/
> I see insight32.7z and insight64.7z, both of which appear to be binary
> release archives.  I don't see corresponding source archives, from which
> I may replicate your builds.  Where are they?  By failing to provide
> them, you are infringing the GPL, (unless you can immediately honour
> this request to provide them).  IANAL, but I suspect that this may be
> grounds for the FSF to ask either you, or SourceForge if you fail to
> address the issue, to take your archives, (and maybe even your entire
> project), off line.
>