Do we have a list of switches that are not supported / won't be supported ?

Are these supported?
--enable-event-tracker
--enable-fips

On Fri, Oct 20, 2023 at 10:09 AM Chris McFarlen <ch...@mcfarlen.us> wrote:

> Docs are planned and there will be a summit talk on using cmake.  I plan
> to write docs as I am creating slides for the talk.
>
> Everything you listed is supported save enable-test-tools which needs to
> be added.
>
> CMAKE_INSTALL_PREFIX > --prefix
> WITH_USER            > --with-user
> OPENSSL_ROOT_DIR     > --with-openssl
> jemalloc_ROOT        > --with-jemalloc
> BUILD_TESTS=OFF      > --disable-tests
> BUILD_EXPERIMENTAL_PLUGSINS=OFF (default) > —-disable-experimental-plugins
> ENABLE_EXAMPLE=OFF (default) > —-disable-example-plugins
> TBD                  > —-enable-test-tools
> CMAKE_BUILD_TYPE=Debug  > —-enable-debug
> autodetect (turn off with ENABLE_CCACHE=OFF) > —-enable-ccache
> BUILD_NUMBER.    > —-with-build-number
>
>
> Sent with Proton Mail secure email.
>
> ------- Original Message -------
> On Thursday, October 19th, 2023 at 8:44 PM, James Peach <jpe...@apache.org>
> wrote:
>
>
> > Could you please summarize the current state of the cmake work?
> >
> > Is there any documentation for users of how to switch from autotools to
> cmake? Are there any autotools build features that are not supported in
> cmake?
> >
> > FWIW I have builds that are using
> > --prefix
> > --with-user
> > --with-openssl
> > --with-jemalloc
> > --disable-tests
> > —-disable-experimental-plugins
> > —-disable-example-plugins
> > —-enable-test-tools
> > —-enable-debug
> > —-enable-ccache
> > —-with-build-number
> > PKG_CONFIG_PATH
> > RPATH
> >
> > > On 20 Oct 2023, at 2:35 am, Chris McFarlen ch...@mcfarlen.us wrote:
> > >
> > > With each CI job now using cmake, the autotools configuration setup
> will quickly become unusable. This is a proposal to go ahead and remove the
> auto tools config from the tree to speed up the planned moves and upcoming
> refactoring to the source code. Maintaining two sets of configuration files
> has been necessary while the cmake build was reaching parity, but now it
> will be difficult to detect breaking changes.
> > >
> > > What say you?
> > >
> > > Chris
> > >
> > > Sent with Proton Mail secure email.
>

Reply via email to