Hy, I want to use the QuickDialog library but gives me error.
The step that I made:
download it from github
copy the directory into my project's directory
add QuickDialog.xcodeproject
my project --> Build Phrases:
Target dipendencies: add QuickDialog
link Binary : add libQuickDialog.a
include in mi file Prefix.phc :#import
my project --> Build Settings:
Other linker flags: -ObjC
User header search paths : "${PROJECT_DIR}/QuickDialog" and check the box
always serach user path : YES
run
But give me the error:
QuickDialog/QuickDialog.h file not found
What is wrong???
Please help me!!
If you put this: "${PROJECT_DIR}/QuickDialog"
and you try to import "QuickDialog/QuickDialog.h"
that means that he goes in directory: "${PROJECT_DIR}/QuickDialog/QuickDialog/QuickDialog.h" ?
Did you try to put just: "QuickDialog.h" ?
EDIT: The solution is here: Including QuickDialog into Xcode 4.2 Project
Related
I'm trying to add an iOS framework called WebPDecoder.framework using CMake. I found that the right way to do this would be:
find_library(IOS_WEBP NAMES WebPDecoder PATHS "${PROJECT_SOURCE_DIR}/lib/ios" NO_DEFAULT_PATH)
The framework folder is in the lib/ios folder, but CMake can't find it. Adding --debug-find I'm getting the following output:
find_library called with the following settings:
VAR: IOS_WEBP
NAMES: "WebPDecoder"
Documentation: Path to a library.
Framework
Only Search Frameworks: 0
Search Frameworks Last: 0
Search Frameworks First: 1
AppBundle
Only Search AppBundle: 0
Search AppBundle Last: 0
Search AppBundle First: 1
NO_DEFAULT_PATH Enabled
find_library considered the following locations:
The item was not found.
Why is CMake ignoring my custom path?
I had the same problem. It turned out that a copypasted CMake setup for iOS was setting CMAKE_FIND_ROOT_PATH_MODE_LIBRARY to ALWAYS. To allow CMake to find the custom path under project source directory, the setting must be BOTH or NEVER.
I have created an application on angular 7 and ionic 4.
I tried to edit app.routing.ts file, setting path and component. From then on I am getting this error below:
ERROR in ./src/app/department/department.module.ts
[ng] Module build failed (from ./node_modules/#ngtools/webpack/src/index.js):
[ng] Error: ENOENT: no such file or directory, open 'C:\Users\x\department\department.module.ts'
[ng] at Object.openSync (fs.js:436:3)
[ng] at Object.readFileSync (fs.js:341:35)
[ng] at Storage.provideSync (C:\Users\x\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:98:13)
Make sure department component exist, check the templateUrl that corresponds to the file name you are referencing. You may have also modified the path unknowingly during modification of app.routing.ts file.
C:\Users\x\department\department.module.ts
This error occurs when your component can't be found with your app.module settings.
Follow these steps to solve your problem:
Check if the module.ts file exists.
Check the relative path.
The path is case sensitive (maybe the .ts file is Department).
Both answer are useful from #trustidkid and #vinay sharma. If there is someone has been facing the same problem;
1-Go to to the file that the error has occurred in. (To go directly to the file, click the error line shortly [CTRL+Click] (CMD+Click on MacOS):
ERROR in ./src/app/department/department.module.ts
Then check the path address if it is exactly true pointing the file. Most of these problems are having similar solutions. Just be sure about the path address of the file you want to point and the address mentioned in the other file which the error occurred.
This problem happens when you delete a component but forgot to delete its import from module.ts.
For example: TestComponent is deleted so you have to also delete:
import { TestComponent } from './test.component'
If you have a folder mapping on a windows machine like me, do not try to build it from a mapped folder, go to the original folder and build it from there.
Mapped Folder has a small icon like this:
In my case I had prime ng version that did not support a particular module, I simply commented it out and it worked.
While integrating latest robbiehanson's XMPPFramework, I came up with an error : CocoaAsyncSocket/GCDAsyncSocket.h' file not found
and a simliar kind of error:
/Users/Con/Documents/PROJECTS/Cor/Cor/Libraries/XMPP Framework/Core/XMPPLogging.h:62:9: 'CocoaLumberJack/DDLog.h' file not found
Help!
open your Built Setting on your project, then set it like
User Header Search Paths = $(SRCROOT) // recursive.
Always Search User Paths = YES
I am doing a swift framework and i want to use old objective c classes. For this, i use the bridging headers method but when i try to build appears this error:
<unknown>:0: error: using bridging headers with framework targets is unsupported
I added my {PROJECT}-Bridging-Header.h to Objective-C Bridging Header in Swift Compiler - Code Generation
How can i solved it?
I did in applications and runs Ok, but in this framework no
Thanks
iHart is correct
For that follow below steps :
1. remove your bridging header and all related file . . .
2. Clean Build/Solution. Cmd + Shift + k like . . .
3. Create new Objective-C file for bridging header file creation . . .
But what I had to do also is add all the missing header files to my umbrella header. And also make sure that these files are marked public. In Xcode you can add them to the public section under Build Phases -> Header.
For that follow below steps:
Remove your bridging header and all related file.
Clean Build. Cmd + Shift + k like.
Create new Objective-C file for bridging header file creation.
Now, add your others file.
I hope, this work for you because we solved exactly the same error this solution.
When I use hpple and build, aways show " 'libxml/tree.h' file not found " error.
I have ，
set [Header Search Path] "${SDKROOT}/usr/include/libxml2"
set [Other Linker Flag] value as "-lxml2"
Oh, sorry, I just set the TARGETS's Build Settings forgot set the PROJECT -->Build Settings.
Step 1: Target--> In Build settings-->Header search path-->press return(enter) key--->replace /usr/include/libxml2
Step 2: Target--> In Build phase--> confirm it whether "libxml2.dylib" framework is present, if not added
Step 3: Target--> In Build phase--> search libxml2.dylib then click add button
Refer Screenshot: