accufere.blogg.se - Visual studio code debug python with arguments

One approach might be to write the code using a VS project file, but for the build process read in the xml using python / SCons, then parse it to generate the build via SCons. To give an example if I'm planning on writing a VC++ Visual Studio project but want to make it cross platform. One of the main benefits of python is that it has a vast library of supporting code.

SCons is a python based build system, unlike CMake it doesn't generate make files in that it handles the build itself. With VS Python tools we can get all the good auto completion features and can debug / step code to our hearts content.

My personal favourite though is the latest Visual Studio 2015 with python tools. In the open source world pycharm is one of the favourites for debugging python code this offers a lot of similar features. I've found that python makes for a very good scripting language, you can also easily debug it, add break points, get auto completion features etc. Net and python, the reason being they're debuggable via Visual Studio. In the past I've dabbled in a large number of different languages.Ĭurrently my two favourites are. I've placed an example over on my GitHub account I should point out there does appear to be an upcoming feature called server mode that may allow for some form of API access in the future SCons / Cuppa

You can't step through the code / build script with a debugger (I could be wrong on this one, but I've not found one).

The CMake language while very cross platform lacks features (such as class's for example).

It has no fixed API for hooking into, forcing you to use the CMake language.

However personally I've never been that fond of CMake With an easier to use language and syntax.ĬMake has now taken over as one of the more popular build systems since it's also windows and cross platform compatible.

Then came along CMake, CMake is a meta language in that it generates Make files in a similar fashion to autoconf and automake but all rolled into one However, over time because of cross compatibility reasons, if you were new to this sort of thing, it could quite quickly become a rat's nest of code. Surrounding these two was autotools which included autoconf and automake to try and make writing these sorts of scripts a lot easier. Make would use Makefile scripts to handle the actual compilation based on the results from configure.

For a while now I've been looking for a decent build system with a language I can easily write and debug.ĭuring the very old days of Linux the main go to for a build system typically was make and configure.Ĭonfigure would check the system to see if a library was present and its location,