view etc/toolbar/replace-up.xpm @ 4939:349f01075eb7

build fixes for gdbinit and config-dependent elc files -------------------- ChangeLog entries follow: -------------------- ChangeLog addition: 2010-01-20 Ben Wing <ben@xemacs.org> * Makefile.in.in: * Makefile.in.in (GENERATED_HEADERS): * Makefile.in.in (.PHONY): * Makefile.in.in (src/.gdbinit): * configure: * configure.ac (TAB): etc/gdbinit.in has been moved to src/.gdbinit.in.in. Reflect this -- generate src/.gdbinit.in from src/.gdbinit.in.in, and use the normal mechanism for doing so instead of copying it specially. Add target for `config-changed' and pass down to `src'. Move some PHONY declarations to just before the actual targets. src/ChangeLog addition: 2010-01-20 Ben Wing <ben@xemacs.org> * .gdbinit.in.in: Moved here from etc/.gdbinit.in. Put @srcdir@ in various places rather than just `..' whenever Makefile.in.in does so. Fixes various strange crashes and errors than occur when using `..'. * Makefile.in.in (config-changed): Add target, useful when building both Unicode-internal and old-Mule workspaces using --srcdir and don't run configure before switching from one to the other.
author Ben Wing <ben@xemacs.org>
date Wed, 20 Jan 2010 19:48:26 -0600
parents 3ecd8885ac67
children 7910031dd78a
line wrap: on
line source

/* XPM */
static char * replace[] = {
"28 28 2 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c black s foregroundToolBarColor",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXooXXXXooooXXXXXXXXXXXX",
"XXXXXXooXXXXooXXoXXXXXXXXXXX",
"XXXXXoXooXXXooXXoXXXXXXXXXXX",
"XXXXXoXooXXXoooooXXXXXXXXXXX",
"XXXXoXXXooXXooXXXoXXoooXXXXX",
"XXXXooooooXXooXXXoXXooXXXXXX",
"XXXoXXXXXooXooXXXoXXoXoXXXXX",
"XXXoXXXXXooXoooooXXXXXXoXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXoXXXX",
"XXXXXXXXXXXXoXXXXXXXXXXoXXXX",
"XXXXXXXXXXXoXXXXXXXXXXXoXXXX",
"XXXXXXXXXXXoXXXXXXXXXXoXXXXX",
"XXXXXXXXXXoXXXXXXXXXXoXXXXXX",
"XXXXXXXXXoXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXoXXXXXXooooXXXXXXXX",
"XXXXXXXXoXXXXXXooXXXoXXXXXXX",
"XXXXXoXoXXXXXXXooXXXXXXXXXXX",
"XXXXXooXXXXXXXXooXXXXXXXXXXX",
"XXXXXooooXXXXXXooXXXXXXXXXXX",
"XXXXXooXXXXXXXXooXXXXXXXXXXX",
"XXXXXXXXXXXXXXXooXXXoXXXXXXX",
"XXXXXXXXXXXXXXXXooooXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};