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 researc
--
[ 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 t
Yes, VS.NET 2003 is still our primary development platform. VS.NET 2005 is a
part of our 64-bit port efforts.
- Alfred
Teddy wrote:
> Will the SDK still be compaible with VS.NET 2003?
>
> On 11/16/05, Alfred Reynolds <[EMAIL PROTECTED]> wrote:
>> What pleas? We are working on an update to get th
Will the SDK still be compaible with 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 2005, this should help with GCC 4.x also.
>
> - Alfred
>
> Ondrej Hošek wrote:
> > It went along the l
The SDK launcher application does more than just deliver the SDK Source files,
it processes them also. So no, it wouldn't make sense to deliver them via the
linux client, you need to copy them yourself.
As for utils/common/threads.cpp, we don't have a Linux port of that file as we
don't have an
I quote from my previous e-mail:
"Firstly, are there any hopes of the SDK source code being accessible
via the Linux Steam client too sometime, maybe as a "game" restricted to
HL2 buyers? I deduced from the readme file that this should be now
possible if a username and password is supplied.
"Sec
What pleas? We are working on an update to get the code base to compile under
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. Seem
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 .di
Source SDK requires gcc-3.4, so we should be safe with gcc-4.0.
The main problem is that gcc-4.0 complais about a lot of stuff in the
sdk that 3.4 does not :)
I would really like to experiment recompiling my stuff with gcc 4.0 and
see if the code it generates is faster.
On Wed, 2005-11-16 at 09:4
The Source engine and Steam client are compiled with 3.4.1 currently.
- Alfred
Jeff Fearn wrote:
> On 11/16/05, Marcelo Bezerra <[EMAIL PROTECTED]> wrote:
>> On Tue, 2005-11-15 at 13:51 -0800, Alfred Reynolds wrote:
>>> C++ interfaces are passed from it to our GCC 3.x compiled binaries).
>>> How
On 11/16/05, Marcelo Bezerra <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-11-15 at 13:51 -0800, Alfred Reynolds wrote:
> > C++ interfaces are passed from it to our GCC 3.x compiled binaries).
> > How did you solve that?
>
> gcc-4.0 and gcc-3.4 share the same C++ ABI, so that should not be a
> problem.
On Tue, 2005-11-15 at 13:51 -0800, Alfred Reynolds wrote:
> C++ interfaces are passed from it to our GCC 3.x compiled binaries).
> How did you solve that?
gcc-4.0 and gcc-3.4 share the same C++ ABI, so that should not be a
problem.
___
To unsubscribe,
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 hav
13 matches
Mail list logo