mozilla
/
moz-skia
зеркало из https://github.com/mozilla/moz-skia.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
4 127 коммитов 1 ветка 0 Теги 134 MiB
Граф коммитов

5 Коммитов

Автор SHA1 Сообщение Дата
djsollen@google.com e7290ef304 Update the makefile and gyp for the debugger. 
Review URL: https://codereview.appspot.com/6355052

git-svn-id: http://skia.googlecode.com/svn/trunk@4410 2bbb7eff-a529-9590-31e7-b0007b416f81
 2012-06-29 18:26:27 +00:00
chudy@google.com b6789115b7 Add missing gyp dependencies for debugger 
git-svn-id: http://skia.googlecode.com/svn/trunk@4405 2bbb7eff-a529-9590-31e7-b0007b416f81
 2012-06-29 14:34:58 +00:00
chudy@google.com 902ebe5eb4 clt debugger 
Review URL: https://codereview.appspot.com/6267043

git-svn-id: http://skia.googlecode.com/svn/trunk@4404 2bbb7eff-a529-9590-31e7-b0007b416f81
 2012-06-29 14:21:22 +00:00
borenet@google.com dd3d08ea8e When building for Android, package executables in APKs (trunk) 
Review URL: https://codereview.appspot.com/6307101

git-svn-id: http://skia.googlecode.com/svn/trunk@4368 2bbb7eff-a529-9590-31e7-b0007b416f81
 2012-06-27 19:04:39 +00:00
epoger@google.com 1e8e056afc Some final cleanups leading up to The Official Switch to Gyp 
see http://codereview.appspot.com/4580043

1. Create a single public skia.gyp file that all outside projects (Chrome,
Android, etc.) should depend on from now on.  I haven't yet created targets
suitable for those projects to use, but this is where we should add them.
2. Make gyp generate its Makefiles within out/ directory, rather than polluting
directories under source control.
3. Modify trunk/Makefile to automatically run gyp_skia and then call the
generated Makefile, to ease developer transition.



git-svn-id: http://skia.googlecode.com/svn/trunk@1526 2bbb7eff-a529-9590-31e7-b0007b416f81
 2011-06-07 14:48:41 +00:00