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: make it possibly to specify subdirs in build.info #7558

Closed
wants to merge 5 commits into from

Conversation

levitte
Copy link
Member

@levitte levitte commented Nov 3, 2018

This adds a keyword SUBDIRS for build.info, to be used like this:

SUBDIRS=foo bar

This tells Configure that it should look for 'build.info' in the
relative subdirectories 'foo' and 'bar' as well.

@levitte levitte added the branch: master Merge to master branch label Nov 3, 2018
crypto/build.info Outdated Show resolved Hide resolved
@richsalz
Copy link
Contributor

richsalz commented Nov 3, 2018

I am not disagree'ing with Tim's comment, but the concept of putting SUBDIR in the build.info is a great idea.

This adds a keyword SUBDIRS for build.info, to be used like this:

    SUBDIRS=foo bar

This tells Configure that it should look for 'build.info' in the
relative subdirectories 'foo' and 'bar' as well.
We have $config{openssl_algorithm_defines}, $config{openssl_other_defines}
and $config{openssl_thread_defines}.  These are treated exactly the same
in include/openssl/opensslconf.h.in, so having them separated into three
different databases isn't necessary, the reason for the separation being
long gone.  Therefore, we collapse them into one and the same,
$config{openssl_feature_defines}.
We kept a number of arrays of directory names to keep track of exactly
which directories to look for build.info.  Some of these had the extra
function to hold the directories to actually build.

With the added SUBDIRS keyword, these arrays are no longer needed.
The logic for skipping certain directories needs to be kept, though.
That is now very much simplified, and is made opportunistic.
@levitte
Copy link
Member Author

levitte commented Nov 3, 2018

Approval noted, and CIs look happy. I'll leave a grace period 'til sometime tomorrow, or perhaps monday

@levitte
Copy link
Member Author

levitte commented Nov 5, 2018

Merged. Thanks for the reviews!

75d47db Simplify the processing of skipped source directories
e0bf7c0 Collapse different classes of macro databases
9654924 Add SUBDIRS settings in relevant build.info files
7f73eaf Build: make it possibly to specify subdirs in build.info

@levitte levitte closed this Nov 5, 2018
levitte added a commit that referenced this pull request Nov 5, 2018
This adds a keyword SUBDIRS for build.info, to be used like this:

    SUBDIRS=foo bar

This tells Configure that it should look for 'build.info' in the
relative subdirectories 'foo' and 'bar' as well.

Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from #7558)
levitte added a commit that referenced this pull request Nov 5, 2018
Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from #7558)
levitte added a commit that referenced this pull request Nov 5, 2018
We have $config{openssl_algorithm_defines}, $config{openssl_other_defines}
and $config{openssl_thread_defines}.  These are treated exactly the same
in include/openssl/opensslconf.h.in, so having them separated into three
different databases isn't necessary, the reason for the separation being
long gone.  Therefore, we collapse them into one and the same,
$config{openssl_feature_defines}.

Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from #7558)
levitte added a commit that referenced this pull request Nov 5, 2018
We kept a number of arrays of directory names to keep track of exactly
which directories to look for build.info.  Some of these had the extra
function to hold the directories to actually build.

With the added SUBDIRS keyword, these arrays are no longer needed.
The logic for skipping certain directories needs to be kept, though.
That is now very much simplified, and is made opportunistic.

Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from #7558)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch: master Merge to master branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants