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

freetype: don't clober CFLAGS/LDFLAGS #324

Merged
merged 1 commit into from
Dec 6, 2020

Conversation

ThomasAdam
Copy link
Member

When detecting Freetype, don't include its own compilation information
directly in CFLAGS/LDFLAGS. Instead, separate this out.

This fixes the case where a user could override CFLAGS as in:

make CFLAGS="-O0 -ggdb" -j $(nproc)

yet freetype clobbers this, resulting in freetype not being detected.

When detecting Freetype, don't include its own compilation information
directly in CFLAGS/LDFLAGS.  Instead, separate this out.

This fixes the case where a user could override CFLAGS as in:

    make CFLAGS="-O0 -ggdb" -j $(nproc)

yet freetype clobbers this, resulting in freetype not being detected.
@ThomasAdam ThomasAdam added this to the 1.0.2 milestone Dec 6, 2020
@ThomasAdam ThomasAdam self-assigned this Dec 6, 2020
@ThomasAdam
Copy link
Member Author

@mikeandmore

FYI -- this is how I solved this. Seems to work for me.

@mikeandmore
Copy link
Contributor

I don't know autoconf very well...but I think this is the best way to fix it. Freetype is just another library so we should handle its cflags in the same way.

@ThomasAdam ThomasAdam merged commit ccfad77 into master Dec 6, 2020
@ThomasAdam ThomasAdam deleted the ta/freetype-compilation-flags branch December 6, 2020 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants