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

[Android] Enable LTO #274

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Conversation

Vogtinator
Copy link
Member

@Vogtinator Vogtinator commented Oct 19, 2022

On armeabi-v7a it's broken in two ways.
Also simplify the LTCG determination code and print the result.

Depends on #285

@Vogtinator
Copy link
Member Author

@adriweb Looks like the case without HAVE_SECRETS isn't working

@adriweb
Copy link
Member

adriweb commented Dec 5, 2022

@adriweb Looks like the case without HAVE_SECRETS isn't working

Indeed... How does that not work, though? We see HAVE_SECRETS: false in the env dump, and it has an if ${{ env.HAVE_SECRETS == 'true' }} ...

@Vogtinator
Copy link
Member Author

@adriweb Looks like the case without HAVE_SECRETS isn't working

Indeed... How does that not work, though? We see HAVE_SECRETS: false in the env dump, and it has an if ${{ env.HAVE_SECRETS == 'true' }} ...

Maybe just if: runner.os == 'macOS' && github.repository == 'nspire-emus/firebird' && env.HAVE_SECRETS == 'true' ?

@adriweb
Copy link
Member

adriweb commented Dec 5, 2022

I'll try, but the original version was a copy paste from some big repo CI that seemingly worked heh

@Vogtinator
Copy link
Member Author

Apparently secrets are not available in if, maybe env isn't available either? https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-secrets

@adriweb
Copy link
Member

adriweb commented Dec 5, 2022

well apparently it's because secrets aren't available in if that the intermediate "putting the boolean value in env" step is required for the check, but...

@Vogtinator
Copy link
Member Author

My assumption would be that env is computed only when a step is run, but if has to be computed much earlier than that to determine whether to run the step at all.

@adriweb
Copy link
Member

adriweb commented Dec 5, 2022

My assumption would be that env is computed only when a step is run, but if has to be computed much earlier than that to determine whether to run the step at all.

Well the docs about that say it should be fine: "You can use a context in an if conditional statement to access the value of an environment variable."
And the syntax i their example is if: ${{ env.DAY_OF_WEEK == 'Monday' }} which is what I also do: if: ... && ${{ env.HAVE_SECRETS == 'true' }}

So... wut ?

Edit: maybe it's a syntax thing and ${{ .. }} should wrap the whole expression ; I'll try that

@Vogtinator
Copy link
Member Author

Edit: maybe it's a syntax thing and ${{ .. }} should wrap the whole expression ; I'll try that

That was my first guess as well, the if is implicitly wrapped in ${{}} already and nesting that might not work.

@adriweb
Copy link
Member

adriweb commented Dec 5, 2022

I'll let you rebase and see if it works now 🤷‍♂️

@adriweb adriweb added the build label Dec 5, 2022
On armeabi-v7a it's broken in two ways.
Also simplify the LTCG determination code and print the result.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants