search for: midware

hi. I'm merging two datasets. one of them is 51 rows, and a typical row looks like this: midwar[midwar$dispnum==89,] dispnum synch sanum saname sbnum sbname year1 yearn ainit binit fatala 158 89 0 220 FRN 230 SPN 1822 1823 1 1 4 fatalb key1 keyn warnum year1.war yearn.war awon 158 5 2202301822 2202301823 1 1823 1823

...ut > the right language based on the file extensions of the source files. Yes, CMake figures out the *right language* based on the file extensions of the source files. But, llvm is based on *C++* for example, if you create a application just containing *C *extension files, but using llvm as the midware, then CMake system *must *auto recognize the LINKER_LANGUAGE as CXX, but not C. Even all source files in this project is C extension. Now, it's using a strange hack, just set_target_properties(c-index-test PROPERTIES LINKER_LANGUAGE CXX) It's not reasonable, because it's not beca...

On Oct 5, 2009, at 3:17 PM, 罗勇刚(Yonggang Luo) wrote: > Is there anyone get the time to apply this patch? I've committed my suggested fix. There's no point in setting the LINKER_LANGUAGE property of every LLVM library, because CMake figures out the right language based on the file extensions of the source files. - Doug > 2009/10/2, Douglas Gregor <dgregor at apple.com>:

Is there anyone get the time to apply this patch? 2009/10/2, Douglas Gregor <dgregor at apple.com>: > > On Oct 1, 2009, at 6:36 AM, 罗勇刚(Yonggang Luo) wrote: > >> At the first glance, it's coming with that c-index-test is just >> only containing c files (without cpp(cxx,c++) files). >> >> So cmake recognize it as pure C project, >> and so it's