since few days, I'm not able to use FSharp Interactive interpreter(Alt + Enter), it's giving me this message:
*Failed to spawn FSI, please ensure it's in PATH*
also, if I run the script, it give me connect ENONNREFUSED 127.0.0.1.8397
I'm using:
- Ubuntu 16.04
- Visual Studio Code 1.28.2
- Ionide-sharp 3.28.0
anyone have an idea to fix this?
Thanks in advance
I think the main cause is the last update done. I have made a rollback and now everything is back to normal:
remove ionide-fsharp from VS code
click on https://github.com/ionide/ionide-vscode-fsharp/releases/download/3.27.0/Ionide-fsharp-3.27.0.vsix to download previous version of ionide (v 3.27.0)
unzip the file. once the file is unziped, you will have 2 text files and a folder named extension. Rename that folder ionide.ionide-fsharp-3.27.0
on your terminal, type:
cd ~/.vscode
cd extensions/
mv /home/####/Downloads/Ionide-fsharp-3.27.0.vsix_FILES/ionide.ionide-fsharp-3.27.0 . (don't forget the dot at the end to move the folder to the new location )
it should add ionide.ionide-fsharp-3.27.0 into VS Code extensions
you need to turn off auto-update in VS Code (in VS Code, in the bottom left conner, click on Setting icon > click on Settings > in the field Search setting, type update and search, you should then search in the result for Extensions: Auto Update)
You can fix this just by installing .NET Core SDK from this link https://www.microsoft.com/net/learn/dotnet/hello-world-tutorial
Related
i was trying to make use of unreal engine 4 template for AR but i got this error. This step kinda connect android studio with unreal but i just don't work.
Ran into the same issue and fixed it by editing the SetupAndroid.bat file.
Example of adjusted code
Not sure why it doesnt set the location of the SDKManager after it fails the first one. But manually replacing the first location works.
if you encountered this issue when running "SetupAndroid.bat", the reason might be simple. If you check the "SetupAndroid.bat"(right click, edit. Or turn it into a txt), the default sdkmanager path might be different from the actual location.
You might need to search "sdkmanager" from the Android Studio SDK root folder manually(it suppose to display on the cmd interface), find the actual directory and correct the "SetupAndroid.bat", then try it again.
the same here, i tried to search "sdkmanager" at both of my Drive and couldn't find any.
couldn't find any cmdline-tools drive as well.
Try next:
Go to your AppData\Local\Android\Sdk folder
Search for sdkmanager.bat
Navigate to its location and copy it
Open SetupAndroid.bat with Notepad (or other editor of your choice)
Find the line(s) which contains sdkmanager.bat
Paste the copied location (for example \cmdline-tools\latest\bin\sdkmanager.bat)
Save, exit, and run the edited file
This worked for me.
I spent 2 hours to figure out what's wrong with it.
So, provided earlier solutions should fix it:
Simply just replace incorrect path to correct one or, just DELETE most outer IF block and first line where %SDKMANAGER% var first set to invalid (I suppose, outdated path) value.
This is a part of the source code of SetupAndroid.bat from Epic Games. I've checked version 4.27 and 5.1. These lines are kind of identical in both versions (however version 5.1 still has the same exact error, but it works due to changing the order of which path is tried first):
set SDKMANAGER=%STUDIO_SDK_PATH%\tools\bin\sdkmanager.bat
IF EXIST "%SDKMANAGER%" (
echo Using sdkmanager: %SDKMANAGER%
) ELSE (
set SDKMANAGER=%STUDIO_SDK_PATH%\cmdline-tools\latest\bin\sdkmanager.bat
IF EXIST "%SDKMANAGER%" (
echo Using sdkmanager: %SDKMANAGER%
) ELSE (
echo Unable to locate sdkmanager.bat. Did you run Android Studio and install cmdline-tools after installing?
pause
exit /b 1
)
)
And this specific part does not work! I don't know why those who developed that did not check it or they simply don't know how batch file variables work.
The thing here is that on recent Android SDK installations there's no folder tools at the path %STUDIO_SDK_PATH%. So the first condition check fails and then they try to overwrite variable value to correct one with path %STUDIO_SDK_PATH%\cmdline-tools\latest\bin. But this overwrite DOES NOT WORK. You can't just do that in a batch file (which is kind of stupid, but it is). More on that issue with batch vars here: How to overwrite an existing variable using another variable in batch files?
"Good" job! Epic Games
i am trying to install opencv on my Mac IOS and there is this step of Adding an SDK path to CMAKE_OSX_SYSROOT, it will look something like this /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk.
and Add x86_64 to CMAKE_OSX_ARCHITECTURES, but don't know how to do it
I'm assuming you're already in the CMAKE application and you're following either one of these sets of directions.
Possible Instructions:
http://blogs.wcode.org/2014/10/howto-install-build-and-use-opencv-macosx-10-10/
http://outofbedlam.github.io/opencv/2015/07/15/Build-OpenCV-MacOSX/
Given which steps you isolated, I'm assuming you also know how to check and uncheck boxes in the CMAKE window. To enter text, you just right click in the empty space ("value" section) to the right of the variable of interest. When I came across this step, the thing which tripped me up was confirming the path/determining the right thing to enter in the window.* TLDR: it turned out to be almost the same thing (for me at least) "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk."
To find your path you need to navigate to that folder WITHIN THE TERMINAL! (Using Apple's Spotlight Search (command + space bar) or using finder windows just won't work. Because they don't see "inside" the Xcode application within the Applications folder. Assuming your home directory is't at the root, you need to keep entering cd .. until you get to the section that outputs the following:
>>>/ $ls -1
Applications
Library
Network
System
User Information
Users
Volumes
anaconda
...
Then you change directories ..., and see what's inside...
>>> $cd /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
>>> SDKs $ls
MacOSX10.11.sdk
Combine the path with whatever you find in your SDKs folder and you're done (see caveat below)!
Additional Caveat: Those instructions don't say explicitely, but at the end of the whole CMake process, you have to copy the ...opencv/SharedLibs/lib/cv2.so file to your directory of python packages: home/usr/.../lib/python2.7/dist-packages/cv2.so. Based on the advice found here, I installed the cv2.so file from the SharedLibs folder instead of the StaticLibs folder and it worked.
*I tried doing a spotlight serach for the "Developer" folder or "Xcode.app" and nothing was coming up! I thought that folder/path didn't exist and googling around for "CMAKE_OSX_SYSROOT" with "Python" or with "opencv" and a whole bunch of other things made me think the problem was every more of a jumbled mess and problematic.
I downloaded the latest version of Phonegap for IOS and ran "make" from Terminal. I ran make in the following subdir.
phonegap-2.3.0/lib/ios
I get these two lines back on stdout:
Xcode.app: '/Applications/Xcode.app'
Using Developer folder: '/Applications/Xcode.app/Contents/Developer'
and my shell prompt is back.
However, no PhoneGapLibInstaller.pkg file is created as it describes on the github site instructions.
https://github.com/infil00p/phonegap-iphone
The file wasn't in my ios directory but when I did a search on my entire hard drive there is nothing there. I wanted to check in case it put it in the Xcode.app package contents for some reason.
In case this make file did something other than in the guides and actually worked, I loaded Xcode but PhoneGap doesn't show up as a Framework/template to choose from when making a new package.
Any thoughts or suggestions?
Thanks,
Dano
That Github repo is from 3 years ago. You would probably be better off looking at the actual current documentation.
Adobe "value add" distribution page: http://phonegap.com
Docs: http://docs.phonegap.com
Latest Cordova information (the open source project PhoneGap is based on): http://cordova.apache.org/
Current Github: https://github.com/apache/cordova-ios
I am trying to compile/build OPenCV 2.3 with the help of CMake/Mingw. I got the source from there site, superpack as the call their package. I extracted it and placed it in c:\opencv2.3.
I point Cmake to c:\OPencv2.3\opencv for the source and c:\opencvbuild for the installation folder. Click configure, set a couple of options (I think that I set WITH_QT,and BUILD_EXAMPLES if I remember correctly) click on Advanced, and checked ENABLE_SOLUTION_FOLDERS.
Click Configure again, then Generate.
Go to c:\opencvbuild and from there (command prompt). I run mingw32-make, followed by mingw32-make install. No errors.
But, c:\opencvbuild does not show no .lib files, and not .sln files either....What am I doing wrong ?
Thank you very much,
Andres
PS: This is the CMakeCache file, that was generated:
http://dl.dropbox.com/u/35186952/CMakeCache.txt
Instead of copy-pasting, here: http://theroundedengineer.blogspot.com/2011/07/opencv-23-for-vs-2008-from-source.html
Hope that helps.
I am tried deploying .cod,.alx.jar files on blackberry simulator 8100;the application is not getting deployed on phone.I am using Blackberry plugin for Eclipse.
How can I solve this issue?
Please help
Update
Hi,
Thanks for your reply.
I am trying to run the application the way you suggested.
Do I need to setup new run configuration every time I run any project?
What should be default value for build configuration ? [Debug,Private,or Release]
Copying the .cod files into the simulator's directory (where all the other .cod files are) and restarting the simulator will work.
Probably though you want to automatically deploy from Eclipse. If this isn't working for you, there are a couple of things to check:
Check that the project has been activated for BlackBerry - from the right-click menu for the project, make sure that Activate For BlackBerry is checked.
If that's already checked (as it is by default when you create a new BB project), then sometimes explicitly building the project will do the trick: From the Project menu, choose Build Active BlackBerry Simulation
EDIT: In response to some comments below I thought of something else. The configuration you choose may have something to do with your problems (BlackBerry -> Build Configurations). The configuration in the JDE Plug-in doesn't affect the code generated, but it does affect which projects are activated for BlackBerry. If you switch configurations, your project may become un-activated.
Since it doesn't affect the code, I usually just pick one configuration and stick with it throughout debugging and release.
You might be missing 'jar' in your PATH. If so, the eclipse BB plugin silently fails and your application won't be pushed to your simulator plugin directory. To see this failure within eclipse, choose 'Project > Build Active BlackBerry Simulation'.
If you don't have jar in your path, then you will see:
I/O Error: Cannot run program "jar": CreateProcess error=2, The system cannot find the file specified rapc executed for the project
So, if your JDK is here:
C:\Sun\SDK\jdk\bin
Then append it to your system environment's PATH variable, then re-run 'Build Active BlackBerry Simulation' and you should see:
rapc executed for the project [YOUR PROJECT]
Here are a couple of ideas:
1) If you have any build errors then the application won't deploy to the Simulator. The Eclipse compiler (that underlines compile errors in red) is different to the "rapc" one that creates the binary for the Simulator. I have heard of situations where the Eclipse build seems to work, but the rapc compile fails - check the Console for the detailed rapc output (this might not look like a normal Eclipse build error).
2) In the Eclipse menu, open BlackBerry -> Configure BlackBerry Workspace.
Under BlackBerry JDE choose Code Signing and make sure the three RIM checkboxes are selected. I had compile errors when these weren't selected.
Under BlackBerry JDE choose Installed Components. Choose to use the Component Package 4.7.0 as I have heard of problems with the 4.5.0 Simulator.
You should delete all these extra answers you posted, or you might get downvotes - they should be comments instead of answers.
Check if your simulator is set up to clean the file system / configuration before launching the simulator. Simulators can be set up like this. If you deactivate it, the application should not disappear.
For future readers, there is another possibility for this issue. Check your workbench project directory (folder) for a ProjectName.err file. This may provide a clue as to why your build is silently failing and thus not deploying. In my case, it was an "Error!907", a new icon I added to my project was too big. There was absolutely no other indications in Eclipse 3.4.1 that there was a problem in my build.
Just ran through the same kind of problem : project compiled fine but didn't deploy on any device or on any simulator, even though the debugger said it was attached !
The problem came from a .zip file that was located in the ./src directory of the project, deleting or moving it somewhere else resolved this case.
I wish I hadn't spend 2+ hours on such a stupid problem :/
I know this is old, but you have to do the "generate ALX" option from right clicking the project menu as well or it won't deploy, at least it doesn't for me.
I ran into the same problem again and none of answers posted here worked for me.
I played around and finally made it work. The problem was that the output file name contained a hyphen ('-'). Changing this name in the Build section of BlackBerry app descriptor did the trick.
I mean, how stupid a developer must be to slip that kind of bug. No error reported and why reject the names with hyphens in the first place? Give me back my two hours RIM "developers"!
I had the same problem. The reason was using 'ΓΌ' character in the title.
I have been facing this problem today, but with a MIDlet project. It turned out to be that I forgot to specify the "Name of main MIDlet class" in the BlackBerry Application Descriptor (BlackBerry_App_Descriptor.xml). Once I specified it the application appeared on the simulator correctly.