I am looking for a complete instruction on how to setup Pony and make VS2017 or VSCode recognize its syntax, compile and debug program.
So far I've found a plugin for VS2015 (https://github.com/ponylang/VS-pony); however I cannot build the project (project is of course being converted to VS2017 format by VS2017 itself). I've also found some syntax colorizer for VSCode; however I have no clue how to configure building pipe, not mentioning the debugging environment.
Ps. On YouTube there is a lecture on Pony and guys there seem to use VSCode (https://www.youtube.com/watch?v=Vq1vRfv-A6g).
How did they do that? Does any one know?
Currently the plugin only supports syntax highlighting. I haven’t used it myself, but if you go to the Pony mailing list you might be able to find someone who has more information. I believe Sylvan is using Sublime Text in the video you linked to.
Related
I recently found out that VS Code has a beautiful Hex Editor extension made by Microsoft, but the problem is that it doesn't support adding tags / markers to HEX, which is a pretty common feature for such tools, and my workflow relies on using it. I haven't really found any info on this in the docs, but maybe I am just not that good at searching.
So my question is: is there a way to either make my own "fork" of the Microsoft extension or make a separate extension that adds the aforementioned feature to the editor provided by it?
Here is the Github repository for the extension. You can fork it like any open source project.
To edit the extension, you will need to install Node.js and npm on your computer, then run npm i and npm run watch from the root of the project.
Once you are done, you can do vsce package to package the extension and use it with VSCode.
Note that this extension is open source, meaning you can open a pull-request if you think other people might benefit from them.
I'm interested in Visual Studio Code, the new editor Microsoft released a year and a half ago. If I can get the hang of it, I think I'll switch to it on my Ubuntu. So I've done a "Hello, World!" program trying to find how to configure and use VSC's features.
I've seen on VSC's site and on some videos how to configure a folder so that you could go to definitions and find references, but it nonetheless doesn't seem to work for me. I don't know if I've done something wrong or if it's a bug on VSC's part.
Here is what my folder looks like. I've basically set up the tasks.json, launcher.json and c_cpp_properties.json files with default setup (compiling and debugging work just fine), but as you can see in the screenshot below, no indexing seems to be taking place since no symbol is found in main.cpp (even if I add new functions). Also, trying to find references of the i variable leads to No results, and asking to find i's definition doesn't do anything.
I've already tried :
Reinstalling VSC
Removing plugins
Adding the ${workspaceRoot} folder in the c_cpp_properties.json's include for Linux
Here's the screenshot. Notice my installed extensions on the left.
Nothing I've seen has helped me understand what the problem is. Have I done something wrong? I'm on Ubuntu 16.04.
Several binaries of the Microsoft C/C++ vscode extension for Linux are 64-bit. Therefore, if you're on 32-bit Linux, some of the cpptools functionality won't work. You can check the issue on GitHub.
I work also with Microsofts plugin C/C++ in a quite big C project. The C symbol references works good. Maybe you can try to add your projects root directory to "includePath" in c_cpp_properties.json.
But I am pretty sure, that local variables of functions are not parsed.
Maybe does the C++ intellisense plugin conflict with the Microsoft C++ plugin. can you disable the plugin provided by Austin
? The Clang plugin is also not necessary. The Microsoft plugin has Clang support and code completion integrated.
When I asked my question, I was on an Ubuntu VM. Yesterday, I installed an Ubuntu partition on my HDD, and vscode worked perfectly, with peek definition, find references etc.
After a few hours, I ended up in the same situation as when I made my post. But then I just closed and reopened VSCode, and it worked again. Definitely a VSCode bug.
EDIT : Seems to be the same issue as this one.
I´m trying to build paraview from source, therefore using:
Windows 7
Visual Studio 2010
Qt 4.8.7
Python 2.7.8
msmpi 7
paraview source, version 5.1.0
In CMake I can choose different options to specify what functionality to include into the build process. I tried different combinations, like setting BUILD_EXAMPLES or PARAVIEW_USE_MPI, respectively. Now I have got following questions:
When I set BUILD_SHARED_LIBS and PARAVIEW_ENABLE_PYTHON as well (besides others), configuring and generating the project with CMake is successful, but compiling in VS fails; it keeps freezing right after starting the compilation. Did anybody experience the same problem and how did you solve it? (By the way, if I unset BUILD_SHARED_LIBS it works, but I don´t want a static build of Paraview).
By using the combination BUILD_EXAMPLES, BUILD_TESTING, PARAVIEW_BUILD_QT_GUI, PARAVIEW_ENABLE_CATALYST, PARAVIEW_ENABLE_PYTHON and PARAVIEW_USE_MPI the same problem as described in 1.) occurs, but that is more or less what I need to use Catalyst to perform in-situ analysis of my FEM simulation. (Incidentally, if I unset BUILD_TESTING in the above combination it works, but I need CTest to test the Catalyst examples as described here. Does anybody now how to fix that problem?
As shown at GitHub, some examples have been updated to work properly in Paraview 4.4. Is my version of Paraview (5.1.0) unsuitable for the Catalyst examples? Is that the reason why VS is always hanging up for particular variable settings in CMake and which version of Paraview is most suitable to get the Catalyst examples going?
I'd appreciate any help!
That's odd! There's no known reason for this. Although I haven't used VS2010 explicitly, we do have dashboards testing with 2013 and I build with VS2015 with no issue.
I'd recommend using the Ninja as the builder rather than the IDE, however. Just run cmake-gui.exe from appropriate VS studio command prompt and pick Ninja as the build generator. Then, to build, just run ninja in the build directory.
I'm new with XCode and still trying to understand objective-C. I'm using xcode 4.3.2, and I have to create an app that integrates with PJSIP.
I found this link. I am still confused about that link, because the article said that we must have installed the command line tool. But the command line tool is already installed in my XCode. How can i use it?
Do I need to create a view base application? how can I run the command line tool like the link says?
The command line tools allow you to compile "traditional UNIX programs" from source, generally using make. If you are using Xcode to create your projects then you don't even need them installed.
EDIT OK you have edited your question, stating the real issue you are facing; You don't know how to use the PJSIP package you have installed. The link you reference is about building PJSIP, not using it, so you can still forget about the command line and concentrate on how to configure your Xcode project to use PJSIP. This will require setting the header search paths and library search paths to find the header files and library file, in order to compile and link against it. Hopefully it's a static library as that will be easier to use; if it's a dynamic library or framework then you have your work cut-out as that's much harder to use.
In newer XCode (4.3 or above) you might have to install command line tools since it has been made optional. Open XCode and go to XCode->Preferences
Open the Downloads panel and click on "Components". If Command Line Tools are not installed already, you will get an option to install them from here.
Do so and you are set.
I done with it by myself. if you face the same problem, you can refer to this link, I already tried and run it. It works both on simulator and device. thanks.
We want to add command-line support to Netbeans, as in being able to run any program (using the full path of the current file as the argument) directly from the IDE. The same way you can do it already on Notepad++ with the Run tool.
Apparently there is a plugin called VCS Generic Command-Line Support that offers this functionality, but when we try to install it we get this error message:
Some plugins require Master Filesystem to be installed
The plugin Master Filesystem is
requested in version >= 1.1 but only
2.15.2 was found.
Any ideas?
EDIT
I Did some googling as you got me interested pretty much everything i found was in refernce to NetBeans 5.x or below... Im thinking maybe its not compatible with 6 - but thats just a guess.
Looks like a version incompatability with "Master Filesystem". Maybe they are checking the version improperly or perhaps they really mean it needs to be 1.x >= 1.1. Do you have the newest version of VCS Plugin?
As an aside if Im going to have to chek this out... ive been dying for external tool support like in my beloved Eclipse :-)