<br><br><div class="gmail_quote">On Wed, Jun 18, 2008 at 5:31 PM, Miguel A. Figueroa-Villanueva <<a href="mailto:miguelf@ieee.org">miguelf@ieee.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Jun 18, 2008 at 8:10 AM, Mehdi Rabah wrote:<br>
> On Wed, Jun 18, 2008 at 10:43 AM, Christian Ehrlicher wrote:<br>
>><br>
>> > Von: "Mehdi Rabah"<br>
</div><div><div></div><div class="Wj3C7c">>> > On Tue, Jun 17, 2008 at 9:24 PM, Christian Ehrlicher wrote:<br>
>> ><br>
>> > > Bill Hoffman schrieb:<br>
>> > ><br>
>> > >> Alexander Neundorf wrote:<br>
>> > >><br>
>> > >>> On Tuesday 17 June 2008, Christian Ehrlicher wrote:<br>
>> > >>> ...<br>
>> > >>><br>
>> > >>>> How do you define which vsvars32.bat (or vsvars64.bat) to use? I've<br>
>> > more<br>
>> > >>>> than one compiler on my system...<br>
>> > >>>><br>
>> > >>><br>
>> > >>> The first time you would have to run cmake in the right environment<br>
>> > (i.e.<br>
>> > >>> where the correct vcvars.bat has been executed).<br>
>> > >>> But I don't have a windows here, so I am not the best person for<br>
>> > this...<br>
>> > >>><br>
>> > >>><br>
>> > >> I realize some people get confused by this. However, I don't think<br>
>> > >> it<br>
>> > is<br>
>> > >> too much to ask that you have a correct environment setup for using<br>
>> > >> the<br>
>> > >> compiler. We ask no less on Linux/Unix. If gcc is incorrectly<br>
>> > installed,<br>
>> > >> and can't find headers, we don't try and add -I stuff to fix the<br>
>> > problem...<br>
>> > >><br>
>> > >> That's my opinion too - I don't see the point why it should be so<br>
>> > >> hard<br>
>> > to<br>
>> > > set up the correct environment so that it must be done by cmake.<br>
>> > ><br>
>> > ><br>
>> > Hi,<br>
>> ><br>
>> > The point is not to setup the compiler, it is to have cmake include path<br>
>> > pointing to standard locations. For example where STL header are<br>
>> > (like/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/include on<br>
>> > linux), to avoid extra configurations step in the IDE, not for the<br>
>> > compiler.<br>
>> > I talk especially about Eclipse CDT, in which STL automatic completion<br>
>> > work<br>
>> > well under linux, but not under windows.<br>
>><br>
>> This looks like a Eclipse bug rather than something cmake can do for you.<br>
>> As you already said - they're standard locations for the compiler so why<br>
>> should cmake care in any way?<br>
><br>
> -> because Eclipse also doesn't care about the compiler, Eclipse only call<br>
> makefiles. Again, this is not a compiler issue, this is a project setting<br>
> issue. And since my project file is _generated by cmake_, I thought this<br>
> feature will be simple to point to there standard locations. (which is done<br>
> within a cmake gcc-mingw eclipse project I believe)<br>
><br>
>><br>
>> And as before - I've more than one compiler on my system...<br>
><br>
> I also have more than one compiler working on my system but I fail to see<br>
> how this is related to this issue.<br>
><br>
> CMake doesn't care about these standard locations, and Eclipse also do --><br>
> I'll just add a if(WIN32) followed by an include_directories(), this is not<br>
> a big deal.<br>
<br>
</div></div>Mehdi,<br>
<br>
These are two separate issues. The issue that Alex brought up is a<br>
hard thing to do. That is, you are required to have the enviroment set<br>
at cmake time, otherwise the generation will fail.<br>
<br>
However, what you are asking is quite feasible and if you provide the<br>
information I requested in my last e-mail I can implement it.<br>
<br>
Thanks,<br>
<font color="#888888">--Miguel<br>
</font></blockquote></div><br>Hi Miguel,<br>
thanks for your two mails ^^<br>
<br>
After configuring my project, I need to add "C:\Program Files\Microsoft
Visual Studio 9.0\VC\include" path to the project, here is how:<br><br>
- right click on project root<br>
- clic on properties<br>
- clic on "c++ include path and symbols" <br>
- clic on "add external include path"<br>
- paste the visual studio include path<br>
-> ok -> ok<br>
<br>
I understood that the issue we were discussing is the same because the
include path I just gave you is in the vsvars32.bat. Unless you have
another way of getting this information? (hard code it?)<br><br>Regards,<br>--<br><font color="#888888">
Mehdi</font><br>