On May 4, 2012, at 12:38 PM, Hal Finkel wrote: >>> If we set this up kind of like clang is >>> setup, then the build system will detect whether there is a fortran >>> subdirectory in clang, and if so, will build (defining >>> CLANG_HAS_FORTRAN or something like that) and link the extra >>> components. >> >> Should "flang" (please come up with a better name! :) be in >> llvm/tools/flang or in llvm/tools/clang/flang? I think that the >> former makes more sense. These are peer projects, even if one is >> dependent on the other. > > Yea, I was avoiding that :) If we really want something with 'lang' at > the end, then we could call it fortlang (I am certainly open to other > suggestions).
It doesn't have to end with "lang"! > Otherwise, we could avoid the issue for now and just name > the repository fortran or ffe. I think making them peer projects in > reasonable. If we're reusing the built sources from clang, then we just > need to setup the makefiles to make sure that clang is always built > first. It's not a great suggestion, but how about "lfort"? -Chris _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
