cocos2d "There isn't any available platforms" error - cygwin

I just installed cocos2d-js on Windows/cygwin and am trying to run things (moonwarrior sample and a new project) with
cocos run -p web
Unfortunately I get the error "There isn't any available platforms". Aside from the incorrect grammar, I can't find out what's gone wrong. I did download/install for "web only", but I'm trying to run web and it's not working.

AFAIK, The cygwin environment is not supported by cocos2d console.
The error message "There isn't any available platforms" just complaint about it.
You might need to change to noncygwin environment.
You could simply open CMD and type in cocos run -p web.

Related

Julia integration with VS Code in Linux

I am using Pop_os! system (ubuntu based system) and just installed VS Code. I would like to use Julia with it and installed Julia Extension in the VS Code Extension Marketplace. In the extension settings, I typed in the Julia executable path as where I installed it (in my case is: /opt/julia-1.5.3-linux-x86_64/julia-1.5.3/bin/julia.exe). It is able to run code and print hello world in the output window. However, when I try to click "julia: Execute file" button and run it in Julia REPL, it shows me error message:
Command failed: "/opt/julia-1.5.3-linux-x86_64/julia-1.5.3/bin/" --startup-file=no --history-file=no -e "using Pkg; println(dirname(Pkg.Types.Context().env.project_file))"
/bin/sh: 1: /opt/julia-1.5.3-linux-x86_64/julia-1.5.3/bin/: ***Permission denied***
`"/opt/julia-1.5.3-linux-x86_64/julia-1.5.3/bin/" --startup-file=no --history-file=no -e "using Pkg; println(dirname(Pkg.Types.Context().env.project_file))"` (exited with error code 126)
I noticed in the previous error message it says "permission denied", so I change the path to where the static link is located "/usr/local/bin/julia.exe", but in this case it shows me the same "permission denied" error message.
Does anyone know how to get around this issue?
Thanks!
The cause of the issue is when I installed vs code on linux, I accidentally synced the accounted settings I used in a windows laptop, and that seems to mess up the Julia extension (I used to use Julia extension in windows vs code). I tried uninstall and reinstall vs code, and make sure I don't sync my windows account settings, this time julia extension works for me right after installing it. I don't even need to define any paths.

electron-updater auto update on linux

i am desperately in need for help. I have been trying this for so long and i got no results at all.
So, my problem is. I am using the electron-updater package to auto update my electron app. It's working on windows but on linux is another story. I have been looking everywhere and i can't find anything about it.
I am using electron-builder integrated with quasar to package my application, and, i did read about it in the documentations, it's only supported by AppImage formats. Okay that's fair, but what should i even do with that? I am using a custom url-schema and it just doesnt work, it doesn't install it anywhere. It just opens my electron app and that's not the behavior i am expecting.
I have tried using AppImage Launcher but i am getting this silly error (which i dont know why it happens), doesn't provide any description about it and i think i will just give up the project for linux (already did for MacOS) too. I have setup the desktop file, set the executable name, indeed it compiles and it installs perfectly on a .deb package, but i just don't know what to do with this .appimage extension.
My linux configuration on electron-builder looks like this (it will be interpreted by quasar)
linux: {
target: "AppImage",
executableName: "portscanner",
desktop: {
Name: "Port Scanner",
"Generic Name": "Port Scanner",
StartupWMClass: "portscanner",
Terminal: false,
Type: "Application",
MimeType: "application/portscanner;x-scheme-handler/portscanner;",
Categories: "Networking"
},
category: "Networking"
}
I will gladly take any help on this. Thank you guys in advance.
Edit:
I took note of the error i got on AppImageLauncher and it's the following:
Error registering AppImage in the system via libappimage
And in the terminal i have this error:
ERROR: appimage_register_in_system : Malformed desktop entry: Unexpected token ENTRY_KEY at line 8
But i have no ENTRY_KEY in my desktop config :/
Edit2:
I fixed it by removing most of the things of the linux desktop file (except for mimetype) but now i am facing this issue in electron-builder which is the following: "APPIMAGE env is not defined, current application is not an AppImage"
I know i have to put the path to the appimage application but which path? The one generated in the dist folder? A path pointing to $HOME? (tried that and didn't work). None of them work btw. I dont know what to do anymore.

Error while running gnome-music using jhbuild

I'm using jhbuild to build and run gnome-music.
I'm having a successful build but when I run the command
jhbuild run gnome-music
I get the following error
One of the errors is
1.GstTag was imported without specifying a version first
The rest are in the link above.
I'm not sure how to proceed further,can someone help me out?(I'm using Ubuntu 17.04).
I'm following the steps given on:
https://github.com/GNOME/gnome-music
Gst just warns you against not mentioning a version number. Hence, that's not the error.
The error you are facing is regarding Tracker. As you are on Ubuntu distribution, you should know that Ubuntu disables Tracker by default. Hence jhbuild run gnome-music refuses to start. Tracker is a file-indexing service based on file's metadata.
However, Ubuntu is deciding to enable Tracker by default as many GNOME's core apps relies on it. Read here.
Enable Tracker and jhbuild will pick it up from the host system.

IntelliJ Haskforce plugin - run error

I installed the Community edition of IntelliJ and the HaskForce Haskell plugin, and I find that:
It does not do any of the context sensitive formatting or auto-completions shown on the demo page,
There is not any obvious simple run configuration for Haskell
and trying to use a default configuration gives the error:
"Error running Pgm: no JDK specified"
Doing a build is successful, and creates a Pgm.exe in the ./dist/build/Pgm directory.
Is there some additional setup or configuration needed?
In your project settings -> Haskell Tools, you haven't specified paths to all executables, in particular ghc-mod and ghc-modi.

unable to symbolicate crash log from a MonoTouch program

I have a MonoTouch app that I built in debug and uploaded to the device. I ran the app in the debugger and the app died without the debugger catching anything. I have a .crash log for it. I ran:
symbolicatecrash myapp.crash myapp.dSYM
It got symbol information for Apple stuff like CFRunLoopRunInMode and UIApplication, but not for anything in my program.
Is there a different way I need to symbolicate MonoTouch crash logs?
We had this same problem and we created a work around...
When we ran symbolicatecrash with the -v parameter (verbose) we saw it was complaining about not having a binary file inside the dSYM package. So we manually copied the binary file from within the app package into the dSYM package and that worked. Something like [MyProject].app/[MyProject] to [MyProject].app.dSYM/[MyProject].
We then created this as a Custom Command to run After Build:
cp ${TargetDir}/${ProjectName}.app/[MyProject] ${TargetDir}/${ProjectName}.app.dSYM/${ProjectName}
Note the [MyProject] portion as the binary created in the app package is a different name than the project name for us for some reason.
Now all builds symbolicate fine from terminal and within Xcode organizer. I hope there's a less band-aid way, but we were in a time crunch and this worked.
I had this problem and posted a patched version of symbolicatecrash to github. Replace /usr/local/bin/symbolicatecrash with this and you should be back in business.
tholsens answer is correct but when using Xcode >=4.3 (which is installed as an application) you need to run xcode-select first:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
Otherwise you'll get strange errors like 'does not contain slice armv6', etc.

Resources