So. I'll take my foot out of my mouth now. I actually got CDT 6.0 to work with nmake (from VS 2008 Express). Now if I could just calm down the warning level that would make things readable.
And the form that I use to control the DLL import and export seems to work also. Mike On Tue, Jul 14, 2009 at 3:18 PM, Michael Jackson<mike.jack...@bluequartz.net> wrote: > If you are using nmake then you are using MSVC which means you would drop > down into the #if defined (_MSVC_VER) block. At that point FLOW_DLL is going > to be defined as either the import or export version neither of which I have > any faith that CDT Would be able to parse any way (or it might but I am not > holding my breath). So my guess is that it is not going to work but not > because of CMake or anything else, it would probably be CDT's fault. > > And if you _are_ using nmake successfully with CDT, how are you doing that. > I have tried more than a few times to set that up all without any luck. > > ** I am also assuming you mean the nmake that comes with Visual Studio and > not the nmake that comes with UWin from AT&T.... > > --- > Mike Jackson www.bluequartz.net > > > > On Jul 14, 2009, at 3:10 PM, Miguel A. Figueroa-Villanueva wrote: > >> Well, I see it as a viable workaround, but only if you use eclipse >> only with gcc. In the case where you might use nmake/eclipse, then it >> won't work. > _______________________________________________ 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
