Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS Just start with Xcode 4.3

B

benthicwhale

macrumors newbie
Original poster
Jul 30, 2011
10
0
Hi, guys I just begin learning how to program in Xcode 4.3. And I am attending class of C program in university, so I use Xcode Command Line to run some simple C programs.

My operation is as follows: Run Xcode 4.3 - Create a new Xcode project -
Application (under 'Mac OS X' menu) - Command Line Tool. Then I copied content of *.c to Main.c in the new project, and then build and run in Main.c.

My question is, when I add a new .c file to this project, I can not build Main.c successfully. what should I do to add new .c files associated with Main.c into the project?

Please help me, thank you very much! :confused:
 
Unless you have a super awesome access to Apple internally released code, you can't have XCode 4.3. ;) You might want to check again was version of XCode you actually have.

What error messages are you getting in Main.c when you add other .c files to your project?
 
Ok, thank you for your reply, maybe it is not version of 4.3, but should be 4.*. When I added another .c file to my project, I just could not build successfully my project, always built failed.

My question is how to associate another .c file with main.c?

Thank you very much.
 
Is this a new game show? How much do I win for guessing the answer correctly?
 
ehoui said:
Is this a new game show? How much do I win for guessing the answer correctly?
Click to expand...

his question is a very straight forward one?


To include a file to the main you use something like this

Code: 
#include "stack.h"
<-stack.h holds all the prototypes for stack.c which gets called from stack.h thru main.c

ask me here if you need more help!


Happy coding =)
 
kingofqueens said:
his question is a very straight forward one?


To include a file to the main you use something like this

Code: 
#include "stack.h"
<-stack.h holds all the prototypes for stack.c which gets called from stack.h thru main.c

ask me here if you need more help!


Happy coding =)
Click to expand...

Yeah, your assumption is right, that is my straightforward question. Create a new project, then there will be a 'main.c' in the project. I want to add another 3 '.c' files into this project. But after adding another one .c file in the project. I can not build for running successfully. Even though I add '#include <name.c> in main.c. I still built failed.

Because one project can only have one main function. So I need to change the name of main() in other .c files(except main.c). And then invoke this function in main.c. Is that right？

But after I adding a new .c file into the project, such as name1.c, and including this name1.c in main.c by '#include <name1.c>', I received a error message of 'name1.c file not found'. Why?
 
Last edited by a moderator:
benthicwhale said:
Yeah, your assumption is right, that is my straightforward question. Create a new project, then there will be a 'main.c' in the project. I want to add another 3 '.c' files into this project. But after adding another one .c file in the project. I can not build for running successfully. Even though I add '#include <name.c> in main.c. I still built failed.

Because one project can only have one main function. So I need to change the name of main() in other .c files(except main.c). And then invoke this function in main.c. Is that right？

But after I adding a new .c file into the project, such as name1.c, and including this name1.c in main.c by '#include <name1.c>', I received a error message of 'name1.c file not found'. Why?
Click to expand...

Firstly, typically you don't #include .c files. Typically you #include .h files. Header files (.h files) only include a declaration/prototype of the functions defined in the corresponding .c file. If you #include a .c file and that .c file is also in your project, you will get duplicate symbol errors when your program is linked because both the included .c file and including .c file will end up having the same code. You'll want to create a header file for each .c file except for the one containing main. You don't need to create declarations for all the functions, just the opens you want call from other .c files.

Secondly, you want to #include "name1.h" (with double-quotes) not #include <name1.h> (with angle-brackets). The former is used to include header files local to your project. The later is used to include header files from the library header search path (typically /usr/include).
 
Thank you very much, jiminaus, for your kind and patience. My question is quite simple, because I am a Xcode beginner. Now I have figured out the solution of my own question. I share it with our friends in MacRumors.

First, I must clarify that it is not version 4.3, it's 4.1.

Then essence of my question is that Xcode can not find customised files no matter .h file or .c file in my SSD. The reason of it is that we indeed need to set some options in the Xcode Project Setting.

Do it as follows: Select my project name (such as Lab_02 1target, Mac OS X SDK 10.7) - then a middle list will appear with two options of 'PROJECT' and 'TARGETS' - choose one of them arbitrarily - on the right list where you can see 'info' and 'Build Settings' buttons in the top menu, choose 'Build Setting' button - a submenu appears under the top menu - confirm that 'ALL' and ' Combined' options are highlighted ( Default setting is 'Basic' ) - in the Setting list, find 'Search Paths' - build 'Always Search User Paths' to 'yes' ( default is no ) - Add a path to 'Header Search Paths' ( Such as: /Users/benthicwhale/Documents/Xcode_Projects/Header_Files). I should make sure that there is no blank space in this path!! - Then back to my main.c build for running again to see whether Xcode has found this .h file according to the new search path.

Hope this solution can help you with your Xcode career.

Thank everyone who replied my question!
 
benthicwhale said:
Thank you very much, jiminaus, for your kind and patience. My question is quite simple, because I am a Xcode beginner. Now I have figured out the solution of my own question. I share it with our friends in MacRumors.

First, I must clarify that it is not version 4.3, it's 4.1.

Then essence of my question is that Xcode can not find customised files no matter .h file or .c file in my SSD. The reason of it is that we indeed need to set some options in the Xcode Project Setting.

Do it as follows: Select my project name (such as Lab_02 1target, Mac OS X SDK 10.7) - then a middle list will appear with two options of 'PROJECT' and 'TARGETS' - choose one of them arbitrarily - on the right list where you can see 'info' and 'Build Settings' buttons in the top menu, choose 'Build Setting' button - a submenu appears under the top menu - confirm that 'ALL' and ' Combined' options are highlighted ( Default setting is 'Basic' ) - in the Setting list, find 'Search Paths' - build 'Always Search User Paths' to 'yes' ( default is no ) - Add a path to 'Header Search Paths' ( Such as: /Users/benthicwhale/Documents/Xcode_Projects/Header_Files). I should make sure that there is no blank space in this path!! - Then back to my main.c build for running again to see whether Xcode has found this .h file according to the new search path.

Hope this solution can help you with your Xcode career.

Thank everyone who replied my question!
Click to expand...

If you had of used #include "abc.h" instead of #include <abc.h> you wouldn't have had to do this.
 
Just FWIW this is not an Xcode problem. It is a C problem.

benthicwhale, you might want to consider learning C independent of the IDE by using gcc/clang from the command line instead. This gets the IDE out of the way and may be closer to what your class does.

Are they using Linux or Windows in class?

B
 
jiminaus said:
If you had of used #include "abc.h" instead of #include <abc.h> you wouldn't have had to do this.
Click to expand...

Thank you, you are right, with "include" I just need to add reference of .h or .c files into my project, then everything works smoothly.

Thank you again.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back