Difference between revisions of "Using Visual Studio"

From Inkscape Wiki
Jump to navigation Jump to search
(Added Using Visual Studio page)
Line 81: Line 81:
 
# Select Debug->Start Debugging With GDB.
 
# Select Debug->Start Debugging With GDB.
 
# If you get a "GDB command timeout" window, be patient.
 
# If you get a "GDB command timeout" window, be patient.
# Inkscape will stop the breakpoint. Happy debugging.
+
# Inkscape will stop at the breakpoint. Happy debugging.
  
 
= Trouble shooting =
 
= Trouble shooting =

Revision as of 11:55, 5 March 2015

Microsoft Visual Studio is a popular development tool used primarily with C, C++, and C#. Visual Studio (community edition) can be downloaded for free but it requires a plugin called VisualGDB. This plugin is not free, but a fully functional evaluation version is available.

This page will help you set up Visual Studio for coding, building, and stepping through code in Inkcape.

Installation

  1. Follow all steps of guide Compiling Inkscape on Windows.
  2. Make sure Inkcape compiles correctly using the console first.
  3. Install Visual Studio.
  4. Install VisualGDB.
  5. Set the Environment variables in the Windows System settings as described here: Compiling Inkscape on Windows. Do not use mingwenv.bat to set the environment variables.

Note: It is assumed the required packages are installed in the following directories:

  • c:\mingw
  • c:\devlibs
  • c:\src\inkscape\trunk

Create project in Visual Studio

  1. Open Visual Studio.
  2. Select File->New->Project->Installed->Templates->VisualGDB->MinGW/Cygwin Project Wizard.
  3. For the project location, do not use a path with spaces.

    New-project.png

  4. Give the project a name, and click OK.
  5. At the wizard, select Project Type->Import a project build with command-line tools.

    Import-project.png

  6. Click Next.
  7. Check the path to MinGW is correct.
  8. Click Next.
  9. Set the Inkscape source directory to:
    • c:\src\inkscape\trunk
  10. Select Import preserving directory structure.

    Import-project-settings.png

  11. Click Next.
  12. At Build Command, select Customize.
  13. Set Arguments to:
    • /c "c:\src\inkscape\trunk\btool.exe"
  14. Select OK.
  15. At Clean Command, select Customize.
  16. Set Arguments to:
    • /c "c:\src\inkscape\trunk\btool.exe" clean
  17. Select OK.
  18. At Debug Settings->Executable file to debug, browse to:
    • C:\src\inkscape\trunk\inkscape\inkscape.exe

      Build-settings.png

  19. Click Finish and wait for the project generation to finish.

Note: VisualGDB will not copy the source files to the Visual Studio project directory, so you can still use Version Control the usual way.

Enable debugging

In Explorer, open build.xml located in:

  • c:\src\inkscape\trunk

Then look for the "T A R G E T : C O M P I L E" section, go to the <flags> section, and change

 -O2

to

 -O0

Also add this flag:

 -g


Flags.png

Then search for this:

 strip="true" symfile="${build}/inkscape.dbg"

And change to this:

 strip="false" symfile="${build}/inkscape.dbg"


Strip.png

Note: these changes will make Inkscape very slow to compile.

Building Inkscape

  1. In Visual Studio, select Build->Clean Solution.
  2. Then select Build->Build Solution.
  3. Come back later. This will take a while.

Note: The compiler will seem to be stuck at this for a while, but that is normal:

 1>  --- compile / cc

Stepping through code

  1. In Visual Studio, go to Solution Explorer->Inkscape->Source Files->src->main.cpp, and set a breakpoint here:

    Breakpoint.png

  2. Select Debug->Start Debugging With GDB.
  3. If you get a "GDB command timeout" window, be patient.
  4. Inkscape will stop at the breakpoint. Happy debugging.

Trouble shooting

In case Visual Studio cannot break at a certain breakpoint (most likely no debugging symbols present), you can diagnose breakpoint problems using the VisualGDB diagnose tool:


Diagnose-breakpoint.png