#16 To support Visual C++.Net 2005 Express Edition

open
nobody
None
5
2006-05-29
2006-05-29
Xiaofan Chen
No

Right now the Windows build is only supported with
Cygwin/MinGW and Visual C++.Net 2003. Visual
C++.Net 2003 is not freely available. It would be
nice to support the free Visual C++.Net 2005
Express Edition. Thanks.

Regards,
Xiaofan

Discussion

  • J.R. Heisey
    J.R. Heisey
    2006-09-03

    Logged In: YES
    user_id=1204660

    I'll volunteer to do this. It would be necessary to abandon
    the the VS 2003 projects. It would be too much effort to
    maintain both.

    I will not do this with out Scott's approval and some
    general concensus. Anyone know of any limits there are with
    Visual C++ 2005 EE?

    I've experimented a bit. I found that all the str*()
    functions and others have been deprecated with lots of
    warning messages.

    The new functions str*_s() include the size of the
    destination buffer. There are macros that can be used to
    turn off the warnings of the older functions.

    Comments,
    JR

     
  • Logged In: NO

    Since JR has deferred to me, it's only proper I defer to
    Borut. :)

    Borut is the gpsim Window's maintainer and if he is willing
    to accept Visual C++.Net 2005, then that's fine by me.

    Borut?

    Scott

     
  • Borut Ražem
    Borut Ražem
    2006-09-04

    Logged In: YES
    user_id=568035

    It is OK by me to make a switch. I haven't try VS.NET 2005
    yet, but anyway...

    > The new functions str*_s() include the size of the
    > destination buffer. There are macros that can be used to
    > turn off the warnings of the older functions.

    Don't forget that gpsim runs also on systems where str*_s
    functions are not available. I would rather remain on
    standard str* functions and turn the warnings off...

    Borut

     


Anonymous


Cancel   Add attachments