I have decided to use the GTK library and I have been messing around with it.
My problem does not lie within C or GTK itself, it all about Eclipse. Even though my applications compile and run with no errors, but Eclipse is constantly telling me that there are problems such as:
GTK_DIALOG_MODAL, GTK_MESSAGE_INFO, GTK_BUTTONS_CLOSE... could not be resolved.
Is there a way to make Eclipse understand what is going on?
I guess Eclipse cannot find GTK's header files. You can tell it where to look for them by adding one or more include directories to the project properties:
Project → Properties → C/C++ General → Paths and Symbols → Includes
This works for Eclipse Indigo and Juno, at least.
Related
i have a question that google couldn't solve. thing is i am currently working in a project with around 15 other people. some of us use eclipse and some use clion. the problem is that clion uses a "CMakeLists.txt" file in which specifies all files to be compiled. Eclipse doesn't use this file, but the ones using clion complain that they have to manually add all .c files created in eclipse in that file in order to compile the project. is there a way to get around this? thanks
I'm importing a C project to Eclipse CDT which has a preinclude header file. I want to know if there's an option to preinclude the file in the projects settings, The projects doesn't compile because of unresolved defines, that needs to be defined in the start.
does anyone encountered this before ?
Yes, I've seen such problems several times.
If your project doesn't compile, you'll have to change the compiler options, since the compiler needs to know about the file. It depends on your compiler, though, since this is not a C feature.
If it is that CDT do not find the files that are "preincluded" by your compiler, then you can fix that by creating build configuration. You do that by clicking on properties/C/C++ Build/Settings/Tool Settings/Cross GCC Compiler/Includes and then add the file you want to be preincluded.
I'm an experienced Java developer, and I'm very familiar with Eclipse. Lately I've been trying to migrate a Texas Instrumental(BLE), IAR C language project, into Eclipse, without using IAR official Eclipse plugin, I just want to use Eclipse as my code browsing IDE, while I learn how things works, and follow up the tutorial, and in the future use Eclipse to develop.
I've been trying for a day now, to migrate the project, but there is something I'm missing something regarding Eclipse C language support.
There are some types defined in an .h file, in project "A", which is referenced in an other .c file in project "B", and Eclipse although it can "go to declaration", it shows a compilation error in project "B".
I've noticed in other cases of the same scenario, that I don't need to point to any of the folders as source folder, as long as the folders are under the project root directory, they are added to the build path of that specific project, and also imported into a project "B" with only referencing the "A" project in the project properties, is this correct?
Also, I've noticed that in the C language both projects could reference each other, without Eclipse troubling me so I assume this is legit, therefore I assume there should be a C language multi-project structural pattern I should follow, where can I find such detailed specification?
Thanks,
Adam Zehavi.
Try this (Common Source Lookup Path preference)
Edit: in my Eclipse CDT Helios, I do like this:
Right click on project > Properties > C/C++ General > Paths And Symbols.
then choose my language (GNU C) and add the folders with the header files that I want to include.
That operation could be done automatically in one step for every configurations (Run/Debug) or just for the active configuration.
I've finally understood that this cannot be done... alas I've worked hard to been able to edit my code in Eclipse while running, debugging, and deploying the program to the Microprocessor via IAR IDE.
Go to Project > Properties > C/C++ General > Paths and Symbols Then click Export Settings... to save the include paths and/or symbol definitions to a file. In your other project, you can then use Import Settings...
I would like to use XCode 4 as IDE for my C program.
I am using few libraries, which are not installed in system paths. Also, I am using external program for building (waf).
So, basically, I need XCode for everything, except building.
But I can't figure out how to tell XCode where my library include files are for it to be able to autocomplete functions and everything from that libraries?
In the build settings for the Target - look for the HEADER_SEARCH_PATHS setting.
Have you added the library headers to the project? You can just add them by reference.
Pardon me if this is a "noob" question, I'm overextending myself a bit with this.
I'm trying to compile a library written in C for use in an iPhone app I'm developing. I can't seem to figure out how to do this, and I've been searching and trying things for hours.
I've tried using an External Build System project, and selecting the folder where the makefile.in.am.mingw are.
I've tried creating a Static Library project and adding the header\source files to the project. Which looked good until I tried to compile and got 260k+ errors.
When I 'cd' to the directory with the makefiles and type 'make' I get:
No targets specified and no makefile found. Stop.
I have no idea how makefiles work, I just want to use the library!
Is there a simple way to do this? If someone could at least point me in the right direction, I would be quite appreciative.
The makefiles you have are for GNU automake (under MINGW by the look of it). Even if you get them working (automake can be tricky, but it is included in Mac OS X's development thankfully), it probably won't help you much in building an iPhone library.
I did this with an existing C library by creating a new framework target in Xcode with the right include settings, etc gleaned from looking at the makefiles. That created a .framework bundle with headers and an iPhone .a library ready to be used by an iPhone project. You could also just import the C source into the iPhone project, and have it compiled in that way which would probably be quicker.