-
Notifications
You must be signed in to change notification settings - Fork 31
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add --with-libarchive configure option to specify where to find archi…
…ve.h. By default it is searched in /usr/include and /usr/local/include, if the header file is not in these directory you must use this option. For example: ./configure --with-libarchive=/opt/csw
- Loading branch information
Showing
2 changed files
with
48 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b17224b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some notes.
Option can't discover archive.h, when path specified
--with-libarchive=/opt/csw
(i.e. like in --with-c-icap=/usr/local option, when we're specified one level up directory).
and, to find libarchive, option must be specified
--with-libarchive=/opt/csw/include
which look a bit illogical.
Also a bit cosmetic:
https://i.imgur.com/Itmy9GK.png
--with-* options looks like unformatted ;)
b17224b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why it is illogical? You have to give the directory where archive.h is stored. The configure script will use
-I/opt/csw/include
or-I/usr/local/include
.I've also noted the cosmetic issue on
--help
output formatting.b17224b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually in --with-* options set base dir, not exact dir (for libraries/includes).
--with-c-icap= found ICAP library/include starting from base_dir (/usr/local, for example).
Thus, will be logical --with-libarchive will have same behaviour, isn't it? ;)
b17224b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree even if
--with-c-icap
is not a good example :-) Commit b465edd allow both, base dir and real dir. The cosmetic issue is also fixed. Thanks Yuri.b17224b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem :)