OK,
Here's the output from the Log Navigator, showing how includes are being
stacked. I've placed it at:
https://dl.dropboxusercontent.com/u/29578720/Build%20log.rtf
I noted the references to wxAny, which I was using for handling variants,
but I've now replaced this with boost::any and I'm not including wxAny in
any of my modules, despite the log seeming to implicate this class. Again,
the new version of the code builds fine using VS2010, but fails using Xcode.
Best wishes.
Tim Burgess
-----Original Message-----
From: Steve Ramsey [mailto:steve@lucena.com]
Sent: 18 November 2013 18:59
To: tim@raisedbar.net
Subject: Re: [boost] decay.hpp - anonymous enum problem
On Nov 18, 2013, at 7:37 AM, Tim Burgess
I'm pretty much a newbie when it comes to Xcode, so I've no idea how to get you that trace - the Issue Navigator gives me no clues as to what's including/calling decay.hpp. Any clues/links to reading materials would be most welcome.
I find the Log Navigator using the Assistant editor pane to be more flexible than the Issue Navigator when dealing with failed build detritus. So, from the Log Navigator, select your failed build. In the editor pane, you'll find an expandable list of build issues broken down by file. On the far right side of each file-level entry, there is a "show transcript" widget; popup text shows the internal command that was issued for the file and when it was issued. Clicking the widget will show a complete dump of the compiler/linker output for that particular command. It's also possible to right-click on any given issue entry and copy the transcript for either just the current issue or for the entire filtered list of issues. Steve