• 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: Problem Debugging GNU Make Projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem Debugging GNU Make Projects


  • Subject: Re: Problem Debugging GNU Make Projects
  • From: Rob Frohne <email@hidden>
  • Date: Fri, 28 Jan 2005 08:38:09 -0800
  • Resent-date: Fri, 28 Jan 2005 08:49:40 -0800
  • Resent-from: Rob Frohne <email@hidden>
  • Resent-message-id: <email@hidden>
  • Resent-to: email@hidden

Hi Tony,

I don't have any good answer for you. I am hoping someone else will pipe up with the real solution. Mine has been to take the time and convert the project to a native Xcode one, which has taken me days sometimes since I'm rather a novice. It is also a pain, because the maintainers of the regular CVS want everything in terms of config and Makefiles, which means you have to convert back again to make commits.

Rob
On Jan 27, 2005, at 3:54 PM, Tony Cebzanov wrote:

I am trying to use Xcode as an editor/debugger for a project which needs to run on a lot of platforms. This means use of automake, autoconf, and libtool for the builds, and use of the GNU Make project type, with an external build target.

Setting the project up, editing files, etc. was easy, but when I got compile warnings/errors, double-clicking on them was not bringing up the offending source files, even though they had been added to the project. After some hard thinking, it occurred to me that Xcode might not be looking for them in the right subdirectory of the project, which has different subdirectories for different parts of the library.

Sure enough, when I created a "flat" project with only one directory, Xcode was able to bring up source files when there were compile warnings/errors.

So, I'm left wondering if there's any way to find debugging happiness in this environment. Creating separate, flat Xcode projects with a single directory each isn't feasible, because there are so many directories, and managing dependencies between projects would be a nightmare. What I'm hoping is that there's some setting, feature, or trick to getting Xcode to be able to know what subdirectory it's in, so that when an external target is building in a subdirectory, it can bring up the relevant source file.

Whew. That's certainly a mouthful, I hope I asked my question clearly. So, is it doable?

Thanks.
-Tony
_______________________________________________
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

--
Rob Frohne, Ph.D., P.E.
E.F. Cross School of Engineering
Walla Walla College
http://www.wwc.edu/~frohro/

_______________________________________________
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


  • Prev by Date: applescript/interface builder anomaly
  • Next by Date: Re: [xcode] Lua syntax support?
  • Previous by thread: Problem Debugging GNU Make Projects
  • Next by thread: Applescripting xcode documentation
  • Index(es):
    • Date
    • Thread