That extension will be distributed by Microsoft as part of their express 
program. I don't know when that would happen.

- Alfred

Benjamin Davison wrote:
> --
> [ Picked text/plain from multipart/alternative ]
> Just a quick Q: Alfred, sorry to take this offtopic.
>
> I watched a Microsoft research show done by a couple of the valve
> guys(I
> belive it was Mike Dunkle(sp)) and there was talks of getting some
> level of integration going on between VSExpress and the SDK. Do you
> have any idea how
> we will get this and will it be included in the beta update.
>
> Thanks if you answer this.
>
> On 11/16/05, Alfred Reynolds <[EMAIL PROTECTED]> wrote:
>>
>> Yes, VS.NET <http://VS.NET> 2003 is still our primary development
>> platform. VS.NET <http://VS.NET> 2005 is a part of our 64-bit port
>> efforts.
>>
>> - Alfred
>>
>> Teddy wrote:
>>> Will the SDK still be compaible with VS.NET <http://VS.NET> 2003?
>>>
>>> On 11/16/05, Alfred Reynolds <[EMAIL PROTECTED]> wrote:
>>>> What pleas? We are working on an update to get the code base to
>>>> compile under VS.NET <http://VS.NET> 2005, this should help with
>>>> GCC 4.x also.
>>>>
>>>> - Alfred
>>>>
>>>> Ondrej Hošek wrote:
>>>>> It went along the lines of "make it compile", "copy server_i486.so
>>>>> over to the server" and "./srcds_run". Purely trial-and-error.
>>>>> Seems like the ABI differences are minimal, if any. (I hope it'll
>>>>> stay that way for the next few versions.)
>>>>>
>>>>> If Valve decides to move to GCC 4, I'm ready to trade a .diff file
>>>>> for a "thank you" (and maybe the right to brag about having been
>>>>> helpful ;-)). As I said, I just need to try compiling with
>>>>> Microsoft's C++ compiler first, since it's not my objective to
>>>>> destroy things for one group just to make them work for the
>>>>> other. (At least not in this case.)
>>>>>
>>>>> Any chances of my two pleas having been heard by the "higher
>>>>> powers"?
>>>>>
>>>>> Have a nice day,
>>>>> ~~ Ondra Hosek
>>>>>
>>>>> Alfred Reynolds wrote:
>>>>>> The C++ ABI differs in GCC 4.x from GCC 3.x, last time I tried it
>>>>>> was not possible to run a mod compiled with 4.x (as C++
>>>>>> interfaces are passed from it to our GCC 3.x compiled binaries).
>>>>>> How did you solve that?
>>>>>>
>>>>>> - Alfred
>>>>>>
>>>>>> Ondrej Hošek wrote:
>>>>>>
>>>>>>> Greetings to fellow list members,
>>>>>>>
>>>>>>> Recently, I have managed to coerce the code released with the
>>>>>>> Half-Life 2 SDK to compile on Linux with GCC 4.0.2 without
>>>>>>> -fpermissive and with -Wall -Werror (both "mod" and "plugin"
>>>>>>> targets). I will release this modified code later on after
>>>>>>> incorporating the changes of the upcoming SDK beta and ensuring
>>>>>>> that the code still compiles with Microsoft's C++ compiler.
>>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> To unsubscribe, edit your list preferences, or view the list
>>>>> archives, please visit:
>>>>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>>>>
>>>> _______________________________________________
>>>> To unsubscribe, edit your list preferences, or view the list
>>>> archives, please visit:
>>>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>>>>
>>>>
>>> _______________________________________________
>>> To unsubscribe, edit your list preferences, or view the list
>>> archives, please visit:
>>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>>
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list
>> archives, please visit:
>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>>
>>
>
>
> --
> - Ben Davison
> - http://www.shadow-phoenix.com
> --
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list
> archives, please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to