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

build: improve shared library flags logic #1450

Closed

Conversation

jbergstroem
Copy link
Member

This is one of the commit from #1429 which fixes a bug with shared library flags. The other pull request doesn't necessarily have any issues but could benefit from a bit more review. This should be simple enough to get reviewed and merged ahead of 1.8.0

/R=@rvagg, ?

Move all logic for headers/libraries for each shared library
into the shared library scope - similar to how OpenSSL already works.

Also, don't assume that b() returns a boolean.
@Nibbler999
Copy link
Contributor

I can confirm this fixes #1434

@mscdex mscdex added the build Issues and PRs related to build files or the CI. label Apr 17, 2015
@bnoordhuis
Copy link
Member

It would be nicer if --shared-whatever-includes or --shared-whatever-libname implied --shared-whatever.

If I read your PR right, you have to specify --shared-whatever now or the includes/libname/libpath/etc. options are ignored.

@Fishrock123 Fishrock123 added this to the 1.8.0 milestone Apr 17, 2015
@jbergstroem
Copy link
Member Author

@bnoordhuis I prefer being exact since thats how other build systems work. Theres no benefit to being lazy here imo.

There are so many things that break if you start playing around with configure flags. --enable-static and any of the shared flags, etc. My plan was to start testing these and scope if possible to avoid breakage.

@jbergstroem
Copy link
Member Author

Closing in favour of #1454.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants