While I want to run firebase cli in my folder to deploy and serve, shell automatically execute firebase.js file in the folder.
This causes Microsoft JScript compilation error.
This kind of error did not happen in a mac but this happens in windows machine.
I temporarily executed firebase cli by specifying package location
c:\Users\$USER\AppData\Roaming\npm\firebase deploy
Related
I have ported my project build from buildbot to teamcity and it now fails on a command line step where I call a shell script that:
1) launches the macdeployqt qt utility to codesign the built app and then
2) tries to notarize the app.
I always get a sigsegv during the launch of macdeployqt
Obviously launching the script manually on the same machine and folder works as expected.
The problem was on my side, a JetBrains support staff stated that command-line runner is just calling the script as it is and not modifying any environment. It turned out that the script was failing because there was a double / in a path.
I am new to elixir and I am trying to create a command line app for Windows. I would like to deploy the app as an exe file that can be run from command prompt. I would also like the end user to not be required to install erlang to run the app if possible.
I have looked everywhere on Google and found nothing that seemed to help. I have installed Rebar3 but I don't know if that is what I need or not.
EDIT: I am currently using escript to run the app but I still have to type "escript app_name [args]" and I want to just run it as "app_name [args]".
You can create a release with exrm. Include it in your app dependencies in your mix file and then you'll be able to do something like : MIX_ENV=prod mix do compile, release
It will generate a tarball that contains everything you need to run your app. Including a bat file to start it on windows. It might not be a exe as you requested in your question, but it's still easy to from windows CLI
you'll find more information in the Phoenix doc (most of it applies to elixir apps without phoenix): http://www.phoenixframework.org/docs/advanced-deployment
I'm trying to create an Automator workflow which:
gets files and folders of a directory
copies those files and folders to another directory (with overwrite)
run a shell command: cordova prepare
The issue i have is, I'm working in one folder and wanting to be able to run an application that does the above, rather than manually do it every time i need to refresh the Cordova app.
The first two of the above works fine, i see the files copy/overwrite as they should, but when it gets to the shell command it returns the error code "cordova - command not found (127)"
Is it because I have Cordova installed for my user only and it wont execute as root (or whatever OS X the Automator user is)? If so how would i get it to run as another user or install it globally?
I've tested a simple command such as "cd ~/Sites/ && open ./" which works fine without error. It's just the cordova not found thing which i have going on at the moment.
Thanks in advance.
When you call the cordova command, are you using the entire path to the Cordova app? Something like this:
/Applications/Cordova.app
I am trying to build a VS .sln that has multiple C++ .vcproj's in it. The solution file is generated using CMake and I've got this part working in Jenkins (with the CMake builder plugin). To build the solution file, I am using msbuild. I am able to build the solution using both Visual Studio and from the command line with the following command:
C:\Jenkins\workspace\SonioTest>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe" /t:Rebuild bin/SonIO.sln
This builds successfully (on the same machine that Jenkins resides).
However, I am trying to automate this portion of the build in Jenkins and the build ends up failing with a couple of C1083 errors ("Cannot open source file: '..\path\to\file.ext': No such file or directory). I have tried using both the Jenkins msbuild plugin and using the exact same command that works in the terminal as a "Execute Windows batch command" build step, with the same result.
When using the Windows batch command build step, I can see in the log that the command being executed:
C:\Jenkins\workspace\SonioTest>"C:\Windows\Microsoft.NET\Framework\v4.0.30319 msbuild.exe" /t:Rebuild bin/SonIO.sln
... is exactly the same as the one that works from the command line, including the working directory.
I am running Jenkins as a service and I have the service logon as my account (with administrator privileges). Anyone know what directory Jenkins will execute batch commands out of?
Any ideas why I'm seeing this difference of behavior between Jenkins and the command line?
This is as much a workaround as a solution, but I ended up using devenv instead of msbuild and it works fine.
I know that this hints strongly as it being an environmental issue, but since it's not a problem to have VS installed on the build server, I decided to save the time that would be spent in the msbuild rabbit hole.
The environment being used by the account that the Jenkins slave agent is not the same environment as you use when doing the same command line from a prompt. Compare the two environments, note the difference, then add them to the Jenkins job.
To get the environment of the slave while running, have it do a "set" from a Windows Command Prompt
Without knowing much about VS build, it looks mostly like an environment setup.
My first advice would be to make sure, in Jenkins, you change directory to the same directory you ran the good command from and try it then.
Also, might want to try running Jenkins as a standalone app first.
And as a service, maybe allow service to "interact with desktop".
I may be late to the party, but I still ran into this problem on a new Jenkins setup on Server 2016.
My solution was to use the MSBUILD straight from the VS2017 installation C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin. No more errors.
I've been trying to run a GAE Go project I developed on my Mac on my Windows machine with GoClipse after installing and configuring the appropriate SDKs and so forth. When attempting to run the project, I get this error:
Exception occurred executing command line. Cannot run program
"C:\GoogleAppEngine\dev_appserver.py" (in directory
"D:\Golang\workspace\Project\src\pkg"): CreateProcess
error=193, %1 is not a valid Win32 application
How can I fix that error in order to run my project?
While the below configuration works on the Mac as it has Python installed by default, Windows requires a different configuration.
On Mac the GoClipse External Tools Configuration would be:
Location: /GoogleAppEngine/dev_appserver.py
Working Directory: ${workspace_loc:/Project/src/pkg}
Arguments: .
The Windows configuration should look like:
Location: C:\Python27\Python.exe
Working Directory:
Arguments: C:\GoogleAppEngine\dev_appserver.py "${workspace_loc:/Project/src/pkg}"
Trying to run .py (Which IMO is a Python file?) wont work directly on windows. You will need to install Python and then pass the above filename to Python something like (I don't know Python so don't go by exact syntax, you might need to look around)
python "C:\GoogleAppEngine\dev_appserver.py
The reason it's working on Mac is because Python comes pre-installed on mac as cited here But on windows it doesn't. So you can install Python and add the Python's bin folder to path, and then run above script and it should run fine!