STLport

Michael Fink wrote:
> Hi,
>
> I recently tried out Visual Studio 2008 beta 2 and tried to compile 
> STLport with it. The new VS comes with support for x86, x64, PocketPC 
> 2003 and  Windows Mobile 5 SDKs.
>
> The problem mainly lies with setting up compiler environment variables 
> to do the actual compilation. For the first two targets, VS comes with 
> two (actually three, if you're compiling for x64 using a x86 OS) batch 
> files to set up environment.
>
> There should be no problem when compiling for one platform only, but 
> when I use the configure.bat switch -x to create platform-dependent lib 
> and bin subfolders, I have a problem. The VS batch files don't 
> explicitly set a platform specific environment variable, so 
> configure.bat cannot decide which platform it should compile for.
>
> Some time ago the -p parameter (for platform) was removed since all 
> platforms on msvc and evc could be detected from the batch files' 
> environment variables, but when we want to support msvc9 we need some 
> way to decide which platform was set up. Any opinions on how to do that? 
> Maybe it would be best to just call the compiler and see what it prints out?
>   
It is only a beta version , who knowns if the release won't contain the 
necessary information. If not, calling the compiler would be an elegant 
way of doing it. Do we have enough tool under a cmd or command shell to 
manipulate the resulting string and find necessary information ? 
Otherwise we will have to restore -p option...
> An even bigger problem is when compiling for mobile WinCE devices, since 
> these platforms come without any batch files to set up compiling. Any 
> ideas there?
>   
    I hope Microsoft will document how to setup a development 
environment in this case. If not then I think we will only have to say 
good luck to users of those environments :-)

Hi,

>> Some time ago the -p parameter (for platform) was removed since all 
>> platforms on msvc and evc could be detected from the batch files' 
>> environment variables, but when we want to support msvc9 we need some 
>> way to decide which platform was set up. Any opinions on how to do that? 
>> Maybe it would be best to just call the compiler and see what it prints out?
>>   
> It is only a beta version , who knowns if the release won't contain the 
> necessary information. If not, calling the compiler would be an elegant 
> way of doing it. Do we have enough tool under a cmd or command shell to 
> manipulate the resulting string and find necessary information ? 
> Otherwise we will have to restore -p option...

I could also download and install the RTM, which should be available, 
too. I don't think they will add an environment variable for this, 
though. I don't know much about shell programming, so I don't know if 
it's possible.

I'll look into parsing compiler version output with the shell. If that 
doesn't work it seems we're back to restoring the -p option...

>> An even bigger problem is when compiling for mobile WinCE devices, since 
>> these platforms come without any batch files to set up compiling. Any 
>> ideas there?
>>   
>     I hope Microsoft will document how to setup a development 
> environment in this case. If not then I think we will only have to say 
> good luck to users of those environments :-)

Well, a wizard-generated project should contain all defines, but I guess 
  it's good to provide files that contain everything needed. As I had to 
figure it out anyway, I can do that, too.

bye
Michael