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

FEATURE REQUEST : clang 7.0 proper for sumo... #87

Closed
madscientist42 opened this issue Jan 22, 2019 · 3 comments
Closed

FEATURE REQUEST : clang 7.0 proper for sumo... #87

madscientist42 opened this issue Jan 22, 2019 · 3 comments

Comments

@madscientist42
Copy link

Sumo's recent enough to consider moving it up to 7.0 either in a branch (sumo-7.0) or in the main one for sumo.

Got a problem where my client is needing 7.0 for build of their application, but moving to thud ends up doing something...odd...with the bootloader process build that works in sumo.

If I do the work and provide a PR, would it be considered?

@kraj
Copy link
Owner

kraj commented Jan 22, 2019

Doing major version upgrade can be problematic on release branches since the package version of other recipes are more or less fixed and it could mean a lot of porting work to get them compiling with newer compiler

So I would suggest that keep fixing thud and get it going that’s the best approach

Second best approach is to to backport 7.x recipes into sumo parallel to 6.x and leave 6.x as default compiler I would accept such a patch

Third option is to provide enough testing that we can still build major layers e.g oe-core meta-openemebedded and meta-browser with 7.x on sumo branches of these repos then we might upgrade it as replacement

@madscientist42
Copy link
Author

I concur on the sentiment. Ideally, I'd love to get the whole thing to Thud and a bit more movable forward so my clients aren't mired in the past. Short-term, they're needing image build and an SDK now (Heh...when is it ever NOT a "now"?) so I'm going to slap a band-aid on their problem since they know their stuff works right with 7.0 and see if #2 is a viable medium-term option so others can embrace it at their own risk. #3's probably outside of anyone's realistic scope with Thud being out anyhow. :D

@madscientist42
Copy link
Author

Closed because the project's about to make a transition to Warrior, making this mostly MOOT. :D

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

No branches or pull requests

2 participants