• 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
Re: Files still dirty after build
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Files still dirty after build


  • Subject: Re: Files still dirty after build
  • From: Jim Ingham <email@hidden>
  • Date: Wed, 29 Sep 2004 12:01:59 -0700

Regardless of whether this arrangement is normal practice or not, the build behavior is still clearly either an Xcode bug or something messed up in this project. It should make no difference where you put your source files relative to your headers as long as the Xcode can find them.

I tried just making a simple project, adding source & headers directories to the project, and using File->New File... to make a new .c file, and then a new .h file in the respective directories. The build system did what it should, and only rebuilt the source file when something had actually changed. So there's a little more going on than just sources in one directory, headers in another...

Trygve, if you can reduce your project to some small example that shows this happening, please file a bug with the project.

Jim

On Sep 29, 2004, at 11:45 AM, Carl Norum wrote:



Have you really never seen such a thing before? Almost every linux package source I've downloaded for my current project is arranged with a separate include directory containing all the headers.

-- Carl J Norum
Design Engineer
VCom Electronics
Saskatoon, Canada

http://norum.homeunix.net/~carl/


On Sep 29, 2004, at 12:21 PM, Bryan Pietrzak wrote:


On Sep 29, 2004, at 4:18 AM, Trygve Inda wrote:

On my hard drive:

Project/headers/myapp.h
Project/sources/myapp.c

Why does Xcode force me to arrange my source and header files all in the
same folder? It makes things less organized.

In 15 years of programming I'm not sure I've ever seen anyone arrange their source that way. Separating the header from a source file by putting in a different directory is a very very odd practice.


This may just be a case that you're using a workflow that no one has even thought of testing. You may just be trying to swim upriver.

Bryan

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40usask.ca


This email sent to email@hidden


_______________________________________________ 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
_______________________________________________
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: Files still dirty after build
      • From: Trygve Inda <email@hidden>
References: 
 >Files still dirty after build (From: Trygve Inda <email@hidden>)
 >Re: Files still dirty after build (From: Bryan Pietrzak <email@hidden>)
 >Re: Files still dirty after build (From: Carl Norum <email@hidden>)

  • Prev by Date: Re: Files still dirty after build
  • Next by Date: Re: Unicode in XCode?
  • Previous by thread: Re: Files still dirty after build
  • Next by thread: Re: Files still dirty after build
  • Index(es):
    • Date
    • Thread