I can't find my Xcode "Source" file

Isn't it in File > Add new file or similar? (don't have Xcode here atm).

 

Maybe you could post a screenshot of what you mean. What source file ? Adding a class to your project is basically just going File->New->New File for a brand new class you're going to write, or File->Add Files to "Project" to get a open file dialog to select your existing files.

 

If you know where the .h and .m files are, you can grab them in Finder and drag them into the Xcode sidebar, whereupon you will get a dialog asking whether you want to copy them. At least, that is how Xcode 3 works. (This is not the same as importing a framework.)

 

You mean the foundation headers ? They should be automatically imported in the templates when you create a new project/class.

 

Let's come to the teaching bit: If you don't know what you are talking about (like asking for "my source file" when you are really looking for a "Apple's header file"), you should give as much information as possible about what you are doing, so that people have a chance of figuring out what you actually want.

And that's not directed at _you_, so just skip it. It is directed at anyone else who needs help _and_ is willing to learn.

 

And I thought I was rough.

A good point really. OP, I made nothing of your quip, but really, you need to realise that teaching is better than giving out answers if you want to learn, not just have other people do your work for you.

 

I don't quite get what you're trying to do here. You're creating a library ? You're writing an Application ? What is your project exactly ?

You don't add your project to existing frameworks, you link against them. Your project is your project, you're going to distribute it seperately from the base frameworks or even other frameworks.

As for your new header files, you have to manually "#import" or "#include" them depending on what parts of your code requires them (other classes/source files).

Maybe again, you could properly define for us what you mean/what you're trying to do so we can actually offer proper guidance here. It's all left to guess work right now as to what you actually mean.

 

How is anyone supposed to know what you are referring to? What you _wrote_ was that you couldn't find your source file. It now looks like you don't have any source files yet (but that is mostly guessing). This is the first time that you used the word "library", so please think about this: How is anyone supposed to know that you are referring to a library if you don't say so?

What about telling us what it is that you want to achieve? What you are doing so far is like asking "should a put my foot on the gas pedal or on the brake pedal"? How am I supposed to know if you don't tell us whether you want the car to accelerate or to slow down?

 

What have you done and tried and what is the exact error message you're getting ?

Adding your own class has been covered, if it's a new class, it's File->New->New File, or File->Add Files to "Project" to get a open file dialog to select your existing files if this class is already written.

This adds it to your project. Nothing else to do, the build settings will automatically reflect your new code. Then you simply #import the proper header file into the code that needs to reference this class.

Let's say your new class is Circle, and you need to reference it from Geometry, you simply #import "Circle.h" in Geometry.h.

There's nothing more to it.

 

And.. we have come full circle.

File > New > New File

 

As KnightWRX said, I think you still have to import your full circle into your geometry.

 

Strictly speaking doing the above makes them part of the project, which means you can make references to them in other source files. But the latter part is not really specific to Xcode.

 

And I'm betting the OP is having problems with the latter part. He's probably trying to import his header with :

Code:

#import <mycustomheader.h>

instead of :

Code:

#import "mycustomheader.h"

Which we would know if the OP had posted screenshots or exact error messages, or even a detailed post about what he's trying to achieve and what he's done up to now.

 

I think, in this case, a picture really is worth a thousand words. How about some screenshots?

 

Then maybe you should go up to your OP, click Edit, Click Go Advanced, and set the title prefix to "Resolved"?

 

It is good etiquette to post the solution to a problem for any other posters searching for similar problems and coming up on your thread.

You got helped, now it's your turn to pass along the help to others. There's nothing to be embarassed about here, we've all made mistakes that seemed so obvious to fix after we've put our finger on the problem but at the time seemed impossible to get working right.

 

Please post code and exact error messages.