mirror of
https://github.com/RPCS3/llvm.git
synced 2024-12-30 16:34:03 +00:00
9802a6cbdc
As an example that was not actually being used, it suffered from a slow bitrot. The two main issues with it were that it had no cmake support and included a copy of the autoconf directory. The reality is that autoconf is not easily composable. The lack of composabilty is why we have clang options in llvm's configure. Suggesting that users include a copy of autoconf/ in their projects seems a bad idea. We are also in the process of switching to cmake, so pushing autoconf to new project is probably not what we want. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@203728 91177308-0d34-0410-b5e6-96231b3b80d8 |
||
|---|---|---|
| .. | ||
| m4 | ||
| AutoRegen.sh | ||
| config.guess | ||
| config.sub | ||
| configure.ac | ||
| ExportMap.map | ||
| install-sh | ||
| LICENSE.TXT | ||
| missing | ||
| mkinstalldirs | ||
| README.TXT | ||
Upgrading autoconf =============================================================================== If you are in the mood to upgrade autoconf, you should: 1. Consider not upgrading. 2. No really, this is a hassle, you don't want to do it. 3. Get the new version of autoconf and put it in <SRC> 4. configure/build/install autoconf with --prefix=<PFX> 5. Run autoupdate on all the m4 macros in llvm/autoconf/m4 6. Run autoupdate on llvm/autoconf/configure.ac 7. Regenerate configure script with AutoRegen.sh 8. If there are any warnings from AutoRegen.sh, fix them and go to step 7. 9. Test, test, test.