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: [rpm] After fixing scratchbox the libclang workaround is not required anymore. JB#55042 #150

Closed
wants to merge 1 commit into from

Conversation

krnlyng
Copy link

@krnlyng krnlyng commented Jan 12, 2023

We still need to specify the path for it though, since configure picks it off of LD_LIBRARY_PATH which has the sb2 tooling path in it.

DO NOT MERGE BEFORE:
sailfishos/scratchbox2#21

@llewelld
Copy link
Member

llewelld commented Jan 12, 2023

Does sailfishos/scratchbox2#21 also fix the "#include_next" issue, or was this fixed elsewhere already?

@krnlyng
Copy link
Author

krnlyng commented Jan 12, 2023

Does sailfishos/scratchbox2#21 also fix the "#include_next" issue, or was this fixed elsewhere already?

It does indeed fix that too. In fact it's required to remove that workaround, otherwise there'll be build issues.

@llewelld
Copy link
Member

Okay, nice. This change looks fine to me, but I guess I should do at least one complete local build just to be sure, before hitting Accept.

@krnlyng
Copy link
Author

krnlyng commented Jan 12, 2023

Okay, nice. This change looks fine to me, but I guess I should do at least one complete local build just to be sure, before hitting Accept.

You'll need to install scratchbox2 and libsb2 from the other pr in the sdk. As well as libsb2 in the tooling.

… anymore. JB#59836

We still need to specify the path for it though, since configure picks it off of
LD_LIBRARY_PATH which has the sb2 tooling path in it.
@krnlyng
Copy link
Author

krnlyng commented Jan 15, 2023

Does sailfishos/scratchbox2#21 also fix the "#include_next" issue, or was this fixed elsewhere already?

It does indeed fix that too. In fact it's required to remove that workaround, otherwise there'll be build issues.

It's a bit weird, sometimes i do get an error due to include_next, sometimes not. It also seems to be happening when the workaround is applied sometimes though?

In other words: do not merge yet :)

@krnlyng
Copy link
Author

krnlyng commented Aug 22, 2023

It never fully worked unfortunately. Will close for now.

@krnlyng krnlyng closed this Aug 22, 2023
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