• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
(no subject)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)


  • Subject: (no subject)
  • From: Aaron koolen <email@hidden>
  • Date: Thu, 16 Feb 2006 23:48:16 +1300

Hi all. New to XCode and Mac programming as a whole, and after struggling with XCode tonight for a few hours, I'm going insane so thought I'd ask. Bare with me as I have a few questions...

I'm starting to develop an application that has:

1) The main App (Duh) - lets call it App
2) Dynamic libraries that this main app loads (Maybe 5-6 of them)
3) Static libraries that the Dynamic libraries use (String manipulation, core file functions etc etc etc - could be half a dozen of those too by the end)


Now coming from the Windows Visual C world, I first thought I'd be better off making a project for each of these things and then somehow linking them together so that when I build App, it builds the others as well. Well this just didn't work. If I changed a source file in the statlib project, it wouldn't compile the dynamic lib or App.

Question one is - Can it be done this way, and is it the best way to do a project like this?

Question two - is there any sort of 'Solution' concept in XCode like there is in Visual C?


Then I was reading through the docs and it seemed to suggest that a better way is to have one project for the entire thing, and make targets for the dynamic lib, and static lib. So I fiddled with this, made targets, made dynamic lib depend on static lib, and App depend on dynamic lib, so that a change in one would build the others.


Then when I went to put source files in there I made directories for each static and dynamic library, within the same directory that the project resides, and groups within the project for those, added them to the project, attached them to the specific targets. BUT...When I try and include a static lib header file into, say the dynamic lib source file (%projectdir%/dylib/source.cpp lets say). There is no way it can be found unless I go "../StatLib/source.h"

Now I hate the idea of relative pathing inside of source files and in Visual C you just set some sort of header search path for the "Project" (Root of all directories) and away we go. But there doesn't seem to be a way to do it in XCode.

Question three - Is there a way, and how do I do it?

Well sorry for the long winded info, but hope someone can help me out here. I feel like I did 20 years ago when I was first learning to program.
Aaron


_______________________________________________
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


  • Follow-Ups:
    • Re: Beginner Questions (was no subject)
      • From: Daniel Jalkut <email@hidden>
  • Prev by Date: libtool -static vs. ranlib
  • Next by Date: Deprecated warnings for OT
  • Previous by thread: libtool -static vs. ranlib
  • Next by thread: Re: Beginner Questions (was no subject)
  • Index(es):
    • Date
    • Thread