build results window does not scroll properly
build results window does not scroll properly
- Subject: build results window does not scroll properly
- From: "Jeremy Todd" <email@hidden>
- Date: Thu, 28 Sep 2006 17:10:07 -0400
Hi there,
I've noticed a strange difference between Xcode 2.3 on PPC and Intel-based
macs. On Intel-based macs, the build results don't seem to scroll. Instead,
I see only the lines corresponding to the current build step (e.g.
"compiling x.cpp") and previous build steps which have resulted in warnings
or errors. On PPC builds of Xcode 2.3 the build results seem to scroll so I
can see the entire history of what was built.
I find the PPC behavior much more useful. Does anyone know whether this is a
bug in Xcode or whether it's configurable?
Apologies if this has been covered before on this list. I did search for it
and was surprised when I didn't find any mention of it.
Thanks,
Jeremy Todd
iZotope, Inc.
> -----Original Message-----
> From: xcode-users-bounces+jeremy=email@hidden
> [mailto:xcode-users-bounces+jeremy=email@hidden
> ] On Behalf Of email@hidden
> Sent: Thursday, September 28, 2006 3:07 PM
> To: email@hidden
> Subject: Xcode-users Digest, Vol 3, Issue 644
>
> Send Xcode-users mailing list submissions to
> email@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.apple.com/mailman/listinfo/xcode-users
> or, via email, send a message with subject or body 'help' to
> email@hidden
>
> You can reach the person managing the list at
> email@hidden
>
> When replying, please edit your Subject line so it is more
> specific than "Re: Contents of Xcode-users digest..."
>
>
> Today's Topics:
>
> 1. Xcode gets confused on dependencies (Mark Munz)
> 2. forcing a certain framework version (Stefan Werner)
> 3. Re: Cross-SDK CGImageCreate (Kevin Meaney)
> 4. Applescript to find source file in projects (Eric)
> 5. Problem with Xcode linker flags (Wade Williams)
> 6. Re: Problem with Xcode linker flags (Nick Zitzmann)
> 7. Re: Applescript to find source file in projects (Scott Tooker)
> 8. DWARF and gcc 3.3? (Dave Thorup)
> 9. Re: DWARF and gcc 3.3? (Syd Polk)
> 10. 2.3 static library in 2.4 project (Milton Sagen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Sep 2006 13:31:24 -0700
> From: "Mark Munz" <email@hidden>
> Subject: Xcode gets confused on dependencies
> To: email@hidden
> Message-ID:
> <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I recently renamed one of the folders containing several
> projects and one of the subprojects is always complaining
> that it can't find the .xcconfig file specified (with the
> path pointing to the old location).
>
> This happens despite the fact that .xcconfig file is in the
> project and is found w/o issue.
>
> The transcript gives no information. I've tried cleaning the
> project, deleting the build directory, but that doesn't help.
>
> How can I get Xcode to rebuild its dependencies?
>
> Thanks.
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 27 Sep 2006 15:50:31 -0700
> From: Stefan Werner <email@hidden>
> Subject: forcing a certain framework version
> To: Xcode Users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Hi,
>
> I'm having a case where my universal build is linking the PPC
> side against a different framework version as the i386
> version. In detail, I have Python 2.4.3 installed in
> /Library/Frameworks/Python.framework
> and want both the PPC and i386 parts to use it. However,
> Xcode passes only "-framework Python" to gcc/ld, and it seems
> that the PPC half of the build doesn't see the same as the
> i386 half - probably due to the fact that PPC sees a
> different SDKROOT in order to be compatible with 10.3.9. The
> effect is that the PPC part of the UB links against Python
> 2.3.5 in /System/Library/Frameworks (the Python distribution
> that Apple ships with OS X) and and the i386 part links
> against Python 2.4.3 in /Library/Frameworks.
>
> How can I force Xcode to use a specific version of a
> framework, namely the version I have in /Library/Frameworks?
>
> Thanks,
> Stefan
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 28 Sep 2006 13:53:49 +0100
> From: "Kevin Meaney" <email@hidden>
> Subject: Re: Cross-SDK CGImageCreate
> To: "Xcode Users" <email@hidden>
> Message-ID: <email@hidden.1>
> Content-Type: text/plain; charset=US-ASCII
>
> On Oct 9, 2005, at 22:34, Eric Albert wrote:
> >On Oct 8, 2005, at 3:02 PM, David Dunham wrote:
> >
> >> If I want my code to run on Intel, I need to use
> >> kCGBitmapByteOrder32Host. This constant doesn't exist
> prior to 10.4,
> >> and I need to run on 10.2. So my first thought was simply
> to define it.
> >> But that doesn't work, since the argument of CGImageCreate has
> >> changed in 10.4 -- > it used to be CGImageAlphaInfo, and is now
> >> CGBitmapInfo.
> >
> >Both CGImageAlphaInfo and CGBitmapInfo are 32-bit values (at
> least as
> >far as the calling convention is concerned), so I'm a bit
> confused as
> >to how the change is causing any trouble here. Can you
> explain that a bit?
> >
> >Clearly it's runtime-compatible. But CodeWarrior at least considers
> >them different types and complains. (I can't use Xcode for
> this because
> >of some [filed] bugs, though the header file is different no matter
> >what IDE I'd use.)
> >
> >I don't doubt you that CodeWarrior's complaining here, but
> given that
> >CodeWarrior can't build for Intel I'm a bit perplexed as to
> how you're
> >hitting this.
> >
> >Regardless, one simple workaround would be to only use that constant
> >under #if __LITTLE_ENDIAN__. That'll never be defined when
> building in
> >CodeWarrior.
> >
> >-Eric
>
> I have a similar problem related to the above. In Xcode if I
> leave our function calls to CGBitmapContextCreate to take a
> CGImageAlphaInfo then I get link errors when building our
> spotlight plugin, the link errors go when the parameter type
> is CGBitmapInfo. When building our application we don't get
> the link error if CGImageAlphaInfo is the parameter type and
> the only relevant build setting that is different is Generate
> Position Dependent Code.
>
> Currently we are using Xcode to do the intel build of our
> application and to build the intel and ppc for our spotlight
> plugin. We still use Codewarrior to build our application for
> ppc, compiling on both 10.3 and 10.4.
>
> Since Codewarrior gets used on both 10.3 and 10.4 it builds
> against the
> 10.3 and 10.4 headers. But when building on 10.3 the
> CGBitmapInfo type is not defined and we get compile errors.
> I've been hunting around in the header files to try and find
> a macro that specifies the frameworks sdk version that I can
> check against so that CGBitmapInfo can be defined when
> necessary. I have had no luck.
>
> Searching the internet provided me only with the above post
> to xcode-users.
>
> Kevin
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 28 Sep 2006 10:35:01 -0400
> From: Eric <email@hidden>
> Subject: Applescript to find source file in projects
> To: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I'm assuming this is possible, useful and/or has already been
> done by someone.
>
> I have large project tree with many xcode project files. I
> need to know which project file(s) are compiling a source
> file (x.cpp). Has anyone written an Applescript that is
> capable of recursively searching folders for xcode project
> files and then determine whether or not that project file is
> referencing a .cpp file?
>
> If this has not been done before, any hints or tips on how
> such an Applescript could be written would be helpful.
>
> Thanks.
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 28 Sep 2006 09:40:38 -0500
> From: Wade Williams <email@hidden>
> Subject: Problem with Xcode linker flags
> To: xcode-users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> I'm linking to a libz.a of my own making.
>
> One the command-line, to prevent linking with the system
> libz.dylib, I use -Xlinker --search_paths_first in LDFLAGS.
>
> However, in XCode, I've been unable to get that option passed
> to the linker.
>
> I've tried:
>
> Other CFlags and Other C++ Flags = -Xlinker -search_paths_first
>
> and
>
> Other linker flags = -search_paths_first (and -Xlinker -
> search_paths_first for good measure)
>
> In none of the cases above do I see the -search_paths_first
> option passed to the linker.
>
> Any thoughts?
>
> Using XCode 2.4 on 10.4.7 ppc.
>
> Wade
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 28 Sep 2006 09:30:29 -0600
> From: Nick Zitzmann <email@hidden>
> Subject: Re: Problem with Xcode linker flags
> To: Wade Williams <email@hidden>
> Cc: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Sep 28, 2006, at 8:40 AM, Wade Williams wrote:
>
> > I'm linking to a libz.a of my own making.
>
> Is there any reason why you can't rename the file to
> "libmyz.a" or something similar? I think that ought to work,
> as long as you know what it does...
>
> Nick Zitzmann
> <http://seiryu.home.comcast.net/>
> S/MIME signature available upon request
>
>
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 28 Sep 2006 09:46:17 -0700
> From: Scott Tooker <email@hidden>
> Subject: Re: Applescript to find source file in projects
> To: Xcode Users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Try something like this:
>
> tell application "Xcode"
>
> get project relative path of file references of front
> project whose file kind contains "sourcecode"
>
> end tell
>
> This will list project relative paths for all file references
> in the project that have a file type that contains "sourcecode".
>
> Note that "file references of project" returns a flat list of
> all file references in the project (not crossing
> cross-project boundaries).
> Also the "file type" returns the file type identifier used in
> Xcode to type files (for example "sourcecode.c.h"). You can
> check out the "File Types" prefs pane for a full list of the
> file types that Xcode understands.
>
> Scott
>
> On Sep 28, 2006, at 7:35 AM, Eric wrote:
>
> > I'm assuming this is possible, useful and/or has already
> been done by
> > someone.
> >
> > I have large project tree with many xcode project files. I need to
> > know which project file(s) are compiling a source file (x.cpp). Has
> > anyone written an Applescript that is capable of
> recursively searching
> > folders for xcode project files and then determine whether
> or not that
> > project file is referencing a .cpp file?
> >
> > If this has not been done before, any hints or tips on how such an
> > Applescript could be written would be helpful.
> >
> > Thanks.
> >
> > _______________________________________________
> > 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
>
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 28 Sep 2006 14:13:33 -0400
> From: Dave Thorup <email@hidden>
> Subject: DWARF and gcc 3.3?
> To: Xcode Users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset="us-ascii"
>
> Is there DWARF support when building with gcc 3.3? Or is it
> a gcc 4.x only thing?
>
> It looks like DWARF is not supported for gcc 3.3, but the
> release notes I found were for Xcode 2.1. What's the official word?
>
> Thanks!
> _____________________________
>
> Dave Thorup
> Software Engineer
> email@hidden
>
> http://www.kuwan.net
> HyperSpell - Check spelling in Mac OS X from any application.
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.apple.com/pipermail/xcode-users/attachments/20060
> 928/55654527/attachment.html
>
> ------------------------------
>
> Message: 9
> Date: Thu, 28 Sep 2006 13:18:48 -0500
> From: Syd Polk <email@hidden>
> Subject: Re: DWARF and gcc 3.3?
> To: Dave Thorup <email@hidden>
> Cc: Xcode Users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Sep 28, 2006, at 1:13 PM, Dave Thorup wrote:
>
> > Is there DWARF support when building with gcc 3.3? Or is
> it a gcc 4.x
> > only thing?
> >
> > It looks like DWARF is not supported for gcc 3.3, but the release
> > notes I found were for Xcode 2.1. What's the official word?
> >
>
> I don't speak for Apple, but I do know that DWARF is not supported
> for gcc 3.3. If you wish to only use command line tools, you could
> probably get gcc and gdb to handle DWARF, but you would probably run
> into hurdles with the linker, which means for all practical
> purposes,
> you can't use DWARF with gcc 3.3.
>
> gcc 3.3 has not had any substantial work on it since 10.3.0 shipped
> in late 2002; any new features that Xcode has that involves the
> compiler since that time will not be reflected in gcc 3.3.
>
>
> Syd Polk
> email@hidden
> "Let the music be your light" - Dave Edwards, KUHF-FM, 1982
>
>
>
>
> ------------------------------
>
> Message: 10
> Date: Thu, 28 Sep 2006 11:51:34 -0700
> From: Milton Sagen <email@hidden>
> Subject: 2.3 static library in 2.4 project
> To: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> I'm using 2.4 Xcode and a project that links in a static library
> created with 2.3 Xcode, or tries to. The linker returns the error
> message
>
> [path of library].a bad magic number (not a Mach-O file)
>
> If I rebuild the library with 2.4 no problems. Did something change
> from 2.3 to 2.4? I looked through the release notes and didn't see
> anything so I'm wondering if I have something else not quite
> right in
> my 2.4 project.
>
> The 2.3 library isn't completely in my control so I can't simply
> rebuild it and I don't want to have to step back to 2.3.
>
> Milt
>
>
> ------------------------------
>
> _______________________________________________
> Xcode-users mailing list
> email@hidden
> http://lists.apple.com/mailman/listinfo/xcode-users
>
> End of Xcode-users Digest, Vol 3, Issue 644
> *******************************************
>
_______________________________________________
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