On Mon, Oct 22, 2012 at 10:47 AM, Staffan Tylen <staffan.ty...@gmail.com>wrote:
>
>> >From what you posted earlier, I think vcvarsall.bat should be in:
>>
>> c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC
>>
>> for you.
>>
>> Getting this to work, can be a little bit of a pain. But, once you get
>> it to work, it is a big benefit.
>>
>>
> OK, I took the bull by the horn and tried a few things out.
Hi Staffan,
It's a beginning, but probably not a good one. Some of the warnings are
new and not good ones.
c:\program files\microsoft sdks\windows\v7.1\include\sal_supp.h(57) :
warning C4005: '__useHeader' : macro redefinition
This is probably harmless, but it indicates the build environment is still
not correct. I wouldn't move vcvarsall.bat and edit it.
First take a look and see if you can uninstall Visual Studio 10.0 from the
control panel. That is, see if there is still an entry for it in Programs
and features. If so remove it.
If its not there, then just do this:
Open up a command prompt window. Do not run the SDK setenv.cmd at all.
Rather, just run the vcvarsall.bat file from its installed location. Then
in that same window, run the build with your one modification to
ooSQLITE_BLD_LVL.
You should see the same warnings as before, but you should not see any
macro redefinition warnings.
Visual Studio includes a version of the SDK. The only reason to add the
SDK to the build environment is if the SDK is newer than your Visual
Studio. But in your case, Visual Studio 11.0 is newer than the SDK, so you
should just not add the SDK to your build environment.
The short of it is, just use the Visual Studio 11.0 vcvarsall.bat to set
your build environment and leave the SDK out of it.
Of course there is one other complication here. It could be that you had
installed Visual Studio 10.0 so that it permanently added its build
variables to the environment.
Open a command prompt window and test the include variable *before* you run
vcvarsall.bat:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\work.ooRexx>set include
Environment variable include not defined
C:\work.ooRexx>set lib
Environment variable lib not defined
C:\work.ooRexx>
As you can see on my system, there is no INCLUDE or LIB set before I run
one of the setup commands for VC++ or the SDK. Then after I run a set up
command:
C:\work.ooRexx>\Tools\VisualStudio.10.0\vc\vcvarsall.bat x64
Setting environment for using Microsoft Visual Studio 2010 x64 tools.
C:\work.ooRexx>set include
INCLUDE=c:\Tools\VisualStudio.10.0\VC\INCLUDE;c:\Tools\VisualStudio.10.0\VC\ATLMFC\INCLUDE;C:\Program
Files (x86
)\Microsoft SDKs\Windows\v7.0A\include;
C:\work.ooRexx>set lib
LIB=c:\Tools\VisualStudio.10.0\VC\LIB\amd64;c:\Tools\VisualStudio.10.0\VC\ATLMFC\LIB\amd64;C:\Program
Files (x86
)\Microsoft SDKs\Windows\v7.0A\lib\x64;
LIBPATH=C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Windows\Microsoft.NET\Framework64\v3.5;c:\Tools\Visua
lStudio.10.0\VC\LIB\amd64;c:\Tools\VisualStudio.10.0\VC\ATLMFC\LIB\amd64;
C:\work.ooRexx>
If you see that LIB or INCLUDE are already set *before* you run
vcvarsall.bat then you need to somehow clean things up. Maybe you just
forgot to uninstall Visual Studio 10 before you installed 11? If you can
still do an uninstall from the Control Panel, then that will be the best
option for you.
--
Mark Miesfeld
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
