Mercurial > hg > graal-compiler
diff make/windows/create.bat @ 91:a294fd0c4b38
6583644: Move all managed/SCCS files out of 'build' into 'make' directory
Summary: Moved makefiles out of build and build/closed into make/
Reviewed-by: kvn, ohair
author | kamg |
---|---|
date | Wed, 09 Apr 2008 14:22:48 -0400 |
parents | build/windows/create.bat@a61af66fc99e |
children | d1605aabd0a1 |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/make/windows/create.bat Wed Apr 09 14:22:48 2008 -0400 @@ -0,0 +1,179 @@ +@echo off +REM +REM Copyright 1999-2006 Sun Microsystems, Inc. All Rights Reserved. +REM DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. +REM +REM This code is free software; you can redistribute it and/or modify it +REM under the terms of the GNU General Public License version 2 only, as +REM published by the Free Software Foundation. +REM +REM This code is distributed in the hope that it will be useful, but WITHOUT +REM ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +REM FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +REM version 2 for more details (a copy is included in the LICENSE file that +REM accompanied this code). +REM +REM You should have received a copy of the GNU General Public License version +REM 2 along with this work; if not, write to the Free Software Foundation, +REM Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. +REM +REM Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, +REM CA 95054 USA or visit www.sun.com if you need additional information or +REM have any questions. +REM +REM + +REM This is the interactive build setup script (as opposed to the batch +REM build execution script). It creates $HotSpotBuildSpace if necessary, +REM copies the appropriate files out of $HotSpotWorkSpace into it, and +REM builds and runs MakeDeps in it. This has the side-effect of creating +REM the vm.vcproj file in the buildspace, which is then used in Visual C++. +REM +REM The generated project file depends upon the include databases. If +REM those are changed then MakeDeps is rerun. + +REM +REM Since we don't have uname and we could be cross-compiling, +REM Use the compiler to determine which ARCH we are building +REM +cl 2>&1 | grep "IA-64" >NUL +if %errorlevel% == 0 goto isia64 +cl 2>&1 | grep "AMD64" >NUL +if %errorlevel% == 0 goto amd64 +set ARCH=x86 +set BUILDARCH=i486 +set Platform_arch=x86 +set Platform_arch_model=x86_32 +goto end +:amd64 +set ARCH=x86 +set BUILDARCH=amd64 +set Platform_arch=x86 +set Platform_arch_model=x86_64 +goto end +:isia64 +set ARCH=ia64 +set BUILDARCH=ia64 +set Platform_arch=ia64 +set Platform_arch_model=ia64 +:end + +setlocal + +if "%1" == "" goto usage + +if not "%4" == "" goto usage + +set HotSpotWorkSpace=%1 +set HotSpotBuildSpace=%2 +set HotSpotJDKDist=%3 + +REM figure out MSC version +for /F %%i in ('sh %HotSpotWorkSpace%/make/windows/get_msc_ver.sh') do set %%i + +echo ************************************************************** +if "%MSC_VER%" == "1200" ( +set ProjectFile=vm.dsp +echo Will generate VC6 project {unsupported} +) else ( +set ProjectFile=vm.vcproj +echo Will generate VC7 project +) +echo %ProjectFile% +echo ************************************************************** + +REM Test all variables to see whether the directories they +REM reference exist + +if exist %HotSpotWorkSpace% goto test1 + +echo Error: directory pointed to by HotSpotWorkSpace +echo does not exist, or the variable is not set. +echo. +goto usage + +:test1 +if exist %HotSpotBuildSpace% goto test2 +if not "%HotSpotBuildSpace%" == "" mkdir %HotSpotBuildSpace% +if exist %HotSpotBuildSpace% goto test2 +echo Error: directory pointed to by HotSpotBuildSpace +echo does not exist, or the variable is not set. +echo. +goto usage + +:test2 +if exist %HotSpotJDKDist% goto test3 +echo Error: directory pointed to by %HotSpotJDKDist% +echo does not exist, or the variable is not set. +echo. +goto usage + +:test3 +if not "%HOTSPOTMKSHOME%" == "" goto makedir +echo Warning: please set variable HOTSPOTMKSHOME to place where +echo your MKS/Cygwin installation is +echo. +goto usage + +:makedir +echo NOTE: Using the following settings: +echo HotSpotWorkSpace=%HotSpotWorkSpace% +echo HotSpotBuildSpace=%HotSpotBuildSpace% +echo HotSpotJDKDist=%HotSpotJDKDist% + + +REM This is now safe to do. +:copyfiles +for /D %%i in (compiler1, compiler2, tiered, core, kernel) do ( +if NOT EXIST %HotSpotBuildSpace%\%%i mkdir %HotSpotBuildSpace%\%%i +copy %HotSpotWorkSpace%\make\windows\projectfiles\%%i\* %HotSpotBuildSpace%\%%i\ > NUL +) + +REM force regneration of ProjectFile +if exist %HotSpotBuildSpace%\%ProjectFile% del %HotSpotBuildSpace%\%ProjectFile% + +for /D %%i in (compiler1, compiler2, tiered, core, kernel) do ( + +echo # Generated file! > %HotSpotBuildSpace%\%%i\local.make +echo # Changing a variable below and then deleting %ProjectFile% will cause >> %HotSpotBuildSpace%\%%i\local.make +echo # %ProjectFile% to be regenerated with the new values. Changing the >> %HotSpotBuildSpace%\%%i\local.make +echo # version requires rerunning create.bat. >> %HotSpotBuildSpace%\%%i\local.make +echo. >> %HotSpotBuildSpace%\%%i\local.make +echo HOTSPOTWORKSPACE=%HotSpotWorkSpace% >> %HotSpotBuildSpace%\%%i\local.make +echo HOTSPOTBUILDSPACE=%HotSpotBuildSpace% >> %HotSpotBuildSpace%\%%i\local.make +echo HOTSPOTJDKDIST=%HotSpotJDKDist% >> %HotSpotBuildSpace%\%%i\local.make +echo ARCH=%ARCH% >> %HotSpotBuildSpace%\%%i\local.make +echo BUILDARCH=%BUILDARCH% >> %HotSpotBuildSpace%\%%i\local.make +echo Platform_arch=%Platform_arch% >> %HotSpotBuildSpace%\%%i\local.make +echo Platform_arch_model=%Platform_arch_model% >> %HotSpotBuildSpace%\%%i\local.make + +REM build config specific stuff + +pushd %HotSpotBuildSpace%\%%i +nmake /nologo +popd +) + +goto end + +:usage +echo Usage: create HotSpotWorkSpace HotSpotBuildSpace HotSpotJDKDist +echo. +echo This is the interactive build setup script (as opposed to the batch +echo build execution script). It creates HotSpotBuildSpace if necessary, +echo copies the appropriate files out of HotSpotWorkSpace into it, and +echo builds and runs MakeDeps in it. This has the side-effect of creating +echo the %ProjectFile% file in the build space, which is then used in Visual C++. +echo The HotSpotJDKDist defines place where JVM binaries should be placed. +echo Environment variable FORCE_MSC_VER allows to override MSVC version autodetection. +echo. +echo The generated project file depends upon the include databases. If +echo those are changed then MakeDeps is rerun. +echo. +echo NOTE that it is now NOT safe to modify any of the files in the build +echo space, since they may be overwritten whenever this script is run or +echo nmake is run in that directory. + +:end + +endlocal