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

[WIP] Extend support for reporting of build platform #868

Closed
wants to merge 2 commits into from
Closed

[WIP] Extend support for reporting of build platform #868

wants to merge 2 commits into from

Conversation

landstander668
Copy link

@dscho This is a continuation of the work from PR #866, to hopefully make it easier for you to get the changes merged upstream. The first commit is a very small cleanup to what you've already merged, since I misunderstood the purpose of some of the platform defines. The second extends support to all other platforms which I was able to identify, based upon the information from here.

Removed __i586__ and __i686__ from checks for the x86 target platform, as
they indicate specific processor versions... __i386__ (and/or __x86__?)
should always be set in that case.

Signed-off-by: Adric Norris <[email protected]>
Extend support for detection and reporting of build platform, via the
`git version --build-options' command, to non x86/x86_64 targets.

The list of GCC target defines used to flesh out the identification came
from <https://sourceforge.net/p/predef/wiki/Architectures/>.

Signed-off-by: Adric Norris <[email protected]>
@landstander668 landstander668 changed the title Extend support for reporting of build platform [WIP] Extend support for reporting of build platform Sep 2, 2016
@landstander668
Copy link
Author

@dscho Per your comments on adding build platform to CFLAGS here, I'm going to look into implementing this functionality in another way. I've therefore tagged this PR as WIP for the time being.

@dscho
Copy link
Member

dscho commented Nov 18, 2016

@landstander668 any updates?

@landstander668
Copy link
Author

Apologies, but I haven't really been able to work on this recently, and it doesn't look like this is going to change in the near future. I'm closing the PR for now... will open a new one if/when I have an opportunity to properly revisit the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants