On Thu, Jul 22, 2010 at 10:46 PM, John Drescher <dresche...@gmail.com> wrote: > On Thu, Jul 22, 2010 at 4:43 PM, Olaf van der Spek <olafvds...@gmail.com> > wrote: >> On Thu, Jul 22, 2010 at 10:41 PM, John Drescher <dresche...@gmail.com> wrote: >>>> And then what? Having two DLLs with the same name is not going to >>>> work. Same for import or static libs. >>> >>> It would work fine if the dlls for multiple configurations were not >>> all dumped in 1 folder. That is how I have used cmake for 2+ years. >> >> How will the loader load the correct DLL if they've got the same name? >> > > It loads the .dll in the path of the executable. Since the .dlls for > other configurations are not in the same path it finds the correct dll > and there is no conflict.
That *might* be fine if it's a private DLL. What about a shared one? >From windows/system32 (bad) or WinSXS? Why can't I have executables with multiple configs in a single dir? What about import libs? Normally the (VC) compiled only has a single lib dir in which all variants are stored. Olaf _______________________________________________ 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
