Re: Enabling/Disabling Vim features during compilation

On Mo, 30 Aug 2021, lists@ifohancroft.com wrote:

>
> Hi,
>
> I have a couple of questions that I couldn't find an answer for. If anything
> is unclear, please let me know.
>
> 1. Excluding the features marked with '-', can each of the
> features in https://vimhelp.org/various.txt.html#%2Bfeature-list be
> explicitly enabled or disabled on their own during compilation?

Not sure what you mean by that. Many features (but not all) can be
enabled passing appropriate flags to the configure script. Check the
help from ./configure --help for the different flags.

> 2. Are there any features that can be disabled/enabled during compilation
> that can't be enabled/disabled by passing an option to ./configure?

Yes. You may edit the header file feature.h. Note, if you just start
enabling features blindly, compilation may fail (because of ifdefs), so
be careful.

> If the answer to #1 is yes and the answer to #2 is no - I see that
> ./configure --help doesn't list a separate option for each of the
> features, but there is --enable-FEATURE[=ARG] and --disable-FEATURE so I
> am guessing I just replace FEATURE with the name of the feature I wish
> to enable or disable and I don't actually include the + sign, just the
> plain feature name, however:
>
> 3.1. If builtin_terms is enabled, whether only some terminals will be
> builtin or all of them depends on whether builtin_terms is
> +builtin_terms or ++builtin_terms. How do I specify ++builtin_terms as
> --enable-FEATURE? Should it be --enable-+builtinterms?

I believe this is a feature, that is enabled using feature.h depending
on the feature set (huge, normal, small). What are you trying to do
here? Is there a particular interest in the builtinterms feature?

> 3.2. I see that some features that have explicit enable/disable options
> for them and require passing an argument (for example the Perl
> interpreter option requires an argument whether it should be anbled or
> not and whether it should be dynamically loaded) have a +feature
> equivalent with separate options for the different arguments of the
> builtin enable/disable option. Very clever btw! In such a case, if I
> choose to enable the Perl interpret using --enable-perl and want it
> loaded dynamic, instead of setting --enable-perlinterp=dynamic, do I use
> just --enable-perl/dyn or should I use both --enable-perl and
> --enable-perl/dyn?

Check the help of the configure script:

#v+
chrisbra@debian ~/code/vim-src/src% ./configure --help |grep -i perl
--enable-perlinterp=OPTS Include Perl interpreter. default=no OPTS=no/yes/dynamic
#v-

Does that help?

Best,
Christian
--
Jemand, der immer lustig ist, ist was Unerträgliches.
-- Loriot (eigentlich Vicco von Bülow)

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20210831061120.GA1795913%40256bit.org.