BTW, in general you may use VisualStudio debugger directly without a
solution, by manually starting the 'devenv' as:

      devenv /debugexe fossil.exe

This launches VisualStudio in Debug mode and allows you to 'Step Into' a
new instance of the exe (fossil.exe). By default it breaks in main().

To actually see the source-code in the debugger editor window, fossil.exe
has to be built in DEBUG mode.

      cd win
      buildmsvc DEBUG=1
      cd ..\msvcbld
      devenv /debugexe fossil.exe

Otherwise you have to really be fluent in assembler :)

Once in VS debugger, you can use all of the usual features: call-stack,
break-points, watches, etc.

Of course a solution would give you also source-referencing freedom, but if
you know the source well and not averse to step-debbuging, this gives you
ability to debug projects in the absence of an all-embracing solition, say
CMake based projects etc, or indeed compex projects like fossil that
involves a lot of code-generation.

Hope this helps.


On Sat, Oct 29, 2016 at 12:00 PM, arnoldemu <
mem...@arnoldemu.freeserve.co.uk> wrote:

> Hi,
>
> I have attached a zip file which contains a solution and project file for
> fossil to be used with visual studio 2015 community edition.
>
> This uses nmake to build the project file in the windows directory and it
> will output to the msvcbld directory and generate a executable that you can
> debug in the debugger if you wish.
>
> The build, rebuild and clean menu options in visual studio can be used.
> You can also place a breakpoint in the debugger and launch the debugger and
> it will hit.
>
> Extract the contents of the zip file within the win directory.
>
> I did attempt to make a windows 64-bit build but the following things held
> me back:
> 1. the fossil.exe.manifest in win needs a x64 equivalent. I managed to
> change the makefile to use this but was unable to verify my changes were
> correct. (I put a new fossil.exe.manifest in a sub-directory, and changed
> x86 to x64 in the new file.)
>
> 2. the makefile attempted to link against the win32 version of zlib. I
> wasn't sure how to make it build zlib for x64 so I didn't proceed furthur.
> (without this it will not link correctly).
>
> I hope others may find this useful.
>
> Thanks
>
> Kevin
>
>
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to