I am integrating openCV in my project.
When i integrate in my sample application it works fine(In Targets Here i placed the compile source code as in "Objective c++")
But when i integrate the same application in to my "Main application"(In Targets Here i placed the compile source code as in "According to file type") it says error as "Lexical or preprocessor issue map file not found"
If i put the target settings in "Objective c++" then it raises an error in ASIAuthenticationDialog.m
I followed some answers posted here.
This answer worked for me in my sample app(here i did not have any parsing i placed the compile source code as 'objective c++') But in my Main Application where i do parsing it raises error(i placed the compile source code as 'According to file type')
Please Guide me.
Look at XCode's Log navigator : each build produce a log you can navigate into (showing only errors/warning), try and find exactly WHICH source file your compiler was trying to compile. (and also at which step it occurs : precompiled header / compiling / linking ?)
As you seem already aware, the problem might not be from OpenCV, but from your classes that depend on it - when the pre-compiler tries to solve import statements - I although thought that renaming your 'm' files in 'mm' solved this problem...
But if some library you're using need plain C (ASIAuthenticationDialog.m) - I guess that's the problem you're facing could rephrased : 'How do i mix C and C++ sources ?'
Maybe this SO post might help
Good luck !
Related
I installed the Haskero plugin into VS Code as per the instructions there. I then followed the steps outlined in https://gitlab.com/vannnns/haskero/blob/master/client/doc/installation.md, or specifically Steps 5 and 6 as I already had a Stack project built in that directory. VS code starts up and it opens the project folder. When I hover over a function for example it shows the signature for that function, but when I select "Go to Definition", after thinking for a bit, it returns "No definition found for XXX". This is even when the definition is in the same file. For types, the hover displays nothing at all.
P.S. What puzzles me is that I don't recall anywhere associating ghc with the VS Code project so I am curious as to how it knows which compiler to use?
It appears to be working now. I had to do a complete build before it was able to construct the necessary indices
I am trying to code unit tests to my vanilla web-components and all tests I write have a lot of warning as pasted in my question. I found some similar issues to others using ReactJs but it is not my case at all and, on top of that, my index.htnl file consuming the webcomponent doesn't show such warning: I only see it in test files. Well, I could ignore it but I would prefer figure out what configuration I am missing and realy on warnings as really important thing to check out. Maybe some extension I should add. I tried "Prettier - Code Formatter" without success.
The complete project can be clone from https://github.com/jimisdrpc/simplest-webcomponet
VSC picture
I'm currently taking over someone's else project who was in a different country. He is using MumbleKit in his project, however when i try building the project, these errors occurred.
error: input is not a PCH file: '/Users/kai/Library/Developer/Xcode/DerivedData/TestBuild-bivflkvgwypsqidilllttbdfyjjq/Build/Intermediates.noindex/PrecompiledHeaders/SharedPrecompiledHeaders/70367429320928002/CELT-0.7.pch.gch'
fatal error: file '/Users/kai/Library/Developer/Xcode/DerivedData/TestBuild-bivflkvgwypsqidilllttbdfyjjq/Build/Intermediates.noindex/PrecompiledHeaders/SharedPrecompiledHeaders/70367429320928002/CELT-0.7.pch.gch' is not a valid precompiled PCH file
Now, i have tried fixing the header path file and cleaning the project and deleting derived folder's content, still this error occurred. I believe xcode is trying to find a pch file but this .gch is being created instead. How can i prevent this .gch from being created in the derived folder? Or how do i fix this in general since i don't really deal with 3rd party project dependency before.
EDIT : I believe this error is coming from the 3rd party Mumble kit, CELT-0.7 project
Okay, I've found the solution, Mumble kit's CELT project have a file : Base.xcconfig.
There is a variable, GCC_PRECOMPILE_PREFIX_HEADER, initially it was set to YES, after set it NO, that fixed it. Though it will be nice if someone would explain to me what it does exactly.
I've just installed Visual Web Developer Express 2010, and I'm trying to write & compile some basic VB code (to do with Object Data Sources).
However, when I write my class (which is sitting in APP_Code folder), I find that :
1) I dont get any intellisense / code completion happening, and that
2) More of a problem, the compiler doesn't pick up coding syntax errors, and gives a successful build no matter what I write in the class file.
What am I missing here ?
Thanks,
Bazza
The "Build Action" in the properties of the file needs to be set to "Compile" - my guess is that it is something else now, causing the compiler to ignore the file.
I created a project "Sample Code"... here I just paste sample code... much of it is snippets that won't compile.
Is there some project-specific setting I can make so that Eclipse doesn't try to compile it?
I would prefer not to have the source code littered with red error markers.
Put your code in a non-java project, ie a general project.
Downside: you will have to create package directory structure (unless you can copy and paste from somewhere else).
Upside: it won't try to compile.
MY SOLUTION
ok, this is not an exact solution to my problem... but it is another way to do it and I kinda like it now...
I simply forget about using Eclipse to store the sample java files!
I found a good program CodeBox for Mac to store code snippets and I'm sure there exist such things for Windows, Linux too...
there interesting thing is that when I choose from this program to open the java snippet file (.java) in an external editor (Eclipse), it will open in Eclipse without any Syntax checking... wohoo! no squiggly lines
Because of this, it is not full blown code highlighting... classes and variables same color... but that's ok.. still quite readable. Much more than if it was in Eclipse with syntax highlighting running on it...
So basically, if you want to get rid of these red squiggles... one way to do it is don't keep sample .java (or other language) files in a project in Eclipse... simply keep them in the filesystem or code storage app and open them with Eclipse when you want to view them.
Depending on how you prefer to structure your project:
you could put your java files into a separate folder that is not configured as a source folder. There is an entry in the eclipse help on how to configure your build path.
or you can set exclusion-patterns in the build configuration, so that specific packages or files that follow a pattern you define don't get compiled.
Yet another way to handle your snippets could be to use a Scrapbook page.
Eclipse won't highlight anything in a scrapbook page but you can select code parts inside the page and execute them isolated. That's nice if you're experimenting and don't want to set up a whole class with imports and methods just to see if a specific snippet works as expected.