VC++ complier with Codelite
-
- CodeLite Curious
- Posts: 6
- Joined: Thu Dec 09, 2010 1:29 pm
- Genuine User: Yes
- IDE Question: c++
- Contact:
VC++ complier with Codelite
May you please list me the steps/settings required to use vc++ compiler with codelite (instead of MinGW).
I have tried but can't get my program compiled.
Thanks
I have tried but can't get my program compiled.
Thanks
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: VC++ complier with Codelite
1) select the VC++ compiler in your project settings General's page
2) Adjust the include path / library path from: Settings | Build Settings | Compilers | VC++ | Advanced
Eran
2) Adjust the include path / library path from: Settings | Build Settings | Compilers | VC++ | Advanced
Eran
Make sure you have read the HOW TO POST thread
-
- CodeLite Curious
- Posts: 6
- Joined: Thu Dec 09, 2010 1:29 pm
- Genuine User: Yes
- IDE Question: c++
- Contact:
Re: VC++ complier with Codelite
I did these steps, but still can't compile, the output of building the application is:
----------Build Started--------
C:\WINDOWS\system32\cmd.exe /c ""mingw32-make.exe" -j 1 -f "test_vc_9_wsp.mk""
----------Building project:[ test_consol_1 - Debug ]----------
mingw32-make.exe[1]: Entering directory `E:/CPPDEV/CodeLite/test_vc_9/test_consol_1'
cl.exe /nologo /c "E:/CPPDEV/CodeLite/test_vc_9/test_consol_1/main.cpp" /Fo./Debug/main.obj "/I"C:/Program Files/Microsoft Visual Studio 9.0/VC/include"" "/I." "/I." "/I."
mingw32-make.exe[1]: *** [Debug/main.obj] Error -1073741515
mingw32-make.exe: *** [All] Error 2
mingw32-make.exe[1]: Leaving directory `E:/CPPDEV/CodeLite/test_vc_9/test_consol_1'
----------Build Ended----------
0 errors, 0 warnings
I already have MSVS installed and running, also I can use code::blocks successfully with vc++.
any suggestion please.
Regards,
M.Lotfy
----------Build Started--------
C:\WINDOWS\system32\cmd.exe /c ""mingw32-make.exe" -j 1 -f "test_vc_9_wsp.mk""
----------Building project:[ test_consol_1 - Debug ]----------
mingw32-make.exe[1]: Entering directory `E:/CPPDEV/CodeLite/test_vc_9/test_consol_1'
cl.exe /nologo /c "E:/CPPDEV/CodeLite/test_vc_9/test_consol_1/main.cpp" /Fo./Debug/main.obj "/I"C:/Program Files/Microsoft Visual Studio 9.0/VC/include"" "/I." "/I." "/I."
mingw32-make.exe[1]: *** [Debug/main.obj] Error -1073741515
mingw32-make.exe: *** [All] Error 2
mingw32-make.exe[1]: Leaving directory `E:/CPPDEV/CodeLite/test_vc_9/test_consol_1'
----------Build Ended----------
0 errors, 0 warnings
I already have MSVS installed and running, also I can use code::blocks successfully with vc++.
any suggestion please.
Regards,
M.Lotfy
-
- CodeLite Curious
- Posts: 6
- Joined: Thu Dec 09, 2010 1:29 pm
- Genuine User: Yes
- IDE Question: c++
- Contact:
Re: VC++ complier with Codelite
Dear Iran
I know you are so busy in many tasks, but I wish you give my complain some interest since I ought to use VC++ complier (to use some 3ed parties lib's) and I don't want to use MSVC IDE and want to make all my work with one IDE, which is Codelite that i comfortable with.
I tried to put the suggested path's but still can't compile my application.
Would you try it yourself and find where the problem is?
I used some other IDE's to compile with either GCC and VC++ (e.g. wxDev, Code::Blocks), and found that their support for deferent compilers are very flexible and very user friendly.
Regards,
m.Lotfy
I know you are so busy in many tasks, but I wish you give my complain some interest since I ought to use VC++ complier (to use some 3ed parties lib's) and I don't want to use MSVC IDE and want to make all my work with one IDE, which is Codelite that i comfortable with.
I tried to put the suggested path's but still can't compile my application.
Would you try it yourself and find where the problem is?
I used some other IDE's to compile with either GCC and VC++ (e.g. wxDev, Code::Blocks), and found that their support for deferent compilers are very flexible and very user friendly.
Regards,
m.Lotfy
-
- CodeLite Enthusiast
- Posts: 14
- Joined: Wed Feb 16, 2011 6:07 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: VC++ complier with Codelite
I *suppose* you didn't specify correctly all the tools for VC - you are still using mingw32-make instead of nmake for example - i just speculate as i don't use VC with CL.mlotfy wrote:I
----------Build Started--------
C:\WINDOWS\system32\cmd.exe /c ""mingw32-make.exe" -j 1 -f "test_vc_9_wsp.mk""
-
- CodeLite Guru
- Posts: 351
- Joined: Mon Oct 20, 2008 7:26 pm
- Genuine User: Yes
- IDE Question: C++
- Location: France
- Contact:
Re: VC++ complier with Codelite
IIRC, you have to start a cmd prompt, and call the vcvarsall.bat (or something like that), which allow you to use the vc compiler. This batch file is somewhere in the VisualStudio installation, under the vc dir (You'll have to find it, I do not have a VS currently).
HTH
HTH
Jérémie
-
- CodeLite Enthusiast
- Posts: 39
- Joined: Sat Aug 21, 2010 7:32 pm
- Genuine User: Yes
- IDE Question: c++
- Contact:
Re: VC++ complier with Codelite
check this
and this
You do not have the required permissions to view the files attached to this post.
-
- CodeLite Curious
- Posts: 6
- Joined: Mon Oct 19, 2009 10:41 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: VC++ complier with Codelite
Hi,
I stepped into the same error message some time ago, when I set up codelite for MSVC 2008:
You have to specify not only the path to cl.exe, but also to the general Visual Studio stuff:
<path_to_vs>\VC\bin AND <path_to_vs>\Common7\IDE
see also my post on that issue:
http://codelite.org/forum/viewtopic.php?f=3&t=985
HTH,
Kay
I stepped into the same error message some time ago, when I set up codelite for MSVC 2008:
You have to specify not only the path to cl.exe, but also to the general Visual Studio stuff:
<path_to_vs>\VC\bin AND <path_to_vs>\Common7\IDE
see also my post on that issue:
http://codelite.org/forum/viewtopic.php?f=3&t=985
HTH,
Kay
-
- CodeLite Enthusiast
- Posts: 37
- Joined: Fri Oct 01, 2010 8:32 pm
- Genuine User: Yes
- IDE Question: all
- Contact:
Re: VC++ complier with Codelite
hej!
where and how exactly did you put these? i tried a zillion methods to tell codelite searching for the binary but it doesn't work for me either. executed vcvars32.bat, added the path to msvc to the windows envpath, added the path to the cl internal env vars, added the path in practically EVERY textfield i found but it still uses mingw.
what leads to my wondering - why does it use mingw by default? mingw just seems to be defined in 'build systems' - i selected vc++ compiler for my project though. why doesn't it spit out something like 'can't find cl.exe'?
regards,
nem
where and how exactly did you put these? i tried a zillion methods to tell codelite searching for the binary but it doesn't work for me either. executed vcvars32.bat, added the path to msvc to the windows envpath, added the path to the cl internal env vars, added the path in practically EVERY textfield i found but it still uses mingw.
what leads to my wondering - why does it use mingw by default? mingw just seems to be defined in 'build systems' - i selected vc++ compiler for my project though. why doesn't it spit out something like 'can't find cl.exe'?
regards,
nem
-
- CodeLite Curious
- Posts: 6
- Joined: Mon Oct 19, 2009 10:41 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: VC++ complier with Codelite
Hi,
see screenshot below. Please note the backslashes in the path and the _missing_ double-quotes (").
Regarding mingw, that is still in my path, as I am using the standard mingw32-make build system of codelite also for MSVC.
BTW, is there a way to prevent overriding of these settings when updating codelite?
Cheers,
Kay
see screenshot below. Please note the backslashes in the path and the _missing_ double-quotes (").
Regarding mingw, that is still in my path, as I am using the standard mingw32-make build system of codelite also for MSVC.
BTW, is there a way to prevent overriding of these settings when updating codelite?
Cheers,
Kay
You do not have the required permissions to view the files attached to this post.