I am uploading ipa from post trigger of Xcode Server to HockeyApp. I used puck command
puck -force=true -submit=auto -api_token=$TOKEN -app_id=$ID "$XCS_ARCHIVE"
This command works fine on terminal but It shows error 'puck: command not found' when run in post script.
xcode server version : 5.2
If the Xcode server is a separate device, please ensure that the puck client is also installed there.
The "command not found" error indicates two things:
That you are not running it from a directory which includes the command
The computer's PATH environment variable does not include the path to that directory
Full path to puck: /usr/local/bin/puck
Related
I am a student who has gotten a part time job embedded system programming. I am given a program the company uses, and asked to understand it. This is a working program. Therefore, the project can be built and flashed on ESP32 by the developers with no problem. So, the code and CMake files should have no issues. However, I cannot build the program either with VSCode extension nor with idf.py. In fact, I cannot build esp-idf examples from the official website, either.
Note: I am new to StackOverflow as well as to ESP32, so sorry if I made any mistakes here. If this post is problematic in any way, please inform me.
The error message from the terminal is shown here
I was initially using VSCode on Windows 10 (Windows is not activated). At first, ESP extension was completely failing to start the building process because it could not locate the tools. I was getting "could not be located" errors for all the tools. Below is a list of what I did in this setting:
I had v5.0.0 for esp-idf downloaded from Espressif server. I deleted it and tried v4.3.3 and then I tried to download from Github server. I downloaded the requirements for idf.py scripting environment and completed the settings for it as described by the Espressif's documentation.
I manually set the environment variables for IDF_PATH and PATH for both the user and for the system.
After 2, the initial error was gone. Unfortunately, I had a new error which indicated that ".elf" file for the project output could not be found. I do not exactly recall the error but if it is integral to the problem's solution I can try to replicate this issue.
I tried to delete and reinstall VSCode. I tried running VSCode with admin authority.
I tried changing the IDF_TOOLS_PATH in the VSCode esp-idf extension configurations from ".espressif" to "esp\esp-idf".
At this point, I moved to try to build the project on Ubuntu 22.04.1 LTS:
In Ubuntu, I got the fatal error: esp_event.h: No such file or directory error.
It does not seem to be a common issue and I could not find much about it online.
I followed the Linux setup steps in the documentation. It said that only step 1 (Downloading the prerequisites) was necessary for the VSCode extension.
I decided to try the "master branch" from esp-idf configurations as well. After I downloaded the master branch, the error changed to the current version: 'fatal error: esp_wifi.h: No such file or directory'
I also tried the idf.py in Ubuntu but I got the same error.
Both in Ubuntu and in Windows, the Doctor Command returns nothing. It does not even open the terminal or any window. I am not sure what it should return but some online discussions were asking about its return so I wanted to note it here.
Edit: When I tried the examples on Ubuntu, they actually build just fine. Doctor Command also works with examples.
However, the main code has still issues. Initially, I assumed I made some mistakes with esp-idf configurations. But, perhaps that was not the case.
I had the same problem and ended up editing my project's CMakeLists.txt. When I added "esp_wifi" to the "REQUIRES" list, it worked for me:
idf_component_register(
SRCS "main.c"
INCLUDE_DIRS res
EMBED_FILES res/settings.html
REQUIRES esp_wifi
)
When I build and run as webgl in unity it works perfectly (on local server), however when I upload it to my server, and try to run it, I get the following error:
Unable to load file Build/web_gl_3.framework.js.gz! Check that the file exists on the remote server. (also check browser Console and Devtools Network tab to debug).
I have checked that the file does exist on the server, however it is encrypted so I cannot troubleshoot the code much (it is automatically generated by Unity in the webgl build folder anyway).
In the console it says:
Refused to execute script from 'https:[private_info]/Build/web_gl_4.framework.js.gz' because its MIME type ('application/x-gzip') is not executable, and strict MIME type checking is enabled.
How can I resolve this error?
In Terminal everything is working just fine:
alex#ubuntu:~/workspace/spt$ export PATH=$PATH:/usr/lib/meteor/bin
alex#ubuntu:~/workspace/spt$ mrt
Stand back while Meteorite does its thing
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
[[[[[ ~/workspace/spt ]]]]]
Running on: http://localhost:3000/
Now I want to see the output in Eclipse console, so I create "External Tools Configurations" and have:
Also I add the PATH:
However when I try to run I get the following output in console:
[1m[37mStand back while Meteorite does its thing[39m[22m
[1m[37mDone installing smart packages[39m[22m
[32mOk, everything's ready. Here comes Meteor![39m
/home/alex/.meteorite/meteors/meteor/meteor/2d8b41a87cec884489ead138b5dfea31487363f3/meteor:
line 7: uname: command not found Sorry, this OS is not supported.
Any ideas on what's going on?
I think somehow when it says Append its a loose definition. If meteor can't find uname it means path has been emptied to /usr/lib/meteor/bin. You could create a complete path variable manually:
Find out your path, run echo $PATH in your terminal, and add your :/usr/lib/meteor/bin to it and use this as your path in that dialog in the screenshot.
I am trying to install ZEND FRAMEWORK on my localhost but failing miserable. I am following the below mentioned steps but don't know where am I going wrong. Please help me with the same.
Steps are as follows that I followed:
Downloaded the ZEND Framework full package version 1.11.7 which is about 25 Mb in a zipped version and then unzipped it to a folder called ZendFrameWork.
Copied the ZendFramework folder inside my c:\xampp\php\
changed the "include_path = '.;\xampp\php\PEAR;\.;C:\xampp\php\ZendFramework\library' " in the php.ini file.
Then restarted the apache server.
EDIT :: I have successfully managed to get the zf command to run without any errors. but now, all it does is, after i enter "zf create myproject" it just gets stuck with the cursor blinking on the next line. And if i press CTRL+C, i get the message : Terminate batch job ? (Y/N)
Then set the environment variable for zf.bat file as " C:\xampp\php\ZendFramework\bin "
But when I try to execute the " zf create sampleProjName " from command line it does nothing, so then I used Windows Powershell and it gives the error which I have attached below.
Waiting for your response.
Thanks in advance.
Try using normal cmd - not powershell. Works fine for me.
Thanks for all your response.
I successfully installed Zend Framework.
I removed the full installation and replaced it with minimal installation and also I did not have php.exe set as an environment variable, so i did that too and also in the php.ini file i needed to write the zend library first before the pear one.
And this was it, TA-DA, it worked.
:)
While building our project on the Build Server, the compilation fails with the error message:
TlbImp: error TI0000 : The input file 'C:\*.dll' is not a valid type library.
We tried to manually invoke the TlbImp command thru the VS2005 Command Prompt and the same error message appeared.
To investigate, we tried to create a clean build environment in a Virtual Machine (Vbox), then we run the build there. It went fine.
We also tried to invoke the same TlbImp command thru the VS2005 Command Prompt and it succeeded.
With that, we are assuming that there is nothing wrong with the DLL. Do you have any idea what scenario(s) can cause this problem?
EDIT:
Found the problem, see my answer. ;)
If it is working on one machine and not on the other, then most probably some dependency of this DLL is missing in your machine. Inspect the dll through DependencyWalker and you will get to know that which dependency hasn't been built properly.
After closer inspection, we found out that the environment variables on the official build server is FUBAR.
The official build server was installed with both VS2003 and VS2005. Our project is VS2005. The build script is using components from VS2003 instead of VS2005 because the VS2003 paths (Path, LIB, LIBPATH and INCLUDE) were first declared before the VS2005 paths.
A simple SET command to override the environment variables with the "correct ones" fixed the build!
Thanks!