Thanks - I'll look into that.
On 7 May 2018 at 20:14, Tobias Kammersgaard
wrote:
> LC_ID is no longer a thing. You will run into problems because you can't
> link with the libraries in the Source SDK. They're not compatible with
> VS2017.
>
> However if you want to avoid installing multiple vers
You can get compilers without installing visual studio iirc
>Понедельник, 7 мая 2018, 12:29 +03:00 от Tom Schumann
>:
>
>I'm specifically trying to avoid running multiple versions of Visual Studio
>for the sake of one project.
>
>On 7 May 2018 at 15:47, Francisco Javier Bizcocho Antúnez <
>volk
I'm specifically trying to avoid running multiple versions of Visual Studio
for the sake of one project.
On 7 May 2018 at 15:47, Francisco Javier Bizcocho Antúnez <
volkovda...@gmail.com> wrote:
> You are not gaining anything by using VS2017, all the relevant engine
> functionality is already com
You are not gaining anything by using VS2017, all the relevant engine
functionality is already compiled. You're only getting the burden of making
it work with a compiler with a different C++ runtime. Just install VS2013
compiler and all the issues will go away.
On Mon, 7 May 2018 at 06:41, Tom Schu
Well that got me a bit further - looks like _CRTNOALIAS was defined as
nothing (based on https://doxygen.reactos.org/d7/d45/crtdefs_8h_source.html
).
Also, pthreadmbcinfo is now struct __crt_multibyte_data*, pthreadlocinfo is
now struct __crt_locale_data*, _locale_tstruct is now _locale_t
and _cr
Possibly but I've compiled Source plugins without issue (I just didn't use
the custom memory management for them).
Anyway, looks like _CRTNOALIAS was probably defined in a previous version
of Visual Studio but not longer is. It looks like it should be #define
_CRTNOALIAS __declspec(noalias)
On 7 M
Usually mixing projects that are compiled with different versions of VS
brings nothing but problems. Even if you manage to compile and link you can
always have runtime issues. The C++ runtimes are dufferent. So rule of the
thumb: use the same compiler to avoid this kind of issues.
On Sun, 6 May 20
Somebody with the same issue:
http://www.interlopers.net/forum/viewtopic.php?f=2&t=16578
Try asking on there if you do not end up with a solution on this mailing
list.
On 06/05/2018 23:46, Tom Schumann wrote:
I'm trying to compile https://github.com/ValveSoftware/source-sdk-2013 in
Visual Stu
I'm trying to compile https://github.com/ValveSoftware/source-sdk-2013 in
Visual Studio 2017 which I know isn't supported, but I've generated a .sln
using the fix at https://developer.valvesoftware.com/wiki/Source_SDK_2013,
but I get compile errors which I can't figure.
Most of the problems seem to
9 matches
Mail list logo
