Re: Don't really understand why there are so many settings
Re: Don't really understand why there are so many settings
- Subject: Re: Don't really understand why there are so many settings
- From: "Theodore H. Smith" <email@hidden>
- Date: Sun, 11 Feb 2007 16:25:25 +0000
On 11 Feb 2007, at 02:40, email@hidden wrote:
So why is there so many settings? There's the "ElfData" (top node)
settings, and there's the target settings. And I don't know what's
the difference between them. Does the top node settings display
and alter for both targets or something? Or is it a sort of third
settings place?
The "top node" as you call it is your project settings. These are
taken as the default values for all targets in the project. Each
target has it's own settings, which may override the project
settings (but typically don't by default). Notice that some
settings in your target inspector are bold?
Yep.
Those are the ones that you're overriding in that particular
target. You can remove the override by selecting them and hitting
the delete key - they'll then take the value(s) set in the project
settings.
OK now I get that bit.
Anyhow, my .dylib's not building correctly. This target is
actually Universal Binary which is what I want. But it contains NO
CODE! I dont' get it. Last release this project built fine. Now
the dylib doesn't because I fiddled around with the top node
thinking I was just altering the shell tool.
The dylib file size is 20K. And it should be around 100K. How do I
get it to contain all the source code that is actually compiling?
The best thing to do would be to just roll back to the working
version, from your cvs/svn/whatever repository. You of course are
using a revision control system, right? :)
Nope :)
I never really found I needed it. I do keep external backups but
that's just in the event of total system loss.
Other than that, the only thought I have, based on the settings you
posted, is to make sure your exports.txt exports file actually
contains all the symbols that should be exported. You're using it
in combination with dead code stripping, which means anything not
in your exports.txt file won't be included in your dylib.
Well... it used to work. I only need one root symbol actually. This
is the one function that "Registers" all the other functions. I'm
assuming that because one function refers to the other functions, the
linker should keep them in. Well, it used to work that way. I don't
know if I ever needed exports.txt actually, someone helped me with
the settings before and he used exports.txt so I kept it.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden