Skip to content
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

Jump to bottom

[SR-2125] Build output uses relative paths #4127

Closed
dabrahams opened this issue Jul 20, 2016 · 1 comment
Closed

[SR-2125] Build output uses relative paths #4127

dabrahams opened this issue Jul 20, 2016 · 1 comment
Labels
bug BuildScript Foundation

Comments

@dabrahams
Copy link

Previous ID SR-2125
Radar None
Original Reporter @dabrahams
Type Bug
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Foundation
Labels Bug, BuildScript
Assignee None
Priority Medium

md5: 246cbfc20f7a958cb4c6ce49e04ae611

Issue Description:

When swift-corelibs-foundation is built as part of invoking Swift’s build script, errors are printed with paths relative to the root of swift-corelibs-foundation. As a result, tools (such as Emacs) can’t jump directly to the error, but—if the programmer is lucky—instead ask the programmer to resolve the path. The build system for swift-corelibs-foundation should be fixed so that filenames are passed to tools with absolute paths.
@spevans
Copy link
Collaborator

spevans commented Feb 10, 2020

With the move to a cmake based build for swift-corelibs-foundation this issue is now fixed and full paths are shown in error messages.

Validated by adding an error then running build-script inside emacs, selecting the error jumps to the correct file / line.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug BuildScript Foundation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dabrahams @spevans