New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installXcodebuild incompatible with Xcode 3.0 #1

Closed
macosforgebot opened this Issue Nov 13, 2007 · 10 comments

Comments

Projects
None yet
1 participant
@macosforgebot

macosforgebot commented Nov 13, 2007

BHuntsman@… originally submitted this as ticket:1

  • Owner: wsiegrist@…
  • Keywords: xcode

The installXcodebuild script does not properly determine the dependencies of Xcode 3.0's xcodebuild script. This prevents darwinbuild from being used to compile projects that require Xcode 3.0 while using the chrooted environment.

Attached is a logfile from an initial run of xcodebuild while using the darwintrace.dylib library, indicating most preliminary dependencies.

@macosforgebot

This comment has been minimized.

macosforgebot commented Nov 13, 2007

BHuntsman@… originally submitted this as attachment:xctrace.txt:⁠ticket:1


xcodebuild trace log from Xcode 3.0

@macosforgebot

This comment has been minimized.

macosforgebot commented Nov 19, 2007

BHuntsman@… originally submitted this as attachment:xc-files.txt:⁠ticket:1


darwinxref exportFiles xcodebuild > xc-files.txt

@macosforgebot

This comment has been minimized.

macosforgebot commented Nov 19, 2007

BHuntsman@… originally submitted this as comment:1:⁠ticket:1


Replying to BHuntsman@mail2.cu-portland.edu:

The installXcodebuild script does not properly determine the dependencies of Xcode 3.0's xcodebuild script. This prevents darwinbuild from being used to compile projects that require Xcode 3.0 while using the chrooted environment.

Attached is a logfile from an initial run of xcodebuild while using the darwintrace.dylib library, indicating most preliminary dependencies.

Please see the file list in the attached xc-files.txt. Instead of using a script to find dependencies and put them into the BuildRoot, I used the dependency list to generate a binary source package, then built and installed it as it's own root. This way, the xref database can track the files in it. I have confirmed it to work by building the files-520 project, which requires xcodebuild.

@macosforgebot

This comment has been minimized.

macosforgebot commented Nov 19, 2007

BHuntsman@… originally submitted this as comment:2:⁠ticket:1


Replying to BHuntsman@mail2.cu-portland.edu:

Replying to BHuntsman@mail2.cu-portland.edu:

The installXcodebuild script does not properly determine the dependencies of Xcode 3.0's xcodebuild script. This prevents darwinbuild from being used to compile projects that require Xcode 3.0 while using the chrooted environment.

Attached is a logfile from an initial run of xcodebuild while using the darwintrace.dylib library, indicating most preliminary dependencies.

Please see the file list in the attached xc-files.txt. Instead of using a script to find dependencies and put them into the BuildRoot, I used the dependency list to generate a binary source package, then built and installed it as it's own root. This way, the xref database can track the files in it. I have confirmed it to work by building the files-520 project, which requires xcodebuild.

This only works for files-520. A more complicated project such as IOKitUser still requires others. See attachment 3.

@macosforgebot

This comment has been minimized.

macosforgebot commented Nov 19, 2007

BHuntsman@… originally submitted this as attachment:3.txt:⁠ticket:1

  • Attachment 3.txt (496 bytes) added

Additional dependencies

@macosforgebot

This comment has been minimized.

macosforgebot commented Apr 24, 2008

wsiegrist@… originally submitted this as comment:3:⁠ticket:1

  • Owner changed from @kvanvechten to wsiegrist@…
  • Status changed from new to assigned

Initial work on this is in r367. See this email for more details.

@macosforgebot

This comment has been minimized.

macosforgebot commented May 17, 2008

wsiegrist@… originally submitted this as comment:4:⁠ticket:1


You can work around this issue by building on a UFS volume. I believe any volume that doesnt support volfs will work. I'm still working on a more permanent fix of course.

@macosforgebot

This comment has been minimized.

macosforgebot commented Sep 17, 2008

wsiegrist@… originally submitted this as comment:5:⁠ticket:1


The problem still exists with Xcode 3.1, though it will probably complain about missing a product type in the platform instead of a missing project file.

@macosforgebot

This comment has been minimized.

macosforgebot commented Sep 27, 2008

wsiegrist@… originally submitted this as comment:6:⁠ticket:1

  • Status changed from assigned to closed
  • Resolution set to fixed

I'm closing this ticket since the dependency issues are fixed. The problem with running Xcode inside of a chroot on HFS is an Xcode bug and has been reported to Apple . The workaround is still to use a UFS disk for building.

@macosforgebot

This comment has been minimized.

macosforgebot commented Nov 9, 2008

probono@… originally submitted this as comment:7:⁠ticket:1


Exporting the directory to localhost over NFS and mounting that export locally seems to be a workaround. See here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment