I'm attempting to set up this Rust template project to get started doing Rust development for ESP32: https://github.com/esp-rs/esp-idf-template
I've installed the Rustup esp toolchain, as described here: https://github.com/esp-rs/rust-build
At the Generate the Project step, I chose these parameters:
Configure project to use Dev Containers = false
ESP-IDF native build version = v4.4
Rust toolchain = esp
STD Support = true
MCU = esp32
At the Build step, I get this output (second run displayed, first run compiles a long list of dependencies before this point):
C:\Users\Me\boop\doop>cargo build
Compiling esp-idf-sys v0.31.6
error: failed to run custom build command for `esp-idf-sys v0.31.6`
Caused by:
process didn't exit successfully: `C:\Users\Me\boop\doop\target\debug\build\esp-idf-sys-cafd80a349bfdbb2\build-script-build` (exit code: 1)
--- stdout
cargo:rerun-if-env-changed=IDF_PATH
cargo:rerun-if-env-changed=ESP_IDF_TOOLS_INSTALL_DIR
cargo:rerun-if-env-changed=ESP_IDF_VERSION
cargo:rerun-if-env-changed=ESP_IDF_REPOSITORY
cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG_DEFAULTS
cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG
cargo:rerun-if-env-changed=MCU
IDF_PYTHON_ENV_PATH=C:\Users\Me\boop\doop\.embuild\espressif\python_env\idf4.4_py3.10_env
PATH=C:\Users\Me\boop\doop\.embuild\espressif\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin;C:\Users\Me\boop\doop\.embuild\espressif\tools\cmake\3.23.1\bin;C:\Users\Me\boop\doop\.embuild\espressif\tools\ninja\1.10.2\;C:\Users\Me\boop\doop\.embuild\espressif\python_env\idf4.4_py3.10_env\Scripts;C:\Users\Me\boop\doop\.embuild\espressif\esp-idf\release-v4.4\tools;%PATH%
Current system platform: win64
Skipping xtensa-esp32-elf#esp-2021r2-patch3-8.4.0 (already installed)
Skipping cmake#3.23.1 (already installed)
Skipping ninja#1.10.2 (already installed)
Skipping esp32ulp-elf#2.28.51-esp-20191205 (already installed)
IDF_PYTHON_ENV_PATH=C:\Users\Me\boop\doop\.embuild\espressif\python_env\idf4.4_py3.10_env
PATH=C:\Users\Me\boop\doop\.embuild\espressif\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin;C:\Users\Me\boop\doop\.embuild\espressif\tools\cmake\3.23.1\bin;C:\Users\Me\boop\doop\.embuild\espressif\tools\ninja\1.10.2\;C:\Users\Me\boop\doop\.embuild\espressif\python_env\idf4.4_py3.10_env\Scripts;C:\Users\Me\boop\doop\.embuild\espressif\esp-idf\release-v4.4\tools;%PATH%
--- stderr
Using managed esp-idf repository: EspIdfRemote { repo_url: None, git_ref: Branch("release/v4.4") }
fatal: No names found, cannot describe anything.
Using esp-idf v4.4.1 at 'C:\Users\Me\boop\doop\.embuild\espressif\esp-idf\release-v4.4'
fatal: No names found, cannot describe anything.
Error: Access is denied. (os error 5)
I get the same error when I choose ESP-IDF native build version = v4.3.2, although without the fatal: No names found, cannot describe anything. messages.
I get an identical error when attempting to build this Rust ESP32 demo project: https://github.com/ivmarkov/rust-esp32-std-demo
This was run as Administrator.
In my search for a solution, I found this: Why os.rename sometimes returns error access is denied python Per the top answer, I disabled "Show frequently used folders in Quick access" in File explorer, but unfortunately the build error has not changed.
What access is being denied, and what could be causing the denial, even when run as Administrator?
Secondarily, what is the cause and meaning of the fatal: No names found, cannot describe anything. messages?
I've been working through the same issue today.
It is caused by a change in the embuild dependency: https://github.com/esp-rs/embuild/commit/d8f8da228f1e1e6c105074d96617a8601092f633
Trying to write permission data to an open file causes the 'os error 5
I've submitted a PR to the project: https://github.com/esp-rs/embuild/pull/56
Now merged, cargo update and you should be good!
I'm trying to build the system image, but the build process fail at very early stage,
mainly it stops at the ..blueprint/microfactory.bash on the line 62 with this error
"flag provided but not defined: -b"
Is there anything im missing.
sorry this is my first time trying to build it bear with me.
Building a github .xcodeproject and running into the same error for two forks of manOpen. I am having trouble understanding what the issue is.
I am new to building using Xcode so figure this must be simply a "new user mistake".
I cloned the project into /usr/local/Projects
When I build I get this error:
Lex /usr/local/Projects/ManOpen/ManOpen/cat2html.tproj/cat2html.l (in target 'cat2html (Tool)' from project 'ManOpen')
cd /usr/local/Projects/ManOpen
export DEVELOPER_DIR\=/Applications/Xcode.app/Contents/Developer
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lex -o /Users/john/Library/Developer/Xcode/DerivedData/ManOpen-bztxjqkaqtyazxhiudyipgfevout/Build/Intermediates.noindex/ManOpen.build/Debug/cat2html\ \(Tool\).build/DerivedSources/cat2html.yy.c /usr/local/Projects/ManOpen/ManOpen/cat2html.tproj/cat2html.l
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/gm4:stdin:1744: ERROR: end of file in string
Command Lex failed with a nonzero exit code
Not a fix, but a work-around: ManOpen Uses cat2rtf as of Mac OS 10.4, so you can remove cat2html as a dependency of ManOpen.
I'm trying to create a IPA from my cordova-ionic project using visual studio 2015. I can run the project on an iOS simulator using remotebuild.
I have followed the steps here and created a provisioning profile (using my free Apple ID). I am in a tricky situation and the iOS device that I would like to run the project on is in a different country.
I'm creating the provisioning profile on my friend's mac with the iOS device attached. I am then logging into an El Capitan VM on my machine and using the provisioning profile generated on my friend's mac to attempt to create an IPA. I am following what is outlined here and running the project on visual studio using debug and remote device or local device.
I get the following error:
Error: Remote build error from the build server Build failed with error Error code 65 for command:
xcodebuild with args: -xcconfig,/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/cordova/build-debug.xcconfig,-project,BookYourTutor.xcodeproj,ARCHS=armv7 arm64,-target,BookYourTutor,-configuration,Debug,-sdk,iphoneos,build,VALID_ARCHS=armv7 arm64,CONFIGURATION_BUILD_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/sharedpch - 1 BookYourTutor 1
Looking at the output from build, towards the end, i see:
Libtool /Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device/libCordova.a normal armv7
cd /Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/CordovaLib
export IPHONEOS_DEPLOYMENT_TARGET=8.0
export PATH="/Users/noyolk/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Users/noyolk/Downloads/Xcode-beta.app/Contents/Developer/usr/bin:/Users/noyolk/.taco_home/node_modules/taco-remote-lib/2.2.1/node_modules/taco-remote-lib/node_modules/ios-sim/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
/Users/noyolk/Downloads/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -static -arch_only armv7 -syslibroot /Users/noyolk/Downloads/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.0.sdk -L/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device -filelist /Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/Cordova.LinkFileList -o /Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device/libCordova.a
=== BUILD TARGET BookYourTutor OF PROJECT BookYourTutor WITH CONFIGURATION Debug ===
Check dependencies
Signing for "BookYourTutor" requires a development team. Select a development team in the project editor.
Code signing is required for product type 'Application' in SDK 'iOS 10.0'
** BUILD FAILED **
The following build commands failed:
Check dependencies
(1 failure)
Failed to build app for buildNumber 708: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/cordova/build-debug.xcconfig,-project,BookYourTutor.xcodeproj,ARCHS=armv7 arm64,-target,BookYourTutor,-configuration,Debug,-sdk,iphoneos,build,VALID_ARCHS=armv7 arm64,CONFIGURATION_BUILD_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/sharedpch
MSBUILD : cordova-build error : Error: Remote build error from the build server Build failed with error Error code 65 for command: xcodebuild with args: -xcconfig,/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/cordova/build-debug.xcconfig,-project,BookYourTutor.xcodeproj,ARCHS=armv7 arm64,-target,BookYourTutor,-configuration,Debug,-sdk,iphoneos,build,VALID_ARCHS=armv7 arm64,CONFIGURATION_BUILD_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/sharedpch - 1
Error Remote build error from the build server Build failed with error Error code 65 for command: xcodebuild with args: -xcconfig,/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/cordova/build-debug.xcconfig,-project,BookYourTutor.xcodeproj,ARCHS=armv7 arm64,-target,BookYourTutor,-configuration,Debug,-sdk,iphoneos,build,VALID_ARCHS=armv7 arm64,CONFIGURATION_BUILD_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/noyolk/.taco_home/remote-builds/taco-remote/builds/708/cordovaApp/platforms/ios/build/sharedpch - {1}
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
With what I believe to be the most important bit being,
=== BUILD TARGET BookYourTutor OF PROJECT BookYourTutor WITH CONFIGURATION Debug ===
Check dependencies
Signing for "BookYourTutor" requires a development team. Select a development team in the project editor.
Code signing is required for product type 'Application' in SDK 'iOS 10.0'
** BUILD FAILED **
I'm having trouble understanding what exactly this means or how I should fix it. For context, I'm using xcode 8 beta 4 on my El Capitan VM.
I've tried searching around for this 'error code 65' and the error message 'Signing for XXX requires a development team. Select a development team in the project editor.' but have not had much luck.
Any help is greatly appreciated.
Downgrading to xcode 7 from xcode 8 beta 4 seems to have resolved this issue.
There is a change due to the release of iOS 10.
Reference https://dpogue.ca/articles/cordova-xcode8.html for a workaround.
I actually had to do some trial and error. The above link helped a lot, but the issues were still with what Apple was needing for XCode 8 to accept the build request. My settings in build.json are similar to this:
"ios": {
"debug": {
"developmentTeam": "[my team id]",
"provisioningProfile: "[my provisioning profile]"
},
"release": {
"developmentTeam": "[my team id]",
"provisioningProfile: "[my provisioning profile]"
}
}
}
To get your developmentTeam, log into developer.apple.com, click on Membership, and you will see your TEAM ID. Put that in as the developmentTeam.
For the provisioningProfile, open XCode --> Preferences, click on your profile, View Details. Click on your provisioning profile, right click, and Show in Finder. Your provisioning profile is the entire file name, minus the .mobileprovision file extension. Save build.json, rebuild your project, and you should be good to go.
I am using Marmalade to build a PlayBook app, but I think my question applies to PlayBook apps in general. I have successfully created a debugtoken.bar file and have installed it on my device. When I go to try to install a built application.bar file on the device, I get:
[execute] "blackberry-deploy.bat -device 192.168.1.114 -password ******* -installApp -package deployments\default\playbook\release\Quote Unquote.bar"
Info: Sending request: Install
Info: Action: Install
Info: File size: 6400334
Info: Installing ...
Info: Processing 6400334 bytes
actual_dname::
actual_id::
actual_version::
result::failure 881 required signatures missing (RDK, AUTHOR)
ERROR: error running blackberry-deploy
***ERROR***
Note that this is the Marmalade deploy tool running the standard PlayBook installer.
What I don't understand is: I thought the point of using a debugtoken.bar file was that you could install unsigned apps. I have in fact successfully deployed these unsigned apps using the Marmalade deploy tool just like this. But I was having problems signing the app for distribution, so I went back and did everything from scratch, requested new code signing keys from RIM, made a new debugtoken.bar file and installed it, etc. And now I'm worse off than I was before because I can't even install to the device now.
So again: My understanding is that the point of debugtoken.bar was to be able to deploy to the device before actually signing the application.bar for distribution. So what does this error message even mean?
To answer my own question:
For deploying a "debug" build to a device, it's critical to have
Application-Development-Mode: true
in the MANIFEST.MF within the .bar file.
A stupid mistake, but I'll leave this up in case it helps anyone...
Taking a look to the QNX deployment plugin "C:\Marmalade\6.1\s3e\deploy\plugins\qnx\qnx.py" I found that 'FOR DEVELOPMENT' option is false if the 'playbook_keystore' is given so I just cleared the signing section on the Marmalade System Deployment Tool and it is not longer trying to sign it