Do we have some alternative plugin for python behave for jumping from feature file to step definition.I know Behave BDD Support is available in professional edition.
So do we have something to achieve jumping feature in pycharm community edition or any other tool.
Unfortunately, there is no alternative to PyCharm Professional edition. I tried XCode with different plugins, but they provide only syntax highlighting. Community edition also provide syntax highlighting without jumping feature.
There is Visual Studio Code for Win, Linux, and Mac, and nice extension, which allows to have code-navigation from feature file by CTRL+Clicking a step to its step definition. The extension is Cucumber (Gherkin) Full Support. I have just pushed a small behave project for checking the extension settings.
Install Visual Studio Code
Install the extension for Visual Studio Code
Clone the project and check the navigation from features/one.feature file to features/steps/definitions.py
use the .vscode/settings.json for your project
The extension also allows to have snippets as you type.
Related
I have a C code (pretty old one) that I tried to run in VS17 and am getting this error:
The build tools for Intel C++ Compiler 17.0 (Platform Toolset = 'Intel C++ Compiler 17.0') cannot be found. To build using the Intel C++ Compiler 17.0 build tools, please install Intel C++ Compiler 17.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
I am not including the code as it is old and big.
Can someone please suggest what the problem is?
It means your project configuration was done with an old version of Visual Studio.
I suggest you follow the VS suggestion: at the solution pane, right click on the project/solution and select 'retarget solution'. This will change your solution/project configuration to the current visual studio you use (2017).
As the project/solution files will be overwritten by the 'retarget' process, it worth copying the solution/project files (or even the entire solution
directory) before starting the 'retarget solution' process, so you can revert to the previous state for troubleshooting etc.
An example:
I'm want to build an old version of librdkafka, which was originally built with VS2010, and I want to use VS2017.
when looking at the solution explorer pane, you can see all projects has "(Visual Studio 2010)" title near them, at the left side of each project name.
Now I right click on the solution, and select 'Retarget solution':
At the dialog box, you get, click OK, and that's it.
I have developed a .bpl package with some components. I did this in C++ Builder XE7 and to install it I could just select "Install package" (or something similar) by right clicking on the .bpl project (in the project manager).
Now I have updated to C++ Builder Tokyo (10.2) and there is no alternative to install/uninstall the package from the project manager.
Has this function been moved/renamed? Do I really have to do it manually?
EDIT:
I solved it. For anyone having the same problem, It seems like the import from XE7 into 10.2 doesn't work that well. I opened it in 10.1 and there the install option became available. Then I opened that project in 10.2 and everything went fine now...
Make sure Win32 platform is selected when you want to install. Since IDE is a Win32 app, you can only install win32 components in it. The other platform targets just use components blindly. This causes other issues that Embarcadero has put on back-burner for way too long for example they have not done anything about RSP-10456 since I reported it when XE8 was in beta.
I would like to know if anyone knows how to flatten the package structures in Visual Studio Code.
I used to have this in my IntelliJ IDE, but with VS Code I can't find a similar option. I am looking for any solution which could resolve this. Either changing settings or extensions if available.
This is supported since the 1.41 release (November 2019) and enabled by default. VSCode calls this feature "compact folders", and it can be disabled like this:
"explorer.compactFolders": false
(gif from the release notes)
For java the only way i found is using this extension
(it won't change the default file explorer, but you can fold that one and use this one instead).
https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-dependency
or goto your VSCode->Extensions and search for "Java Dependency Viewer".
In VS Code v1.73.1 (latest as of this writing) folders are rendered in a compact form by default. To change this, go to File/Preferences/Settings/Features/Explorer and deselect Compact Folders.
I finally was able to successfully install the Windows SDK tools (v.7.1) on my Windows Vista system. I already had the GCC compiler installed and that is what I currently use to compile C code.
Where do I find the documentation for the WinSDK and how should I go about including it in GCC?
I couldn't find any explanations in the release notes or anything. However, if you can find something that explains it, feel free to give me a link.
This might sound weird to you, but you didn't need to download any separate Windows SDK to develop for Windows, because Visual Studio, and MingW/GCC, and others, already commonly include all that most people would need. (Some people would say, that Visual Studio and other tools, ship with their own version of the SDK, but I think that's merely confusing the issue further.)
You need Visual Studio first. And maybe, some day later, you might want to add the Windows SDK add on to it, but it is not intended to be used by itself, or in combination with GCC.
Basically, some of the SDK content duplicates stuff that is already included in Visual C++ and Visual Studio and some of it is additional tools like WinDbg.
Let me explain. The Windows SDK is indeed, useful for doing certain things in Windows that beginners are unlikely to need to do. For example, if you need to integrate with some specialized APIs, the Windows SDK contains a lot of documentation, examples, and a more complete set of header files that weren't included in Visual Studio because they're less frequently used APIs. The core API headers and documentation for Windows are already in Visual Studio, so technically, Visual Studio already contains the core SDK, and the so called SDK is an "auxiliary SDK", or a "low level SDK for purists, advanced users, and certain kinds of systems or native-level programming", but not needed, for most typical end-user applications development.
But if you want to learn Win32 native programming using C or C++, or you just want to write native Windows applications you PROBABLY don't need anything that comes in the SDK, and even then you need Visual Studio first, and the SDK second. Let me explain:
Many tools that let you write pure native Windows applications, provide higher level APIs, including Visual Studio, which gives you MFC or ATL. None of those tools need the SDK to work. The SDK, so called, is more of a "extra crap that we don't ship with visual studio because hardly anybody needs it", which Microsoft abbreviated to SDK. I know. Weird.
You don't need the SDK at all if you intend to use GCC. If you want to write an application for Windows in bare C or bare C++, you can just install mingw if you insist on using gcc and working from the command line.
The normal way to write native applications is to use the free Microsoft Visual C++ Express edition, and you can use it to write either C or C++ apps, and it includes the header files and libraries you need to write almost any native windows application feature you need, without any need for the SDK. Visual Studio is a nice modern IDE, and lots of convenient cool features like code completion and so on. The SDK you downloaded doesn't contain any of that.
Anything you do need to know about the raw Win32 APIs you can learn using the Web format of the MSDN documentation, or the help in Visual Studio. The basic Windows APIs like WinCreateWindow, are documented already in the Visual Studio help and MSDN help, and you don't need the SDK docs for most of the core windows APIs.
If you're just getting started, can I suggest you should just go get the free (but not open source) Visual Studio 2010 Express. That's the recommended way to get started, not the SDK.
I'm quite sure that the Windows 7 SDK that you downloaded is not intended for use with GCC anyways, and if you need a version of windows header files that work with a Gnu C/C++ compiler, any basic Win32 APIs like GDI and the basic Windowing API stuff is already bundled in mingw version of gcc.
You might also want to know about the DDK, which is like the SDK but which is oriented towards Device Driver and native NT-mode development.
I'm trying to disassemble a C/C++ DLL, and have made some progress, but I would like to create my own C DLL with the same function the original exports, and compare disassemblies.
Visual Studio adds to much crap, and when I remove the crap and build my project, the expected DLL is missing.
I need a lightweight, preferably IDE, tool to edit and build very simple C libraries.
Take a look at Code::Blocks
I need a lightweight, preferably IDE, tool to edit and build very simple C libraries.
I have found that one of the best ways to do integrated C-only Win32 development is using the freely available Lcc Win32 Compiler which comes with a built-in IDE, including resource editor.
In fact, it is really very lightweight and can be run from a USB stick with some manual tweaking.
It's indeed a really small download of just 6 mb and you can even download an optional Win32 API help file which is really useful while doing development.
The compiler also comes with a C tutorial, as well as good user documentation detailing how to use the integrated Win32 resource editor "wedit", there's also an advanced manual about more complex development tasks.
Dev-C++ is a nice and fast IDE which works well with MingW.
But it's all been asked and answered before ...
MinGW adds its own crap. Install your VC express properly and save yourself a lifetime of trouble.
Btw, you don't need to use Visual Studio for its compiler or vice versa. The oddity of missing a build dll is probably because you are not looking at the right path.
If you are building C DLLs you really would benefit from its command line toolset and utilities, sdks, easy config etc. MS lock-in proprietary extensions are widely used (in context of you trying to emulate another dll), and last thing you need is chasing cross compiler issues..
GCC + any text editor such as VIM is a very light alternative.
For Windows Development, all you need is inside MinGW
Edit: If you are in dire need of an IDE you can also use the MinGW tools from Eclipse with the CDT plugin. Although it adds weight to the solution because of the installation of Eclipse, this is what I really use to build my small DLLs (JNI wrappers in my case).
You can setup your small and direct makefiles or let Eclipse do it automatically for you and concentrate only on the source files (*.h, *.c).
The best part of using this approach instead other IDE is that you do not need Eclipse to further build the DLL, since the underlying project files generated are standard ones directly usable by integrated dev inside MinGW (or any Unix distro) such as make, configure, automake, and so on.
I'll second the vote for Code::Blocks, it's what I use (despite having VS 2008 installed as well). It is very simple and lightweight but has basically all the features you'd expect out of an IDE. It comes with several predefined project templates for all kinds of C and C++ development, including templates for DLLs.
Download the version that includes MinGW and you get a complete lightweight IDE ready to start compiling. You can also easily configure it to use the Visual Studio compiler instead of gcc if you prefer.
try Open Watcom. A cross-platform product, well-supported by the community, lets you develop in DOS, Windows, OS/2 etc for a lot of platforms. Version 1.8 was released recently. Has a light-weight IDE indeed