Using Xcode-v7.1.1, embedXcode+, ArduinoMAC-v1.6.6,
I can't get embedXcode to work with any of the boards !
The installation of embedXcode and embedXcode+ was done according to the following LINK...
The board I intend to use is the "NodeMCU 0.9 ESP-12" as chosen in the create-new-project menu (as seen in middle-image below):
The error crops up by running "Build" (not the "All"-Target):
The error that I get is "nodemcu board is unknown" (see image at bottom)
Can anybody help me with this ? Highly appreciated !!
My case was solved by moving Arduino.app directly to /Applications folder.
I have multiple Arduino.app under i.e. /Applications/1.6.6/ or /Applications/1.7.4 ...etc. then the build process could not find the board.txt file in the Arduino.app.
Hope this helps.
Related
I have a question, after I have whole built the AOSP source code, it generates couple image files, such as ramdisk.img, recovery.img, system.img, res-package.img,etc .
Right now, I am considering partial flashing my Android Box without formatting all of the system, for keeping some previous data remains.
Therefore, I just tried to use the command “adb sideload filename.img”, which filename might be ramdisk,recovery, etc.
Then, after I did so, the android system shows the message :
“footer is wrong”
“signature verification failed”
“Installation aborted”
There, what should I correct my command, to make the process correct?
as the figure shows enter image description here
And, my methods to do so is trying to refresh a new system feature, but keep the previous data, such as APPs, or user data, remain, does anybody have other good suggestions? Thank you in advance.
it depends on the flash type and file-system you are using, and it is not possible to partially flash in the partition, but you can update the partition.
The app is being built on another persons computer and then sent to me to test. I am extremely new to this but have been testing apps for a few months. I just don't do programming at all. I can maneuver my way around inside Xcode 7.1 pretty well. However, I do need to fix these errors in order to test this current app. Can someone help me out?
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1
I also have another error that reads
Error reading '/Users/logjam3/Desktop/Cosmo Client/Cosmo Client.xcodeproj'
This is exactly the path to where my project is so I don't know why I get this error.
You have to change the prefix header source location. You can do this by searching for prefix header then changing the location by pressing the 'file' icon on the right sidebar of Xcode.
I must be missing something. After downloading AntlrWorks2 I found the executable bin/antlrworks2.exe and bin/antlrworks264.exe. Aren't these supposed to be the standalone version of the tool? Neither works for me; after a NetBeans splash screen, the first times around I got an error message on missing packages; after a couple of times I chose to go on regardless, but now (still after the initial spash screen) there is simply nothing happening at all.
I can't find any tutorial or manual detailing how to run AntlrWorks stand-alone, so any help is much appreciated.
This is due to a bug in the NetBeans platform. I filed a report but it hasn't received a reply yet:
Cannot launch platform application after moving installation folder
Here is a workaround that does not delete any preferences you have customized:
I found that deleting just the var folder under the user's generated
.antlrworks2 settings folder resolves the issue...
Still an issue as of date of this post. Deleting the .antlrworks2 folder from \users\username\AppData\Roaming does work - you can find this folder by putting %APPDATA% into your file explorer address bar (exactly as shown) - that will go to the app data folder for your current user login session. Delete the .antlrworks2 folder and then re-run the app.
How to avoid the window "No source available" while stepping into debug mode on VS2010 SL5
In Tools, Options, Debug, General Page. Check if you have 'Enable .NET Framework source stepping' enabled, if it is enabled, disable.
I tried all the suggested fixes; Nothing worked for me.
I finally figured out the solution after several hours of trial & error iterations.
It turns out that the 'No Source Available' error is due to a stack-overflow within the VS debugger env.
The C/C++ code function that was supposed to be stepped-into (by VS debugger), was using a variable that was initialized to a stack array of a few MB in size. When I replaced this with a heap allocation, VS was successfully able to step into the code.
This worked for me.
Please note that in my case, the actual code (with the stack allocation) ran without a stack-overflow error within the debugger (if I skip the No source available error). It was just that VS's debugger's was not able to step-into a particular function sitting inside another C/CPP file, because of the internal stack overflow.
Hope this helps.
You can hit Shift+F11 to step out and it will complete whatever unavailable function it is in and stop at the next line (it may be unavailable as well, but continue to use Step Out until you get to code you want to examine.)
Regarding VS2019, a description for the issue is provided at MSDocs.
For the requisite vcruntime and ucrt source files, the problem can occur after importing from a previous VS version which has since been uninstalled.
To prevent VS from using the old directories, find the solution property pages and navigate to the Debug Source Files Dialog Box.
Click the tick button to check the entries where any invalid ones can be removed.
The vcruntime and ucrt source should always exist in the directories, and the path at the top of the Browse to find source code dialog should always show the correct path.
In my case, because of a venerable drive bug, it is given to prompt for the "D" drive instead of the "C" drive. Further, the provided path cannot be pasted over to refresh the view, so, if none the wiser, one has to use the dialog to navigate all the way up to the required location from the desktop or equivalent.
Here there is an extension for this issue:
http://erwinmayer.com/labs/visual-studio-2010-extension-disable-no-source-available-tab/
But in my own experience before finding this article (I was in page but I was trying to fix it myself without reading article) I have fixed this problem just by accepting a confirmation message saying something like "Selected source file is different from compiled assembly. Are you sure you want to use this file for debug?". But I can't remember exactly what I did to get this message. I think there was a linklabel which I clicked on "No source available" window and then confirmation message appeared and after confirm the problem ran away.
I am trying to develop QRCode reader application in iPhone.
I am trying to use ZXing SDK. i have successfully run the sample application given by ZXing. But i ma trying to develope new application as per instructions in Readme given by Zxing. but when i am trying to add ZxingWidget in build phases. it going add but it shows like below
I think it will getting problem to me. When i am trying to run application it will give erros like Lexical or Prepocessor issue File not found.
Is am doing any thing wrong when am added to files to application.
Actaully first of all i added ZxingWidget.xcodeproj to my application by drag and drop. But it wont give any alert window would you like copy like similar when we adding images or files to xcode. and next i added cpp and iphone folders to xcode application. and later i added the frameworks as per read me.
Please any one help me in this issue.
Thanks in advance
Pretty hard to help without the real error message. In the Issue Navigator, you can Right Click > Reveal in Log to see the complete error that you can copy and paste.
That said, it sounds a bit like it can't find the headers (though I'm just guessing without the real error message.) If so, double check steps 4 and 5 of the readme.
if you run on real device, the problem will be solved.
I don't know the reason.
But I guess It's related to Build Products Path.