In general it works like this. When you run the setup script
(edksetup.sh/edksetup.bat) it copies
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/BaseTools/Conf/tools_def.template
to your Conf/tools_def.txt if one does not exits. The supported toolchains are
looked up from your Conf/tools_def.txt file:
The variables are in the form of:
TARGET_TOOLCHAIN_ARCH_COMMANDTYPE_ATTRIBUTE
If you look in the Conf/tools_def.txt you will not see VS2012 options, just
VS2010 options. So you probably need to clone a VS2010 option and make a
VS2012 option. While the options may be the same, the path to the tools look
like they change:
DEFINE VS2008_BIN = C:\Program Files\Microsoft Visual Studio 9.0\Vc\bin
DEFINE VS2008_DLL = C:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE;DEF(VS2008_BIN)
DEFINE VS2008_BINX64 = DEF(VS2008_BIN)\x86_amd64
DEFINE VS2008_BIN64 = DEF(VS2008_BIN)\x86_ia64
DEFINE VS2008x86_BIN = C:\Program Files (x86)\Microsoft Visual Studio
9.0\Vc\bin
DEFINE VS2008x86_DLL = C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\IDE;DEF(VS2008x86_BIN)
DEFINE VS2008x86_BINX64 = DEF(VS2008x86_BIN)\x86_amd64
DEFINE VS2008x86_BIN64 = DEF(VS2008x86_BIN)\x86_ia64
DEFINE VS2010_BIN = C:\Program Files\Microsoft Visual Studio 10.0\Vc\bin
DEFINE VS2010_DLL = C:\Program Files\Microsoft Visual Studio
10.0\Common7\IDE;DEF(VS2010_BIN)
DEFINE VS2010_BINX64 = DEF(VS2010_BIN)\x86_amd64
DEFINE VS2010_BIN64 = DEF(VS2010_BIN)\x86_ia64
DEFINE VS2010x86_BIN = C:\Program Files (x86)\Microsoft Visual Studio
10.0\Vc\bin
DEFINE VS2010x86_DLL = C:\Program Files (x86)\Microsoft Visual Studio
10.0\Common7\IDE;DEF(VS2010x86_BIN)
DEFINE VS2010x86_BINX64 = DEF(VS2010x86_BIN)\x86_amd64
DEFINE VS2010x86_BIN64 = DEF(VS2010x86_BIN)\x86_ia64
For a quick hack you could try changing the path for the VS2010 to point to the
VS2012 tools and see if that works.
Andrew Fish
On May 24, 2013, at 1:29 PM, "Gamez Gonzalez, Edgar Ivan A"
<edgar.ivan.a.gamez.gonza...@intel.com> wrote:
>
> Hi, I’m trying to build NT32 project on Visual Studio 2012.
> Now I’m stuck with target.txt, I do not know how to write the tagname
> TOOL_CHAIN_TAG = ?
> Im getting this error:
> :error 4000: Not available
> [VS2012] not defined. No toolchain available for build!
>
> Thanks for your support.
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
