I've seen this warning before, and I don't remember how I fixed it...
warning: Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.3.3 (8J3)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib (file not found).
Following that path, I find that...
/Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.3.3 (8J3)/Symbols/Developer/
...doesn't exist.
.../Symbols/ only has /System/ and /usr/
Change your "Deployment Target" in your project preferences. Select the one matches o your device.
Simple solution, but I had the same error, after restarting my iPad it was gone.
related: http://www.cocos2d-iphone.org/forum/topic/17730
Weird problem from old (obsolete?) software versions.
The question is now moot, no?
Related
The .xnb files that the Monogame pipeline creates are way too big. I have a folder of images that makes up 8 mb. When passed through the pipeline and published for installing creates 2 gb of .xnb files... that's a little bit of a problem.
Example: An image (png) is 32,6 kB, gets turned into a .xnb.deploy worth 10,1 MB.
I'm not sure what to do about this. There must be something obvious I'm missing because I feel it shouldn't be this way at all, am I missing some compression setting in the pipeline and if so where do I find it? Thanks
Edit: Tried in both Debug and release, same result.
Edit 2: I've tried many of the solutions that I've found on the internet without any luck. I've tried to set the content pipeline settings to Compress - True but that did nothing.
I've tried to go through every image(around 500) and turning the TextureFormat to DxtCompressed, I had an error that I needed to have the ResizeToPower set as True, so I did that and tried again. This gave me the error "processor textureprocessor had unexpected failure" and I could not find a solution to that... so I gave up on that idea.
I also tried following this link http://rbwhitaker.wikidot.com/forum/t-904011/xnb-compression but could not find the "compress content pipeline output files" option anywhere.
ERROR in C:\projects\xxxx\node_modules#ng-bootstrap\ng-bootstrap\modal\modal-ref.d.ts
(1,1): error TS2688: Cannot find type definition file for 'core-js'.
There was a bug in the #ng-bootstrap 1.0.0-alpha.12 release that was corrected in 1.0.0-alpha.13. More details are available in https://github.com/ng-bootstrap/ng-bootstrap/issues/1027
In short: 1.0.0-alpha.12 release is broken, use 1.0.0-alpha.13 release
I got the same issue after switching to the #ng-bootstrap 1.0.0-alpha.12.
After switching to alpha.13 the error disappeared.
I was updating the packages in my emacs 25.0.50 build. And for some reason it didn't work properly. When I restarted emacs I received the following fatal error message:
error: Recursive load, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/cl-extra.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/bytecomp.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq-25.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/cl-extra.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/bytecomp.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq-25.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/cl-extra.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/bytecomp.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq-25.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/cl-extra.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/bytecomp.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq-25.elc, /Users/Maurice/.emacs.d/elpa/seq-2.15/seq.elc, /usr/local/Cellar/emacs/HEAD/share/emacs/25.0.50/lisp/emacs-lisp/cl-extra.elc, /Users/Maurice/.emacs.d/core/prelude-packages.elc, /Users/Maurice/.emacs.d/init.el
Could anyone explain to me what I should do to rectify this situation?
"Recursive load" means you have a circular dependency between packages. cl-extra pulls in (by way of load or require, etc) seq, which pulls in bytecomp, which pulls in cl-extra, which pulls in seq, ...
By the looks of it, you have a locally installed third-party packaged version of seq, so removing that as the probable culprit seems like the way to go; but there is a reason it's being pulled in, so it's likely that something else stops working because of this change, and so on.
Prelude seems to want this; maybe you'll need to give up on it until this problem has been resolved. (File a bug report if you can!)
I am getting
bnfc: src/LexBNF.x:(80,13)-(86,20): Non-exhaustive patterns in case
error. What does it mean?
It doesn't really say what's wrong my BNF grammar, and I have no idea how to find the error. I tried looking for it for past few days, unsuccessfully.
I checked if every symbol is defined somewhere in the file, I fixed some rules, nothing helped.
I used to have 2.6, and had this same problem. However, on the tool's webpage, it says that some improvements about error messages have been made since earlier versions, so I installed the latest version (2.8), and that gave me a more informative error message. I'd recommend that you do the same.
Could be because you forgot the backslash on the grammar definition.
The link show a similar case: https://groups.google.com/forum/#!topic/proglang-course-2013/guL-rKm4Q_8
i have a pattern that is used all over my codebase that throws a frivolous warning on jshint.
I got the reason for the warning using --verbose. it is W002.
I can disable that warning on each js file by adding /*jshint -W002*/
but i can't see any way to disable that warning by instead of editing every single file, adding an option on my global jshint.json configuration file.
Is there any way to do that?
edit:
seems to be a common problem
I was about to ask this question, then I found the answer myself.
Get the warning ID. Eg, for
A trailing decimal point can be confused with a dot
The warning ID is W047. jslinterrors can help find the warning IDs.
In your .jshintrc:
}
"-W047": true
}
The syntax is really poor with the magic numbers (commonly regarded as a bad idea in programming) - eslint does it better - but that's how to globally ignore a warning.