Re: [CMake] ExternalProject breaks a parallel make.
В Sat, 2 Apr 2011 14:08:36 -0400 David Cole пишет: > Try with CMake 2.8.4 -- we fixed some parallel make propagation issues > in 2.8.3 or 2.8.4... Using "$(MAKE)" now. Should avoid the problem > you're reporting here. Your advice for 2.8.2 solved the problem, thanks David. BUILD_COMMAND = $(MAKE) INSTALL_COMMAND = $(MAKE) install ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Dependencies scanning for non-c/c++ files
Ah, I see this is an issue already discussed in length. Well hopefully something comes of these discussions. Thanks for the links. --- Aaron Wright From: Michael Hertling To: cmake@cmake.org Date: 04/06/2011 05:03 AM Subject:Re: [CMake] Dependencies scanning for non-c/c++ files Sent by:cmake-boun...@cmake.org On 04/05/2011 06:26 PM, aaron_wri...@selinc.com wrote: > There's a base class for the dependency scanners and several derived > classes for C, java, fortan, etc. Would it not be easy to just derive > another class for each file type I need? These dependency scanner classes > seemed to just regex each line in the file looking for "include" or > "import", or some other language specific keyword. That would work for me, > I could just scan for "m4_include". Probably, this is well feasible, but IMO, it would be really worthwhile to - optionally - enable the usage of an external tool to do dependency scanning, for new languages as well as for the premier ones like C/C++ in case one wants to overcome the built-in scanner's shortcomings while accepting certain performance penalties. There has already been some considerations and requests in this regard, e.g.: http://www.mail-archive.com/cmake@cmake.org/msg30396.html (!) http://public.kitware.com/Bug/view.php?id=11985 http://public.kitware.com/Bug/view.php?id=11770 http://public.kitware.com/Bug/view.php?id=2172 Regards, Michael ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Dependencies scanning for non-c/c++ files
On 04/05/2011 06:26 PM, aaron_wri...@selinc.com wrote: > There's a base class for the dependency scanners and several derived > classes for C, java, fortan, etc. Would it not be easy to just derive > another class for each file type I need? These dependency scanner classes > seemed to just regex each line in the file looking for "include" or > "import", or some other language specific keyword. That would work for me, > I could just scan for "m4_include". Probably, this is well feasible, but IMO, it would be really worthwhile to - optionally - enable the usage of an external tool to do dependency scanning, for new languages as well as for the premier ones like C/C++ in case one wants to overcome the built-in scanner's shortcomings while accepting certain performance penalties. There has already been some considerations and requests in this regard, e.g.: http://www.mail-archive.com/cmake@cmake.org/msg30396.html (!) http://public.kitware.com/Bug/view.php?id=11985 http://public.kitware.com/Bug/view.php?id=11770 http://public.kitware.com/Bug/view.php?id=2172 Regards, Michael ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] DLL and EXE with same base name: clash in VS.
On 04/06/2011 10:34 AM, Óscar Fuentes wrote: > Michael Wild writes: > >> On 04/06/2011 09:21 AM, Alexey Livshits wrote: We have a clang.exe and a clang.dll. While building, VS creates clang.pdb (for the executable) and clang.pdb (for the dll) which obviously is not right. Is there a way to tell VS to use a different name for the PDB? >>> >>> You can use different project name for exe and set the output name via >>> OUTPUT_NAME property. >> >> CMake uses prefix+base+".pdb" to generate the PDB file name, however I >> didn't dig deep enough to find out what `base' is, just that it is >> obtained with cmTarget::GetName(). Whether that refers to the target >> name or the OUTPUT_NAME, I couldn't find out easily, so you'll have to >> experiment ;-) > > It is OUTPUT_NAME. The target name for clang.dll is libclang and the > build creates clang.pdb (and clang.ilk ...) > > If I understand correctly what Michael says, the .pdb file name is > hardcoded. If I read cmTarget::GetPDBName(const char*) in cmTarget.cxx correctly, yes. I don't know VS well enough to know whether using a different name would actually work, or whether the name is being enforced. Michael ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] DLL and EXE with same base name: clash in VS.
Michael Wild writes: > On 04/06/2011 09:21 AM, Alexey Livshits wrote: >>> We have a clang.exe and a clang.dll. While building, VS creates >>> clang.pdb (for the executable) and clang.pdb (for the dll) which >>> obviously is not right. Is there a way to tell VS to use a different >>> name for the PDB? >> >> You can use different project name for exe and set the output name via >> OUTPUT_NAME property. > > CMake uses prefix+base+".pdb" to generate the PDB file name, however I > didn't dig deep enough to find out what `base' is, just that it is > obtained with cmTarget::GetName(). Whether that refers to the target > name or the OUTPUT_NAME, I couldn't find out easily, so you'll have to > experiment ;-) It is OUTPUT_NAME. The target name for clang.dll is libclang and the build creates clang.pdb (and clang.ilk ...) If I understand correctly what Michael says, the .pdb file name is hardcoded. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] DLL and EXE with same base name: clash in VS.
On 04/06/2011 09:21 AM, Alexey Livshits wrote: >> We have a clang.exe and a clang.dll. While building, VS creates >> clang.pdb (for the executable) and clang.pdb (for the dll) which >> obviously is not right. Is there a way to tell VS to use a different >> name for the PDB? > > You can use different project name for exe and set the output name via > OUTPUT_NAME property. CMake uses prefix+base+".pdb" to generate the PDB file name, however I didn't dig deep enough to find out what `base' is, just that it is obtained with cmTarget::GetName(). Whether that refers to the target name or the OUTPUT_NAME, I couldn't find out easily, so you'll have to experiment ;-) Michael ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] DLL and EXE with same base name: clash in VS.
> We have a clang.exe and a clang.dll. While building, VS creates > clang.pdb (for the executable) and clang.pdb (for the dll) which > obviously is not right. Is there a way to tell VS to use a different > name for the PDB? You can use different project name for exe and set the output name via OUTPUT_NAME property. -- BG, Alexey ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
