38 Commits

Autor SHA1 Mensagem Data
craig.schlenter@chromium.org 00b8e8569b Add .fragment and .sigs to non-compilable suffixes.
This fixes the shared build on Linux after r18122.

Review URL: http://codereview.chromium.org/123015

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18365 0039d316-1c4b-4281-b951-d872f2087c98
2009-06-14 18:34:33 +00:00
sgk@google.com 0dc017427b Don't try to compile .mk files when building shared libraries
(to exclude third_party/skia/src/core/core_files.mk).
Review URL: http://codereview.chromium.org/115320

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15999 0039d316-1c4b-4281-b951-d872f2087c98
2009-05-13 21:17:28 +00:00
sgk@google.com 933d672967 When env.Replace() is getting called with a list of Nodes, use a slice to
replace the old list element with the new list.  This keeps the list of
files flattened and lets the later Builder calls remove the file names
with non-linkable/non-compilable suffixes (.h) from the list.

Add .gperf to the list of non-{compil,link}able suffixes.
Review URL: http://codereview.chromium.org/89003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14064 0039d316-1c4b-4281-b951-d872f2087c98
2009-04-20 22:05:26 +00:00
tc@google.com 51b65d2d04 Save space and time by having files build directly in their final
destination rather than once in obj then copied to the top level
src directory.

Roll deps to pick up DISTCC/CCACHE fix.

Review URL: http://codereview.chromium.org/56194


git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13042 0039d316-1c4b-4281-b951-d872f2087c98
2009-04-02 22:26:04 +00:00
sgk@google.com 8002191ee6 Remove Hammer files.
Updates chromium_builders.py to remove import and use of deleted module.
Review URL: http://codereview.chromium.org/42667

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12987 0039d316-1c4b-4281-b951-d872f2087c98
2009-04-01 22:23:13 +00:00
sgk@google.com 088f3157fa Checked in wrong copy.
Review URL: http://codereview.chromium.org/56163

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12985 0039d316-1c4b-4281-b951-d872f2087c98
2009-04-01 22:09:52 +00:00
sgk@google.com d171a71d4b Change uses of the SCons Install() builder to 'cp' inside the
Chromium infrastructure, too.
Review URL: http://codereview.chromium.org/60030

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12984 0039d316-1c4b-4281-b951-d872f2087c98
2009-04-01 22:05:52 +00:00
sgk@google.com b73fae7a37 Build in a ../sconsbuild directory by default:
* Deps roll for ../sconsbuild support in gyp.
* Add a 'scons_settings': { 'sconsbuild_dir' } setting to common.gypi.
* Change uses of $DESTINATION_ROOT to $TOP_BUILDDIR.
Review URL: http://codereview.chromium.org/53133

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12636 0039d316-1c4b-4281-b951-d872f2087c98
2009-03-27 04:27:01 +00:00
sgk@google.com f955e6aaa1 Prep for gyp conversion: cut-and-paste the FileList base class that chromium_builders.py was using from the (soon-to-be-removed) module that generates VisualStudio files from the SCons configuration.
Review URL: http://codereview.chromium.org/53107

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12592 0039d316-1c4b-4281-b951-d872f2087c98
2009-03-26 20:01:55 +00:00
sgk@google.com ddd4fc30c3 Update Linux gyp build to import and propagate external environment
variables ($CC, $DISTCC_DIR, $HOME, etc.).
Accomodate spelling change ($CHROME_SRC_DIR => $SRC_DIR) that
makes the gyp SCons a little more generic.
Use the new $LIB_DIR variable the gyp SCons generator now defines for us.
Review URL: http://codereview.chromium.org/42650

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12583 0039d316-1c4b-4281-b951-d872f2087c98
2009-03-26 18:58:10 +00:00
sgk@google.com 150b0bf00b Update the gyp Linux build:
* Add Linux settings to target_defaults in common.gypi so
  gyp-generated SConscript files no longer depend on
  build/SConscript.main or the Hammer infrastructure.
* Copy the FilterOut() function from Hammer to the chromium_builders.py
  Tool module.
* Add a ChromiumLoadableModule() builder to chromium_builders.py.
* Add dependencies on the 'views' library to the chrome link (target 'app').
* Add missing views/*/*_unittest.cc modules to the 'unit_tests' target.
  Exclude all but the one that builds on Linux from the non-Windows builds.
* Crib a list of chrome/views files to exclude from the Linux build
  from the old SCons configuration.
* Add a new build/linux/system.gyp file with new 'settings' targets
  to encapsulate the pkg-config checks for gtk+-2.0, nss and pangoft2.
* Add depenedencies in the other targets on the new gtk, nss and
  pangoft2 'settings' targets from build/linux/system.gyp.
* Add a pkg_config_wrapper.py script that keeps gyp happy by
  simply exiting 0 if the package isn't found.
* DEPS roll for latest gyp changes to support the above.
Review URL: http://codereview.chromium.org/42340

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12228 0039d316-1c4b-4281-b951-d872f2087c98
2009-03-20 23:13:26 +00:00
sgk@google.com 86394aa8c5 Have the gyp build use base SCons, not Hammer components, so it can
control the Alias namespace directly and set appropriate default targets.
This currently switches within the various Chrome*() calls.
Review URL: http://codereview.chromium.org/46037

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11657 0039d316-1c4b-4281-b951-d872f2087c98
2009-03-13 19:42:26 +00:00
evan@chromium.org bfacc94e2e Add to and sort the list of non-compilable suffixes.
Review URL: http://codereview.chromium.org/21286


git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9659 0039d316-1c4b-4281-b951-d872f2087c98
2009-02-12 17:07:34 +00:00
tc@google.com 7a43e3c670 Add a Repack tool to scons. This is used to compile linux resources
together (kind of like the windows RES builder).

I also moved the GRIT builder into the chromium site_scons since we
import it in lots of places.  This seems cleaner.

Review URL: http://codereview.chromium.org/21115


git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9331 0039d316-1c4b-4281-b951-d872f2087c98
2009-02-06 20:17:54 +00:00
sgk@google.com 85952ad232 Exclude .idl files from the generated compilable files lists.
Review URL: http://codereview.chromium.org/16614

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8426 0039d316-1c4b-4281-b951-d872f2087c98
2009-01-22 00:45:17 +00:00
sgk@google.com 35daf5f024 Generate all chrome .vcproj files:
* Path name translation (/ to \) of various MSVSTool attributes.
* Explicit keyword= arguments to MSVSProject.  This will likely
  go away eventually in favor of uniform behavior.
* Add a relative_path_substitutions array that can be used
  to substitute in Visual Studio variable like $(OutDir).
* Add a local_directory_prefix that can be set to './' to only
  affect files in the current directory.
* Additional Keyword ordering in Tool attributes to continue to
  match the default order Visual Studio generates.
* Add a Derived() proxy class that can wrap a File node to tell
  the .vcproj generation that we want the derived file, not its
  source(s), in the file list.
* In the individual *.scons files, add the necessary files (mostly
  .h files) to file lists, and update MSVSProject() calls with
  the additional necessary information.

Result is identical .vcproj files modulo the following differences:

* Four locales .vcproj files (da, en-US, he and zh-TW) with
  source file orders that don't match the other locale .vcproj
  files have re-ordered file lists to match the rest.
* Cosmetic XML changes (white space, ending tags) in:
    chrome/app/chrome_dll.vcproj
    chrome/app/generated_resources.vcproj
    net/build/net_resources.vcproj
* Removal or addition of ./ prefixes from various files that don't
  match the other file specifications within their individual
  .vcproj files:
    chrome/installer/util/util.vcproj
    net/build/net.vcproj
    net/build/net_unittests.vcproj
* Add missing empty sections (<ToolFiles>, <References>, <Globals>)
  for consistency with other .vcproj files:
    chrome/tools/test/image_diff/image_diff.vcproj
    third_party/libpng/libpng.vcproj
    third_party/zlib/zlib.vcproj
* Add missing RootNameSpace attribute:
    chrome/test/automation/automation.vcproj
    testing/gtest.vcproj
* Use && instead of \r\n as a command separator, to sidestep
  XML-generation problems:
    chrome/app/chrome_exe.vcproj
* Remove unnecessary (?) duplicate files in the file list:
    chrome/browser/views/browser_views.vcproj
      (event_utils.cc and event_utils.h were duplicated)
  
Review URL: http://codereview.chromium.org/17603

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8253 0039d316-1c4b-4281-b951-d872f2087c98
2009-01-17 02:25:22 +00:00
sgk@google.com 32c8f3e749 Updates to Visual Studio project generation to accomodate
recent changes and get rid of cut-and-paste:

* Add generation of the new net_resource.vcproj file.
* Accomodate the net\net.vsprops file.
* New base.vcproj dependency in activex_shim_dll.vcproj.
* New tld_cleanup.vcproj dependency in net.vcproj.
* New ondemand_updates.vcproj dependencies in
  gcapi_{dll,lib}.vcproj.
* Re-order dump_cache.vcproj dependencies to match new
  checked-in solutions.
* New input file directory layout in zlib (minizip folder)
  and testing\gtest (hierarchy).
* Use a new dest= argument to ChromeMSVSSolution()
  and ChromeMSVSProject() to get rid of cut-and-pste
  installation code, and provide a central point for
  controlling when/whether we want to generate the files
  only under the build directory, or drop them in place
  for checking in.
* Comment out an unnecessarily verbose warning if the
  buildtarget is executed with an action that we don't
  map to specific Visual Studio settings.  Sometimes
  this is normal and okay, but the warning should get
  restored at some point when we work out the precise
  conditions under which it makes sense.
Review URL: http://codereview.chromium.org/17602

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7856 0039d316-1c4b-4281-b951-d872f2087c98
2009-01-10 22:22:33 +00:00
sgk@google.com 0df423c5b5 Resubmit r7826 after fixing breakages:
Generation of net .vcproj and .sln files.

Specific changes:
* Add to MSVSProject() calls:  GUID, input_files list,
  tools list (that are common to the individual configurations).
* Add *.h files and MSVSFilter() hierarchies to input_files lists.
* Switch to using the .Remove() method for instead of by-hand
  Python to remove things from input_files lists.
* Use of precompiled header files still requires separate by-hand
  Configuration specifications.
* Remove .dat files from the input file lists when compiling.
* Extensive _Node_MSVS.py changes that set us up for deducing this
  information from parallel Debug and Release builds instead of
  configuring things by hand, basically by delaying evaluation of
  most of the strings, then introspecting on the command lines
  that will be used to generate the targets and translating
  compiler and linker options into Visual Studio settings.

The result is (again) byte-for-byte identical .vcproj files, modulo
removal of a ".\" current-directory prefix for a few RelativePath
specifications.
Review URL: http://codereview.chromium.org/17478

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7854 0039d316-1c4b-4281-b951-d872f2087c98
2009-01-10 17:53:34 +00:00
mark@chromium.org c1800053dc Back out r7826, which broke the Linux build
Review URL: http://codereview.chromium.org/17327

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7830 0039d316-1c4b-4281-b951-d872f2087c98
2009-01-09 21:03:03 +00:00
sgk@google.com a5c1d4b095 Generation of net .vcproj and .sln files.
Specific changes:
* Add to MSVSProject() calls:  GUID, input_files list,
  tools list (that are common to the individual configurations).
* Add *.h files and MSVSFilter() hierarchies to input_files lists.
* Switch to using the .Remove() method for instead of by-hand
  Python to remove things from input_files lists.
* Use of precompiled header files still requires separate by-hand
  Configuration specifications.
* Remove .dat files from the input file lists when compiling.
* Extensive _Node_MSVS.py changes that set us up for deducing this
  information from parallel Debug and Release builds instead of
  configuring things by hand, basically by delaying evaluation of
  most of the strings, then introspecting on the command lines
  that will be used to generate the targets and translating
  compiler and linker options into Visual Studio settings.

The result is (again) byte-for-byte identical .vcproj files, modulo
removal of a ".\" current-directory prefix for a few RelativePath
specifications.
Review URL: http://codereview.chromium.org/17436

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7826 0039d316-1c4b-4281-b951-d872f2087c98
2009-01-09 20:35:47 +00:00
evanm@google.com b852cefdce Add a ChromeLibrary builder that allows the environment to decide whether
we link statically or dynamically.

Review URL: http://codereview.chromium.org/16269


git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7477 0039d316-1c4b-4281-b951-d872f2087c98
2008-12-26 04:07:02 +00:00
sgk@google.com 865a6dd746 Initial subset of .vcproj file generation, covering generation of:
base\build\base.vcproj
  base\build\base_gfx.vcproj
  base\build\base_unittests.vcproj
  base\build\debug_message.vcproj
  skia\skia.vcproj
  testing\gtest.vcproj
  third_party\icu38\icu.vcproj
  third_party\icu38\icudt.vcproj
  third_party\libpng\libpng.vcproj
  third_party\zlib\zlib.vcproj

Supporting work in *.scons files:
* Adds .h files to the input_files lists in the various *.scons files.
* Add arguments to ChromeMSVSProject() to actually generate the
  .vcproj files.
* Add MSVS.AddConfig() calls to the *.scons files to preserve the
  .vsprops inclusion in the generated .vcproj files.
  (These will go away eventually as we migrate away from .vsprops
  in favor of using the settings from the SCons configuration.)
* Add MSVS.AddConfig() calls to preserve the .vsprops inclusion.
* Move the special generation of dmg_fp/*.cc files ahead of the
  input file list so we can list the generated object files.
* Change the 'solutions' Alias to 'msvs' so we don't mislead about
  what will actually be generated.

Updates to the new _Node_MSVS.py module with latest from upstream
prototype development:
  * Support configurability of:
    * buildtarget (used to generat project name)
    * RootNamespace
    * relative_path_prefix (to prepend './')
    * tools (to avoid repetition in the project configs)
  * Track the Visual Studio hierarchy in SCons Nodes, not DOM,
    so we can delay evaluation until after the complete
    configuration has been specified.
  * Add a FileList base class for the things that need, with a
    subclass hierarchy for the different concrete things in our tree,
    and a FileListWalk() function for traversing hierarchies.
  * Centralize turning strings into Nodes in the args2nodes() method
    and have AddFiles() just use it.

Updates to chromium_builders.py to support all this
  * Add knowledge about stripping out noncompilable files
    (.h files) from input_files lists.
  * Return a Null() class if we're not generating MSVS files
    so we don't have to hide the other calls in if:-blocks.
  * Add custom ChromeFileList subclass of MSVS.FileList as a
    container for the file list manipulation we need to do.
  * Move the Chrome*() function definitions out to global space,
    and just use the generate() function for adding them to
    the passed-in environment as class methods.

* Make a change to SCons (in Node/FS.py) to handle polymorphism in
  the new MSVS Node hierarchy.
Review URL: http://codereview.chromium.org/16447

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7467 0039d316-1c4b-4281-b951-d872f2087c98
2008-12-24 03:20:00 +00:00
sgk@google.com a32cb7e0c8 Initial generation of native Visual Studio solution files
(project files still to come).  To wit:
* Solution file configuration is in *_sln.scons files (base\base_sln.scons,
  chrome\chrome_sln.scons).
* Individual Project file configuration is in the the .scons file for
  the relevant target (base\base_unittests.scons,
  third_party\libxml\libxml.scons, etc.)--that is, where their file
  lists will live.
* MSVSProject() calls are currently placeholders that establish
  the existence of Project Nodes (and Project dependencies) but don't yet
  have actual Project configuration information (file lists, .vsprops, etc.).
* Configuraiton is very manual.  In particular, the entries in the .sln
  file will be written out in exactly the order specified in the
  configuration(s).  The current ordering is taken from our existing
  .sln files, so we can generate virtually the same configurations
  on output.
* Generated solution files are nearly byte-for-byte identical
  with our existing .sln files, modulo:
  * net\dump_cache has a WebsiteProperties sections (making that
    configurable per project isn't important right now);
  * sandbox\sandbox.sln was missing a dependency of base.vcproj on
    on debug_message.vcproj (present in other .sln files)
  * webkit\webkit.sln was missing dependencies of WebCore.vcproj on
    libxml_config.vcproj and libxslt_config.vcproj (present in
    chrome.sln);
  * add a handful of other miscellaneous missing dependencies on various
    .vcproj definitions in chrome.sln (present in other .sln files).
  * remove stats_viewer.csproj from chrome.sln (sorry, mbelshe),
    which was complicating the solution configuration with unnecessary
    (for us) "Mixed Platform" types;
* All MSVSFolder(), MSVSProject() and MSVSSolution() calls have
  hard-wired guid= values taken from our existing configuration,
  so we can: 1) verify generation of working configs; 2) minimize
  diffs when checking in generated .sln files.  We can remove
  these in the future in favor of extracting them from existing
  .sln files if we wish.
* Add ChromeMSVSFolder(), ChromeMSVSProject() and ChromeMSVSSolution()
  wrappers to chromium_builders.py, that gate the underlying call to
  the env.MSVS*() builders based on whether env.Bit('msvs') is set
  (i.e., we're in --mode=msvs).
* Remove platform-specific gating of to-be-ported .scons files that we
  now need to load on any platform to generate coheren MSVS files.
  Move the env.Bit('windows') tests for actually building their
  executables into the individual .scons files.


Review URL: http://codereview.chromium.org/14472

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7297 0039d316-1c4b-4281-b951-d872f2087c98
2008-12-19 08:10:30 +00:00
sgk@google.com 740e39dc77 Underlying functionality for generating native Visual Studio solution files:
* New _Node_MSVS.py module (from rspangler) with new MSVSFolder(),
  MSVSProject() and MSVSSolution() Nodes.  This will eventually
  become a new SCons/Node/MSVS.py module in upstream SCons.
* New MSVSNew.py Tool module imports MSVS.py (either from SCons.Node
  or from our temporary _Node_MSVS.py module) and attaches the
  appropriate environment methods.
* MSVSSolution().Write() will generate a solution file based on
  explicit configuration in the SConscript files.
* While we're here, define $SQLITE_DIR, which will be used by
  the next checkins.
Review URL: http://codereview.chromium.org/14467

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7120 0039d316-1c4b-4281-b951-d872f2087c98
2008-12-17 01:10:16 +00:00
bradnelson@chromium.org 43ba76f5ef Pulling in hammer changes.
Review URL: http://codereview.chromium.org/13134

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6370 0039d316-1c4b-4281-b951-d872f2087c98
2008-12-04 19:35:47 +00:00
sgk@google.com 7bef9ef9cc Fixes and enhancements
* Configurable CHROME_BUILD_TYPE command line or external environment
  variable for selecting appropriate release_impl*.scons settings
  (_checksenabled, _coverage, _dom_stats, _official, _purify).
* Configurable CHROMIUM_BUILD command line or external environment
  variable for selecting appropriate chromium_build*.scons settings
  (_google_chrome).
* Configurable /INCREMENTAL linking via command line or external
  environment variable ($INCREMENTAL), through appropriate setting
  of an internal $CHROMIUM_INCREMENTAL_FLAGS construction variable.
* Full link of release builds by default.
* Alphabetize *.scons files in the mac_env.FilterOut() list.
* Explicitly set _checksenabled.scons link flags.
Review URL: http://codereview.chromium.org/13039

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6210 0039d316-1c4b-4281-b951-d872f2087c98
2008-12-02 07:36:03 +00:00
sgk@google.com e257d2668c Fix use of LOAD= with WantSystemLib() (we could blow up if a variable
hadn't been added to the config) and extend use of LOAD= into submodules:
* Add a ChromeLoadSConscriptModules() method that encapsulates the
  conditional logic, and makes things more readable by specifying
  component names as keyword arguments, not hard-coding the logic
  as a series of if-tests.
* Put the ChromeLoadSConscriptModules() logic in a Tool module in
  site_scons/site_tools, so it doesn't clutter up
  build/SConscript.main directly.
* Move env.WantSystemLib() calls into the individual *.scons files,
  so we call them each time (or not, based one LOAD=) and the config
  itself just returns if the system library is requested and we
  don't need to build anything locally.
* Move the settings where a library name changes based on whether or
  not the system lib is being used into the using_*.scons files,
  so they're available to clients independently of whether or not the
  component's *.scons configuration is loaded.
* While here:  rename the affected third_party SConscript files:
  third_party/libjpeg/SConscript => third_party/libjpeg/libjpeg.scons
  third_party/libxml/SConscript => third_party/libxml/libxml.scons
  third_party/libxslt/SConscript => third_party/libxslt/libxslt.scons
* While here:  move the Chrome{Program,SharedLibrary}() etc. builder
  definitions from build/SConscript.main to a new too
  Ad the ChromeLoadSConscriptModules() logic in a Tool module,
  to remove more clutter from build/SConscript.main.
Review URL: http://codereview.chromium.org/11430

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5820 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-21 06:04:04 +00:00
sgk@google.com d9c273a7b8 Fixes for Visual Studio solution + project file generation:
* Fix the grit tool so it works with Repository() directories (and
  tap gspencer to upstream the changes).
* Fix the evaluation of $PRE_EVALUATE_DIRS, which was interfering
  with sucking up the source files for listing in the .vcproj files.
* Set AlwaysBuild() on the project files so they're always
  evaluated for up-to-dateness when 'all_solutions' is the target.
Review URL: http://codereview.chromium.org/10725

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5440 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-14 02:26:30 +00:00
bradnelson@chromium.org 503d675964 Adding in new solution builder pattern.
Review URL: http://codereview.chromium.org/10231

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5047 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-08 00:12:34 +00:00
bradnelson@google.com 51d7120e39 Bringing in sct changes.
Review URL: http://codereview.chromium.org/10210

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5008 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-07 19:39:17 +00:00
bradnelson@chromium.org a8007fa9ca Missed a file in 9468.
Will submit this TBR.

Propogating fix from mainline sct.

Review URL: http://codereview.chromium.org/9663

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4927 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-06 23:21:43 +00:00
brettw@google.com 476481227f Unrollback the Scons changes, they weren't the cause of the problem.
Review URL: http://codereview.chromium.org/9184

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4783 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-05 17:27:18 +00:00
brettw@google.com f9ddaaceb4 Rollback r4734 to see if it fixes the crashing I experience when starting chrome, as well as the 1MB regression in chrome.dll size.
Review URL: http://codereview.chromium.org/8226

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4781 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-05 16:43:50 +00:00
bradnelson@chromium.org 1dea5d339a Adding better project generation (source and build targets).
Adding fix to targets_msvs to work with chrome hammer.bat in depot_tools.


Review URL: http://codereview.chromium.org/9149

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4734 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-05 02:37:37 +00:00
bradnelson@google.com 03be120008 Adding in new software construction toolkit version.
Review URL: http://codereview.chromium.org/9094

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4566 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-04 06:10:23 +00:00
bradnelson@chromium.org 301daed393 Adding visual studio solution files.
Sandbox is currently having a problem with this so it is disabled.
Fixed a few stray items.

Review URL: http://codereview.chromium.org/9259

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4525 0039d316-1c4b-4281-b951-d872f2087c98
2008-11-04 00:32:42 +00:00
bradnelson@google.com 46561165dd Pulling in latest software construction toolkit.
Review URL: http://codereview.chromium.org/8117

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@3861 0039d316-1c4b-4281-b951-d872f2087c98
2008-10-23 21:22:35 +00:00
bradnelson@chromium.org b2605cc773 Dropping in software construction toolkit.
Review URL: http://codereview.chromium.org/6329

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@3145 0039d316-1c4b-4281-b951-d872f2087c98
2008-10-09 22:38:44 +00:00