[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-dev] [New to the Forum] Migrating Visual Studio Project to Eclipse CDT
|
Hello,
I'm new to the forum so I'm not sure if this is the right place to post
(admin please relocate my post if need be -- thanks).
I've decided to move my rather large visual studio projects to Eclipse
(VS can no longer cope, or rather I can no longer cope without proper
context sensitive method selection, refactoring or place marks). I've
searched out a few guides on how to migrate a VS project (I'm currently
using the .NET 2003 version) to eclipse, unfortunately, all the help
pages out there are outdated. For example:
http://eclipsewiki.editme.com/InstallingCDTWithMSVisualC
http://www.ibm.com/developerworks/opensource/library/os-ecl-vscdt/
Its also been suggested by someone (here
http://dev.eclipse.org/newslists/news.eclipse.tools.cdt/msg08937.html )
that devenv can be used (with ant) instead make, but I don't know how to
configure ant to use make and to use all the windows libraries that my
projects require.
Any help will be greatly appreciated.
Thanks,
- Olumide
PS: my VS project's C/C++ command line options (from project property
pages) look like:
/Od /I "C:\Program Files\Alias\Maya6.5\include" /D "WIN32" /D "_DEBUG"
/D "_WINDOWS" /D "_AFXDLL" /D "_MBCS" /D "NT_PLUGIN" /D
"REQUIRE_IOSTREAM" /D "_WINDLL" /FD /EHsc /MDd /Fp"Debug/myCmd.pch"
/Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /nologo /c /TP
Additional options: /Gm /GX /ZI /I "." /D "WIN32" /D "_DEBUG" /YX /GZ /c
Linker command line options:
/OUT:"..\microphone\Debug\bearing.mll" /NOLOGO /LIBPATH:"C:\Program
Files\Alias\Maya6.5\lib" /DLL /PDB:"Debug/myCmd.pdb"
/IMPLIB:"Debug/myCmd.lib" Foundation.lib OpenMaya.lib OpenMayaUI.lib
OpenGL32.lib gts-0.7.6.lib glib-2.0.lib kernel32.lib user32.lib
gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib
oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
Additional options: /subsystem:windows /dll /incremental:yes /debug
/machine:I386 /export:initializePlugin /export:uninitializePlugin
