Can't build: "An unknown error has occurred"

Question

Pomo OP

Created Oct ’15

Replies 3

Boosts 0

Views 5.4k

Participants 3

Hello all,

Honestly, I've exhausted all my ideas and strategies, so hoping someone can help.

- I have a project, a FileMaker plug-in written in C++. It builds fine in OS 10.6.8/Xcode 3.2. This plug-in is a utimately a package with a shared library inside.

- I need to test and debug in OS 10.10. The project opens in Xcode 6.4. However, the Build For commands are all grayed. Compile puts up the informative modal dialog, "An unknown error has occurred."

- There is no explanation of this error in the Issues tab or Console, which are the only places I know where to look.

- I have gone over the build setting uncountable times and spotted no problems. Changed project format to Xcode 6.3. Renamed project using file pane. Uttered curses and incantations. However, see next.

- I suspect some kind of path configuration issue. However, in Xcode 6, I can no longer see what various paths expand to. When the path is long, the expansion is cut off in a short field, boxed in by various panes, and ultimatey by the width of my screen. There is no way to make the field wide enough to view it. Furthermore, some paths are in a light gray small font that my weak eyes can read only if I stick my nose on the screen. This is a major usability problem - is there any solution or workaround for seeing path expansions and darkening these fields?

- I have tried making a brand new Generic C++ Plug-in project from the template, and editing it to match the existing project, transferring settings and files a few at at time. Suffice it to say at this point, without success. The error messages generated are incomprehensible; my guess is that the errors are a result of incorrect search paths and setting expansions that I cannot see in order to diagnose. For example,

Check dependencies

Argument list too long: recursive header expansion failed at /Applications/Wolfram CDF Player.app/Contents/SystemFiles/Components/NaturalLanguageProcessing/Resources/WLTagger.

Of course, this project has no relationship to a random item that happens to be in the Applications folder.

Any help will be very much appreciated.

Doug

Boost

Answer 1

bob133 OP

Oct ’15

Did you make 100% sure that you weren't importing a stray header? Just asking…

0

Answer 2

Pomo OP

Oct ’15

I assume you mean as part of the second try (making a fresh project)? I guess I'd need to know what you mean by a "stray header", where it would be, and how it would produce the symptoms.

To be clear, Xcode is not getting even to the preprocessor stage, AFAICT; that's where I would expect to get header errorrs. The error may well be related to headers, though, at some earlier stage of the build. But the essential problem is I can't find any diagnostic output that tells me exactly what and where the problem is.

These would be helpful for me to diagnose the problems:

1) Point me to a place in Xcode (or Console, or anywhere) that give more information about the error (a command passed to a tool, what setting or action is the cause, or anything).

2) Show me a way to see Xcode's expansions of paths in Build Settings, that is, a long enough field and one not in light gray. Then I might be able to observe the cause of the problem.

Thanks for any help or ideas.

0

Answer 3

LittleOS OP

Oct ’15

Maybe this is too simple minded an approach - but one may want to give it a try.

1. If you haven't done so already, udate your development system to OSX 10.10.5 and Xcode to released version Xcode 7.0.1.

2. Open your old code in this Xcode.

3. Xcode > Edit > Convert > To Latest Swift syntax

let it guide through the suggested fixes

4. proceed to build/debug etc.

I would recommend you disbandon Xcode 6.x because it is known to have bugs that are fixed in Xcode 7.0.1.

Also, Apple has stated that Xcode 6.x will not function correctly under El Capitaine.

One can select what the target is, and test on the widest variety of Simulators.

Let me know if this helps...

Cheers

0