Hello Everyone,
I wanted to inform everybody of this patch: http://reviews.llvm.org/D12211
This patch gets rid of expand-vars.pl and uses CMake’s configure_file() function instead.
One major consequence this patch introduces is breaking the Perl+Makefile build system.
I was wondering if everyone would be ok if I submitted a patch that has the default target in the top level make give an explanation to the user why he/she should use the CMake build system instead effectively deprecating the Perl+Makefile build system.
And to the LLVM experts, is there a documented way to deprecate something?
Any help is greatly appreciated!
– Johnny
From: "Jonathan L via Openmp-commits Peyton" <openmp-commits@lists.llvm.org>
To: openmp-dev@lists.llvm.org, openmp-commits@lists.llvm.org
Sent: Thursday, August 20, 2015 3:58:30 PM
Subject: [Openmp-commits] Perl+Makefile based system old and broken
Hello Everyone,
I wanted to inform everybody of this patch:
⚙ D12211 [OpenMP] [CMake] Removing expand-vars.pl in favor of CMake's configure_file()
This patch gets rid of expand-vars.pl and uses CMake’s
configure_file() function instead.
One major consequence this patch introduces is breaking the
Perl+Makefile build system.
I was wondering if everyone would be ok if I submitted a patch that
has the default target in the top level make give an explanation to
the user why he/she should use the CMake build system instead
effectively deprecating the Perl+Makefile build system.
I think that many are hopeful that LLVM will have switched completely to CMake for the next release anyway; I'm fine with killing the Perl+Makefile setup and replacing it with something that tells users what to do instead.
And to the LLVM experts, is there a documented way to deprecate
something?
Put it in the release notes. I don't think that we have a better way.
-Hal