Composer and Xcode build rules

[kep]

I have searched on this but found no answer. I do apologize if it is there and I missed it.

I use Xcode 3.2.5 on MacOSX 10.6.6. I recently installed Intel Fortran Compiler XE 12.0. My question is simple. When I set up a project and add a target I look at the Build Rules and find the Fortran rule for XE 12.0 as a default rule. But why are there four copies of the XE 12.0 build rule listed? I know that the presence of the extra copies should not affect anything, but why the extras? I have looked for a cause and found no clue. I have duplicated and renamed the .xspec for XE 12.0 and that resulted in even greater confusion.

Since this curiosity probably does not affect anything, feel free to say so and not waste anyone's time on it. Does anyone else see this behavior?

[Jeffrey_A_Intel]

I can reproduce this with Mac OS X 10.6.6, Xcode 3.2.5 and ifort Version 12.0.2.142 Build 20110112. I see four "Default Fortran rule" entries for each Intel Fortran compiler I have installed. (That's 8 entries; lots of clutter!) No idea why (yet).

I don't have any earlier versions of Xcode installed. Do you happen to know if this "feature" is new with Xcode 3.2.5 or have you seen if before? I don't recall having seen it with Xcode 3.2.2.

[kep]

I do not recall having seen it before. I have had more than one ifort version and do remember seeing a rule for each version. But it now, since installing Composer, gets really odd when more than one version is present. Some are repeated, some are not. I do not see how Xcode itself is the problem since it does not do this with other languages. (I do not have Intel C installed so I don't know whether it is Intel related).

[Jeffrey_A_Intel]

I do not see how Xcode itself is the problem since it does not do this with other languages.

But the files which "tell" Xcode about the Intel 11.1 Fortran compiler are the same for all releases of Xcode 3.2.*. Thus, if this didn't happen for versions previous to Xcode 3.2.5, something probably changed in Xcode. It could be a bug introduced in Xcode 3.2.5; it could be Apple fixed something in Xcode 3.2.5 which now exposes a bug in our 11.1 Fortran .xcspec package. Dunno yet.

Xcode is quite fragile and unforgiving when it comes to non-C/C++ third-party compilers.

[kep]

I agree.

I do not have enough evidence or remembrance of my past setups. But I am fairly certain that there were not four entry repeats with earlier Xcode and/or Intel Fortran (I only noticed the problem when I checked to see the new rules after installing my new Composer version recently, after Xcode 3.2.5).

To elaborate on my original post:

One test I tried was to add an '_2' to the end of the name of a copy of the IFORT .xcspec file so that there were two such files present: the original, and one with a slightly different name (I think I even edited the rule name within said copy). The rules listed then have repeats but seem scrambled as well.

This is just a curiosity to me. Compiling and linking are working as usual.

[Jeffrey_A_Intel]

I've checked what happens with Xcode 3.2.2 and Xcode 3.1.3. They both exhibit the "there are four Build Rules entries for each Fortran compiler installed" behavior. Strange that I and no one else seems not to have noticed this before. There are still more combinations which could be tested (e.g., does it require Mac OS X 10.6.6? Does it only happen if Xcode 4.0 is installed).

I think now it's probably more important to figure why it's happening rather than when it started to happen.

[kep]

And I agree on this too. I will continue to use Xcode and the fortran compiler as it is. My version of Xcode is 3.2.5. I have not installed the developer preview of 4.0 so the answer to your last question is no. I think you meant to ask "does it also happen with Xcode 4.0?).

[Jeffrey_A_Intel]

No, I meant what I wrote: is the problem correlated with the presence of Xcode 4.0. Your experience says it's not since you see the problem but don't have Xcode 4.0 installed.